Scopes and role archetypes
The three scopes and the five role archetypes, with how many keys each archetype carries. The table is generated from the product's own definitions.
For: Platform administrator, Builder, Account administrator, Tenant administrator, Operator, Auditor, Member
Scopes
Scopes are nested: every tenant belongs to an account, every account to the platform. read, write and publish granted in the scope above flow down to the scopes below; purge doesn't.
| Scope | What it is |
|---|---|
| Platform | inlorus's top scope; it covers every account. |
| Account | An organization's scope; it holds its tenants together. |
| Tenant | The scope where the work is done: members, teams, applications and records. |
Role archetypes
| Archetype | What for | Number of keys |
|---|---|---|
Administrator (administrator) | Every key in the scope it is assigned in. Delete (purge) applies only to data in the assignment's scope. Platform, account and tenant administrator are this one role assigned at three scopes. | 45 |
Builder (builder) | The package needed to build, and it stops there. It does not include member management, writing configuration or delete. | 14 |
Operator (operator) | Running what others have built: reads and writes operations and integrations. | 8 |
Member (member) | Using the product: reads and writes records. It can be held only in a tenant scope. | 4 |
Auditor (auditor) | Every read key in the permission glossary, and nothing else. A new resource's read key is included automatically. | 18 |
An archetype applies in the scope it is assigned in. The same archetype can be given to different people in different scopes; for example, Auditor reads everything when given on the platform, and only that tenant when given in a tenant.