Overview
Permissions → Roles view defines what actions different user roles can perform. A role is a set assigned to a user, consisting of a hierarchical permission tree. Users are always granted permissions through a role.
Concepts
- Role is a named collection of individual permissions. Instead of assigning permissions to each user separately, a role is assigned to the user.
Example Roles
- Caregiver — sees their own clients and can acknowledge alerts.
- Team Leader — visibility of the team's clients and statistics.
- Administrator — all admin permissions.
- Read-Only User — observer without editing rights.
Role Basic Information
- Name — the display name of the permission group.
- Number of Users — read-only information showing how many users are assigned to this role.
- Role Permissions — what permissions are included in the role.
Creating and Editing a Role
- Open Permissions → Roles.
- Click + new or open an existing role from the list.
- Enter the name.
- Select the desired permissions for the role.
- Save.
Note. Changes to a role apply immediately to all users assigned to that role. Review the effects carefully before saving.
Additional Actions
The three-dot menu in the detail view includes:
- Delete — deletes the permission group. It can only be deleted if it is not assigned to any user. First, change the users' permission group to another, then you can delete the old one.
- Audit trail — change history of the permission group (permission admin_rolegroups_audit).
Best Practices
- Keep the number of roles reasonable — too many complicate management.
- Give the role a descriptive name (e.g., "Caregiver", "Supervisor", "Administrator") so others understand its purpose.
- Use the principle of least privilege: grant only the permissions that are necessary.
- Review roles regularly.
Permission
Managing roles requires administrator permission.
Attention. Keep the number of administrators as low as possible but at least two to avoid lockout risks.