Roles and Permission Management
Overview
The Role Management section allows administrators to define and control user access levels within the system. Roles act as templates that group specific permissions, which you can then assign to users based on their responsibilities.
What Are Roles?
Roles are predefined sets of permissions that determine what users can and cannot do. Think of them as job titles with associated access rights. Common examples include:
- Administrator – Full system access
- Editor – Can create and edit content
- Viewer – Read-only access
- Manager – Can approve and manage team content
Key Features
1. View All Roles
See a list of all existing roles with key details:
- Role Name – The title of the role
- Guard – The security system the role belongs to (usually "web")
- Team – Which team the role applies to (if using multi-team setup)
- Permissions Count – How many permissions are assigned to the role
- Last Updated – When the role was last modified
2. Create a New Role
Add custom roles to match your organization's needs:
- Click "Create Role"
- Enter a descriptive name
- Select individual permissions or use "Select All"
- Save to make the role available for assignment
3. Edit Existing Roles
Modify role permissions as requirements change:
- Add or remove specific permissions
- Update the role name
- Change team assignments (if applicable)
4. Delete Roles
Remove roles that are no longer needed:
- Delete individual roles
- Select multiple roles for bulk deletion
Understanding Permissions
Permissions are specific actions users can perform. Each permission controls access to a particular feature or action:
- View – Can see records or pages
- Create – Can add new records
- Update – Can edit existing records
- Delete – Can remove records
Teams & Scoping
If your system supports multiple teams or organizations:
- Global Roles – Available to all teams
- Team-Specific Roles – Only available to selected teams
Best Practices
1. Start with Standard Roles
Begin with common roles like Administrator, Editor, and Viewer before creating custom ones.
2. Principle of Least Privilege
Grant only the permissions users need to perform their tasks—nothing more.
3. Use Clear Naming
Name roles descriptively so their purpose is obvious (e.g., "Finance Approver" instead of "Role 3").
4. Regular Audits
Periodically review roles and permissions to ensure they still match current needs.
5. Document Role Purposes
Maintain documentation explaining what each role is for and who should have it.
Navigation
- Location: Usually found in Administration or Settings
- Icon: Shield (🛡️)
- Access: Typically limited to administrators
Getting Started
Step 1: Access Role Management
- Log in with administrator credentials
- Navigate to the administration panel
- Click "Roles" or "Role Management"
Step 2: Create Your First Role
- Click "Create Role"
- Name it (e.g., "Content Editor")
- Select permissions (e.g., view pages, create pages, edit pages)
- Click "Save"
Step 3: Assign to Users
- Go to User Management
- Edit a user's profile
- Assign the newly created role
- Save changes
Common Scenarios
Scenario 1: Adding a New Department
- Create roles specific to the department (e.g., "HR Manager," "HR Assistant")
- Assign appropriate permissions to each role
- Assign roles to department members
Scenario 2: Creating Audit Accounts
- Create a "Read-Only Auditor" role
- Grant only "View" permissions
- Assign to external auditors or compliance officers
Scenario 3: Temporary Access
- Create a "Temporary Contractor" role
- Grant limited, time-sensitive permissions
- Remove or disable the role when no longer needed
Troubleshooting
Issue: Can't See Role Management
- Ensure you're logged in as an administrator
- Check if your user account has the necessary permissions
- Contact your system administrator if access is missing
Issue: Role Not Appearing for Users
- Verify the role is saved and active
- Check if the role is team-specific (user might be in a different team)
- Ensure the user account is properly configured
Issue: Permissions Not Working
- Confirm permissions are correctly assigned to the role
- Check if users have the correct role assigned
- Verify there are no conflicting permissions from multiple roles
Security Notes
- Role changes take effect immediately
- Deleting a role will remove it from all assigned users
- Always test new roles in a safe environment before deploying widely
- Keep administrator accounts to a minimum
Support
If you encounter issues not covered here:
- Check system documentation for specific configuration details
- Contact your IT department or system administrator
- Refer to error messages for specific guidance
Remember: Roles are fundamental to system security. Thoughtful role design helps maintain security while enabling users to work effectively.