A role is a named set of permissions — Support, Marketing, Finance. You build it once and assign it to as many users as you like.
Permissions are grouped by module, and each module has its own actions, so you can let someone read conversations without letting them delete agents.
Before you start
- Think in jobs, not people. Support is a role; Ayşe is not.
- The account owner ignores roles entirely — owners are never restricted.
Steps
- 1
Create the role
Click Create Role and give it a Role Name that describes the job.
The roles list - 2
Choose the permissions
Permissions are listed per module. Tick only what the job needs; Select all and Deselect all help when a role is close to everything or close to nothing.
Start from nothing and add what the person asks for. Starting from everything and removing things always leaves something behind.
Selecting permissions per module - 3
Assign it
The role becomes selectable in the Users form. Existing users can be moved to it by editing them.
The role in the user form - 4
Review what a role can do
Use View Role to read a role's permissions without risking a change.
Good to know
- A role marked Default is a system role — it exists for every account and is the safe starting point to copy.
- Removing a permission takes effect immediately for everyone on that role.
- If a teammate is redirected to the dashboard when opening a page, the role is
missing that page's
viewpermission — that redirect is the panel enforcing it. - Billing pages are their own permission. Someone can manage agents all day and still not see Invoices.