Roles
Access is per project. Each member has one role.
| Role | Read | Edit content | Approve & publish | Change the model |
|---|---|---|---|---|
viewer | ✓ | |||
editor | ✓ | ✓ | ||
admin | ✓ | ✓ | ✓ | ✓ |
owner | ✓ | ✓ | ✓ | ✓ |
owner additionally manages members and project settings.
What each can do
viewer reads everything, including previews. Useful for stakeholders who should see work in progress without being able to change it.
editor writes and edits documents, uploads media, edits strings, and submits work for review. Cannot approve their own work or publish.
admin does everything an editor can, plus approving, publishing, reverting, and changing content and block types.
owner manages the project itself.
Two rules worth knowing
Editing content is editor; editing the model is admin. Changing a block's fields changes every document using it, which is a different kind of act from changing one page's copy.
Publishing needs admin. An editor's work is always seen by someone else before the public sees it.
Previewing
Minting a preview token needs only viewer, since previewing is reading. It still requires access to the project, so unpublished work cannot leak to someone outside it.