Roles and access overview
How access works in Acrosite: Team Members hold a workspace role, Client Reviewers get project-scoped review-only access, and the Owner is protected.
Access in Acrosite has two clear tracks. Team Members work inside your workspace and hold a role that controls what they can do. Client Reviewers get project-scoped, review-only access through a separate portal. This page explains how the two fit together.
Who this is for
Workspace Owners and Admins, who manage who can do what. Only Owners and Admins can invite people and change access.
Team Members hold a workspace role
A Team Member is someone inside your workspace — an owner, admin, manager, developer, editor, author, or viewer. Their role decides what they can do across projects: manage the team, set up GitHub and deployment, create and edit content, run reviews and publishing, or just read. See Team Member roles explained for what each role can do, and Invite a Team Member to add one.
Team Members count toward your plan's Team Member limit, and pending invitations count toward that capacity too.
Client Reviewers get project-scoped review access
A Client Reviewer is usually your client. They get review-only access to a single project through the Client Reviewer Portal, where they can see the content shared with them, comment, and approve or request changes. They never receive workspace settings, GitHub, or billing access, and they cannot see other projects. See Invite a Client Reviewer.
The Owner is protected
Every workspace has one Owner with full control, including billing. The Owner cannot be changed, suspended, or removed from the Team page — they show as PROTECTED OWNER — so you cannot accidentally lock yourself out. Owner transfer is handled separately.
Where you manage access
Open your workspace and go to Team. From there you manage Team Members, Client Reviewers, pending Invitations, and the Roles & Access view, all in one place.