Roles reference

A quick reference to the roles in Acrosite and what each can do. Workspace roles apply across the workspace; Client Reviewers are separate and project-scoped. For a fuller explanation, see Team Member roles explained.

Workspace roles

These roles are assigned to Team Members:

• Owner — full control of the workspace, including billing. The Owner is protected and cannot be changed, suspended, or removed from the Team page.
• Admin — manages the team, projects, and integrations across the workspace.
• Manager — manages content workflow: reviews, approvals, scheduling, and publishing.
• Developer — manages GitHub Setup, Deployment Setup, paths, and technical troubleshooting.
• Editor — creates and edits content and manages media.
• Author — creates and edits content and submits it for review.
• Viewer — read-only access where allowed.

Assign the least-privileged role that lets someone do their job; you can change it later. See Manage Team Members.

Client Reviewer

A Client Reviewer is not a workspace role. They are invited to a specific project and work only from the Client Reviewer Portal, where they can review assigned content, comment, and approve or request changes — and nothing else. They do not get GitHub, deployment, billing, team, or workspace settings access. See How Client Reviewers stay isolated.

What roles control

Access in Acrosite depends on your role, your scope, and the resource — not a single on/off switch. Roles gate things like workspace settings, content and publishing, GitHub and deployment setup, logs, and the client review portal. For the access model, see Roles and access overview.

Next steps

• Team Member roles explained
• Roles and access overview
• Manage Team Members