Team and roles

You can invite your team and give each person exactly the permissions they need. For example: an assistant who operates calls and campaigns, but can't see billing or administrative information.

The system roles

• Administrator — full access, including billing and team management.
• Operator — runs the day-to-day (launching campaigns, handling/transferring calls, editing knowledge bases) without touching billing.
• Viewer — read-only: sees agents, calls, and reports, without changing anything.

Viewer and Operator are editable by your organization: adjust their permissions matrix and every user with that role inherits it instantly. Administrator always has full access (so you're never locked out of administration).

Custom roles

1. 1
   Create a role

   In Settings → Roles, "Create role". Give it a name (for example "Assistant").

2. 2
   Check the permissions

   A matrix of modules (Agents, Calls, Campaigns, Billing…) across View / Operate / Manage levels. Check exactly what it needs.

3. 3
   Assign it when creating users

   In Team, when inviting someone, choose their role — a system role or a custom one.

What someone without a permission sees

The portal adapts to each person's role: nobody sees buttons they cannot use. When a user is missing a permission, the action simply is not there — it does not show up and then fail.

• Modules without read access do not appear in the menu (nor in the quick search).
• Buttons to create, edit, archive, buy or launch are hidden from anyone who cannot use them.
• The agent editor opens in read-only mode: the whole configuration is visible, with a notice on top, and the fields cannot be modified.
• In forms where hiding a field would be confusing (a dropdown, a toggle), the control is disabled and hovering it explains that you lack permission.
• The Copilot follows the same rules: it only offers the blocks and actions your role allows.