Workspace and roles
Your own space inside the API: your people, your rules, your queue.
A workspace belongs to one organisation. It has its own API keys, team, house style, review queue and activity log. Nothing in it is shared with other workspaces, and nothing you configure affects the shared engine or other users.
Who can do what
| Owner | Admin | Editor | Member | |
|---|---|---|---|---|
| Run checks in the dashboard and by API | yes | yes | yes | yes |
| Review held claims | yes | yes | yes | no |
| Change house style | yes | yes | no | no |
| Create and revoke API keys | yes | yes | no | no |
| Add and remove people | yes | yes (not admins) | no | no |
| Appoint an admin | yes | no | no | no |
| See the activity log | yes | yes | no | no |
| Hand over ownership | yes | no | no | no |
The owner
The first person from an organisation to sign in becomes its owner. The owner can hand ownership to anyone in the team at any time. The previous owner becomes an admin. A workspace always has exactly one owner, so someone is always responsible.
One workspace per organisation
Everyone must use an email at the organisation's own domain (for example @yournewsroom.com). If a second person from the same domain signs in before being added, they are told to ask the owner. This stops a stranger taking over your organisation's workspace.