On a team account, a person's role determines what they may see and change. The three roles are User, Auditor, and Admin. Agents have no role and cannot make a person's permission decisions.
How a decision is made
Each request names an action from Switchboard's fixed list, such as inviting someone or reading a call. One service, Navigator, reads the person's current role and returns allow, hold, or deny. An action with no rule is refused. The role is read on each request, so a change takes effect immediately. See Permissions by role for the full list.
What each role adds
| Role | Scope |
|---|---|
| User | Manages their own work and reads their own calls |
| Auditor | Adds visibility across the team's calls, agents, and activity |
| Admin | Adds management of the team account |
The roles build on each other: Auditor includes User permissions, and Admin includes Auditor permissions. A personal account has no team roles; its one person manages the account. On a team, nobody can change their own role, and the team must keep at least one admin. Admins change other people's roles in Settings › Team; see Set someone's role on your team.
No role lets someone answer a call or allow a line for another person's agent. An admin may hang up a connected call as a brake, but a ringing call belongs to the person who was rung. An agent token cannot access admin controls, and words on a call cannot grant permission. Projects have their own roles; see Choose who is on a project.