Team workflow
Roles
Each project has its own roles. Team owners and admins are always project admins.
| Role | Can |
|---|---|
| Admin | Everything, including members, environments and deleting the project |
| Developer | Content, media, collections and fields, API keys, webhooks and environments |
| Editor | Create, edit, review, publish and delete content and media |
| Author | Write drafts and submit them for review; can't publish or delete |
| Viewer | Read-only access to content and media |
| No access | Doesn't see the project |
Set a default role for team members and override it per person in Project settings → Members.
Review before publishing
Turn on Review required for a collection, and entries go through: Submit for review → reviewer approves (then publishes) or requests changes. Reviewers are emailed when something is submitted, and authors when it's approved or sent back.
Comments
Every entry has a Comments panel: start a thread on the entry or on a specific field, reply, and resolve threads when done. Request changes opens a thread with the reviewer's note. Participants are emailed about new comments, and each person can turn these emails off per project.
Environments
An environment is a sandbox copy of a project (for example staging), with its own API id and keys, so you can change collections and content without touching the live site.
- Promote schema copies collection and field changes back to main.
- Promote content copies entries to main, one entry or a whole collection at a time. Media and relations are carried over, and main's previous version is saved first so you can restore it. Promote & publish also publishes the result.
Entries created in an environment before content promotion existed can't be matched to their originals, so promoting them creates new entries in main.