Architecture
Roles
Seven roles, from Guest viewer to Owner. Each role includes every role below it.
The seven roles
A role belongs to one person in one organisation. It is stored as a number, and each role includes every role below it. An Owner can do everything a Billing admin can, a Billing admin everything a Domain manager can, and so on down to Guest viewer.
Each role includes every role below it.
| Value | Role | What it adds |
|---|---|---|
| 1 | GUEST_VIEWER Guest viewer | View only, no interactions |
| 3 | CONTRIBUTOR Contributor | View and contribute |
| 7 | STANDARD_USER Standard user | View, interact and contribute |
| 15 | TEAM_MANAGER Team manager | Manage the people in the team and some settings |
| 31 | DOMAIN_MANAGER Domain manager | Manage the organisation's domains |
| 63 | BILLING_ADMIN Billing admin | Manage billing and financial settings |
| 255 | OWNER Owner | Full control |
Why the numbers
Each value is a set of bits, and each role's bits contain all the bits of the roles below it. A check such as "is this person at least a Team manager" passes for a Team manager, a Domain manager, a Billing admin and an Owner.
What the roles allow today
- Team manager or higher can add a person to the organisation, change their role and remove them.
- Domain manager or higher can claim domains for the organisation and look after them. See Domains and claims.
- A CobraSphere administrator can do the same for any organisation.
Roles say what a person may do inside one organisation. Which products a person may open is a separate question, answered on Access.