Roles¶
Admin → Users → Roles defines what a user can do. A role is a named set of permissions, and every user has exactly one.
Creating a role: the code and the name are both required and both unique.
The list¶
Each row shows the code, the role name, the status, how many users have it, how many permissions it grants, and when it was created and updated. Search works on the code and the name.
Create a role¶
| Field | Rule |
|---|---|
| Code | Required and unique. Uppercase letters, digits, and underscore only, up to 32 characters — no spaces, hyphens, or accents |
| Role name | Required and unique, up to 100 characters |
If the code or the name already belongs to an inactive role, the form offers to reactivate that role instead of creating a duplicate. Accepting it restores the existing role with its permissions intact.
Permissions¶
Open a role and go to its permissions to choose what it grants. The picker shows:
- the permission code and a readable name in the interface language;
- a type badge: Core for current permissions, Deprecated for retired ones kept for compatibility.
Permissions are grouped the way the product classifies them: core, admin, plugins, classic, and deprecated. The exact codes are listed in Permission reference — useful when you need to match a role against a support request.
A change to a role applies when its users sign in again: permissions are read at the start of a session.
Deactivate or delete¶
- Inactive keeps the role and its permissions but stops it from being assigned.
- Delete asks for confirmation and removes the role. Users who had it need another role, so review the user count in the list first.
Roles you cannot change¶
Some roles are part of the platform and are protected: the row does not offer edit or delete. They exist so that an administrator always has a way in.
Related¶
- Users — assigning a role.
- Permission model — how permissions are enforced.
- Permission reference — the generated catalogue.