Team roles and permissions

Owner and Admin manage settings, billing, and team members. Editors create and schedule content. Approvers sign off on content before it publishes. Viewers see reporting and analytics only.

From Team, invite by email and assign a role — they're in as soon as they accept. Change or revoke access at any time as responsibilities change.

Roles run from owner through admin, editor, approver and viewer. Start people at the least access that lets them do their job — widening a role later is trivial, and it keeps publishing rights with the people accountable for them.

An editor can draft and schedule but cannot approve; an approver can sign off without needing to draft. Keeping them separate is what makes the review step meaningful rather than a formality.

A role applies to one workspace only. Someone who works across several clients gets a role in each, and access to one never implies access to another.

Approvals, rejections and their reasons are recorded, so it's possible to answer who signed off on a specific post afterwards. That record is often the practical argument for using approvals at all.