| Viewer | Reviewer | Administrator | |
|---|---|---|---|
| Create and work tasks | ✓ | ✓ | ✓ |
| Skip review on own tasks | — | ✓ | ✓ |
| Approve / reject / publish | — | ✓ | ✓ |
| Manage automations | — | — | ✓ |
| Delete tasks | — | — | ✓ |
| Manage integrations & team | — | — | ✓ |
Workspace
Team & roles
Who can draft, who can approve, who can administer
Invite teammates from Settings → Team. Every member has one of three roles, and the roles are the review gate’s enforcement mechanism:
A Viewer’s tasks always require review — even if the task asks to skip it — which makes Viewer the right role for anything that drafts content but should never ship it. That’s exactly why agent API keys belong on Viewer-role identities: the agent can propose all day and approve nothing.
Team size is bounded by your plan. Billing itself belongs to the organization owner rather than any workspace role.