Creating Custom Roles
Creating Custom Roles
Learn how to create and manage custom organizational roles in the Shifts platform, define their permissions, and establish hierarchical relationships to create a role structure that matches your organization’s needs.
Overview
The Shifts platform allows you to create custom organizational roles that match your company’s specific management structure. These roles define what users can access and modify within the system, allowing for precise control over permissions and responsibilities. This article explains how to create, configure, and manage these custom roles.
Understanding Organizational Roles
Organizational roles in Shifts serve several important functions:
- Access Control: Define what features and data users can access
- Permission Inheritance: Establish hierarchical relationships between roles
- Responsibility Delegation: Assign appropriate capabilities based on job responsibilities
- Organizational Structure: Map your actual organizational hierarchy within the platform
Default System Roles
The Shifts platform comes with four built-in system roles that cannot be deleted:
- Super Admin: Complete access to all features and settings
- Administrator: Full administrative access except system-level settings
- Manager: Operational management capabilities
- Staff: Basic self-service access
Creating a Custom Role
To create a new custom role:
- Navigate to Admin Settings > Roles & Permissions
- Click the Create New Role button
- In the form that appears, enter:
- Role Name: A clear, descriptive name (e.g., “Regional Director”)
- Description: Details about the role’s purpose and responsibilities
- Hierarchy Level: Numerical value determining position in organizational hierarchy (lower numbers = higher rank)
- Optionally select a Parent Role if this role reports directly to another
- Click Create Role
Setting Role Hierarchy
Roles exist in a hierarchical structure, with higher-level roles having authority over lower-level ones:
- Hierarchy Levels: Each role has a numerical hierarchy level (1 = highest)
- Relative Positioning:
- Roles with lower numbers supervise roles with higher numbers
- Roles with the same number are peers
- Parent-Child Relationships: Optionally establish direct reporting relationships
- Inheritance Impact: Hierarchy affects how permissions can be inherited
Example Hierarchy Structure
- Level 1: Executive (C-Suite)
- Level 2: Director
- Level 3: Regional Manager
- Level 4: District Manager
- Level 5: Location Manager
- Level 6: Supervisor
- Level 7: Staff
Configuring Role Permissions
After creating a role, you need to configure its permissions:
- From the Roles list, click on the role you want to configure
- Go to the Permissions tab
- You’ll see permission categories (Shifts, Users, Leave Requests, etc.)
- For each category, set permissions:
- View: See information in this category
- Create: Add new items in this category
- Edit: Modify existing items
- Delete: Remove items
- Manage: Special actions specific to the category
Permission Inheritance Modes
For each permission, you can set how it applies to users and their subordinates:
- Self Only: Permission applies only to this role
- Direct Reports: Applies to this role and immediate subordinates (one level down)
- Full Hierarchy: Applies to this role and all subordinates (all levels down)
- Custom Depth: Applies to this role and a specific number of levels down
To set inheritance mode:
- Click the Advanced option next to a permission
- Select the inheritance mode from the dropdown
- For Custom Depth, enter the number of levels
Assigning Users to Custom Roles
Once roles are configured, you can assign users to them:
- Go to Admin Settings > Users
- Select a user to edit
- In the user’s profile, find the Role section
- Click Change Role
- Select the appropriate role from the dropdown
- Click Save Changes
Alternatively, assign a role when creating a new user:
- Go to Admin Settings > Users
- Click Add New User
- Complete the user details
- Select the role in the Role dropdown
- Complete the user creation process
Managing Existing Roles
You can modify, deactivate, or (for custom roles) delete roles:
Editing a Role
- Go to Admin Settings > Roles & Permissions
- Find the role you want to edit
- Click the Edit icon
- Make your changes to the name, description, or hierarchy level
- Click Save Changes
Deactivating a Role
- Go to Admin Settings > Roles & Permissions
- Find the role you want to deactivate
- Toggle the Active switch to Off
- Confirm your decision
Note: Users assigned to deactivated roles will lose the permissions associated with that role.
Deleting a Custom Role
- Go to Admin Settings > Roles & Permissions
- Find the custom role you want to delete
- Click the Delete icon
- Confirm the deletion
Important: You cannot delete system roles (Super Admin, Administrator, Manager, Staff).
Role Permission Reports
To review your role structure and permissions:
- Go to Admin Settings > Roles & Permissions
- Click Permission Reports
- Here you can:
- View a complete matrix of roles and their permissions
- Compare permissions between roles
- Export the permission structure for reference
Best Practices
For effective role management:
- Match Your Organization: Create roles that mirror your actual organizational structure
- Use Clear Naming: Make role names intuitive and consistent with your company’s terminology
- Apply Least Privilege: Grant only the permissions needed for the role’s responsibilities
- Document Role Purpose: Add detailed descriptions of each role’s intended use
- Regular Audits: Periodically review roles and their assigned permissions
- Limit Super Admins: Restrict Super Admin access to only those who truly need it
- Consider Hierarchy Carefully: Plan hierarchy levels to ensure proper inheritance
Troubleshooting
- Permission conflicts: When a user has multiple roles, the highest-level permissions apply
- Cannot delete a role: Ensure no users are currently assigned to the role
- Permission inheritance not working: Verify hierarchy levels are set correctly
- Custom role not appearing: Check that the role is marked as Active
Related Resources
This article should be updated when:
- The role management interface changes
- Additional permission types are added
- Changes to inheritance models occur
- New system roles are introduced