Assign owner, admin, editor, approver, and viewer roles
Match team access to the smallest set of actions each person should perform.
Owners and admins manage credentials, keys, webhooks, and roles. Editors create and submit content, approvers review and decide, viewers read brand data, and publishing actions remain gated by both role and API scope.
What this means in practice
Owners and admins manage credentials, keys, webhooks, and roles. Editors create and submit content, approvers review and decide, viewers read brand data, and publishing actions remain gated by both role and API scope.
Use the documented brand and account boundaries consistently across the scheduler, REST API, SDK, MCP tools, SSE consumers, and webhooks. That makes the same social operation explainable to an operator and reproducible by an integration.
Implementation checklist
Make ownership durable and avoid tying the only owner role to a temporary contractor.
Use admin only for people who manage security-sensitive configuration.
Use editor for day-to-day composition and scheduling preparation.
Use approver for review authority without granting credential administration.
Audit role changes and remove access promptly when responsibilities change.
Operational details
A user's role and an API key's scopes are separate authorization inputs.
Viewer access is suitable for reporting and observation but not inbox replies.
The scheduler should hide controls the current role cannot use while the API enforces the same rule.
Common mistakes to avoid
- Do not make everyone an admin to work around a missing content workflow.
- Do not use shared human accounts for approvals.
- Do not rely on disabled UI buttons as the only permission enforcement.