Management roles define the functions accessible within the administration. Open General Settings → Roles, then a role or an assignment group. Without a record identifier, you return to the list.
This section requires role management or assignment rights. Role and group records have their own Save button: complete their changes before returning to general settings.
Create a Role
- In Roles, click New Role.
- Enter a Name and optionally a Description.
- Choose Blank Role, a template, or an existing role in Copy from an existing role.
- Click Create, then set the rights in the record.
System templates are protected. Duplicate lets you start from one to create a definition specific to the customer. You can only delegate rights within your own scope. A template whose rights exceed this scope is unavailable.
Define Rights and Their Targets
| Field | Purpose | Possible Values | Example |
|---|---|---|---|
| Name | Mandatory identifier | Non-empty text | Reception |
| Description | Details about the role | Optional text | Viewing and transfers |
| Active | Puts the role into service | Toggle | Enabled |
| Search for a right | Filters the editor | Function or resource name | Users |
| Rights toggles | Allow the proposed actions | Read, write, and actions specific to the resource | Read |
| Scope | Limits the resources affected | Scopes offered based on your rights | Designated elements |
Check All and Uncheck All change the set offered in the editor. Check dependencies announced by "Also requires read access to: …". For Designated elements, open the selector, search for targets, enable the elements, then click Apply. This application prepares the role's draft; Save in the record saves it.
Only rights relevant to your organization are offered. Settings for the entire telephony system (updates, system API tokens, main visual identity, system settings for artificial intelligence, platform email sending method, system codecs, log purging) never appear in a role and cannot be granted. Three rights remain reserved for the organization administrator and cannot be delegated within a custom role: Imports, Single Sign-On, and organization API token management. Organization SIP Trunk Connections can be delegated and appear in the Telephony family.
A holder cannot modify their own rights or their own listening or supervision options: have another administrator do this. During an update, rights that can no longer be delegated are automatically removed from existing roles; the operation is recorded in the audit log.
To manage users, grant Users; add read access to Extensions if the manager needs to view and modify extensions. Without this right, the list and record remain usable for identity (first name, last name, email), without the extension column and information. Record sections for which the right is missing are not displayed.
Choosing Softphone Menus
In the record of a customer role, the Softphone Menus block lets you choose the entries displayed in the personal workspace.
- Check the menus to display and uncheck those to hide.
- Click Save in the role record.
- Check the beneficiaries and have their personal navigation verified.
| Field | Purpose | Possible Values | Example |
|---|---|---|---|
| Menu checkboxes | Chooses the display for this role | Checked: displayed; unchecked: hidden | Uncheck Chat |
Phone and Settings always remain visible and do not appear among the checkboxes. This setting hides the display; it does not remove any right and does not change notifications. Displaying a menu does not grant access to a forbidden function or an unavailable module.
Only active roles assigned directly or inherited from a group participate in the choice. A menu is only hidden if all these roles hide it. For example, if one role hides Chat and another leaves it checked, Chat remains displayable. Without an active role, this setting hides no menus.
You can create a role with no management right, intended solely to configure softphone menus. System roles cannot be modified; duplicate one to obtain a customer-specific role. Duplication also carries over the hidden menus.
Adding Holders and Groups
In Holders, use Add a holder…. The list distinguishes a Direct assignment from inheritance via a group. Effective Beneficiaries lets you check who actually receives the role. Removing a holder may require confirmation naming the people affected.
In Groups, New Group creates an assignment group. Enter the name, add people with Add a member…, then check the desired roles and click Save. This assignment group is neither a department nor a ring group.
Disabling and Deleting
The role menu lets you enable or disable a customer role. Delete announces the people and groups affected. Deleting a group announces how many members will lose its roles. Cancel if you only want to modify a member. System templates cannot be deleted here.
Verifying the Result
Reopen the role, check rights, scopes, and effective beneficiaries. Have the accessible menu verified by a relevant person. A role alone does not make a module disabled for the customer available.
If It Doesn't Work
In case of a version conflict, use the displayed review command, compare the current state and your draft, then save. A multi-step operation may be partially successful; steps already saved remain in effect. A grayed-out right may exceed what you are allowed to delegate.
