Start here
Who does what
The four workspace roles, what each can decide, and the two rules that shape them: everyone can read, and approving is not publishing.
A workspace has four roles: Owner, Admin, Editor and Viewer. Two rules explain most of the table below. First, every member can read everything in a workspace they belong to; there is no role that sees less. Second, the decisions are separated by weight: an editor can approve a topic and a draft, but the settings, the integrations and the act of putting something live belong to owners and admins.
Where a screen cannot offer you an action, it says so rather than hiding the button. You will see lines like "Only editors and above can start research" and "Only owners and admins can change where content is published".
The roles
| What you can do | Owner | Admin | Editor | Viewer |
|---|---|---|---|---|
| See every screen in the workspace | Yes | Yes | Yes | Yes |
| Comment on a draft | Yes | Yes | Yes | Yes |
| Decide an opportunity: Move forward, Not worth it, Do it anyway, Find another angle | Yes | Yes | Yes | |
| Research a topic (spends against the workspace budget) | Yes | Yes | Yes | |
| Approve or send back an outline or a draft; apply or dismiss findings; vouch for a source | Yes | Yes | Yes | |
| Add or remove a topic exclusion | Yes | Yes | Yes | |
| Accept or dismiss a report insight | Yes | Yes | ||
| Edit the playbook rules and decide learned rules | Yes | Yes | ||
| Edit the company profile, set direction, accept a re-read | Yes | Yes | ||
| Configure and run the AI visibility prompt panel; measure the market | Yes | Yes | ||
| Connect, re-check or disconnect integrations; choose a property | Yes | Yes | ||
| Manage publishing destinations | Yes | Yes | ||
| Run setup and finish the build | Yes | Yes | ||
| Rename the workspace, set the rebuild cadence, invite people, change roles, remove members | Yes | Yes | ||
| Delete the workspace | Yes |
What the shape means in practice
Viewers read and comment. A viewer sees the queue, the drafts, the reports and the playbook exactly as everyone else does, and can leave a comment on any passage of a draft. They cannot move anything.
Editors run the content work. An editor decides topics, starts research, approves outlines and drafts, and can keep a theme out of the queue. Excluding a topic follows the same permission as deciding one, because it is a decision about the queue, not about the playbook.
Editors do not publish. An editor can approve a draft; putting it live is a separate act that belongs to owners and admins. In this release that act is downloading the Markdown and publishing it yourself, and the Publishing settings page says so. The separation is deliberate, not an oversight.
Owners and admins run the workspace. Setup, integrations, the company profile, the playbook, the prompt panel and the members list are theirs. The difference between the two is small: only an owner can delete the workspace. Owners cannot be demoted or removed from the members screen, and cannot leave.
Where roles are set
Roles are assigned when you invite someone and can be changed on the workspace's members list. The invite form offers Admin, Editor and Viewer; ownership comes from creating the workspace. See Invite your team and Workspace and members.