Collaboration

Invite people who help run the workspace — editors, managers, developers, and admins — and choose the role that fits their work.

Invite a client to review and approve content for a specific project, without giving them workspace, GitHub, or billing access.

How access works in Acrosite: Team Members hold a workspace role, Client Reviewers get project-scoped review-only access, and the Owner is protected.

What each Team Member role can do — Owner, Admin, Manager, Developer, Editor, Author, and Viewer — so you can assign the least-privileged role that fits.

Change a Team Member's role, suspend and reactivate access, or remove someone from the Team page. The Owner is protected from accidental changes.

Track Team Member and Client Reviewer invitations that have not been accepted yet, and resend or revoke them. Pending invitations count toward your invite capacity.

How content moves through review in Acrosite: submit a draft, gather internal and Client Reviewer feedback, then request changes or approve. Approval prepares content to publish but does not publish it.

Send a draft into review with Submit For Review so Team Members and assigned Client Reviewers can comment, approve, or request changes.

Review an item that is In Review and either Approve it, with an optional approval note, or Request Changes with a summary of what to fix.

Add internal comments your team sees and client-visible comments your Client Reviewers see, all in the item's review thread.

The Review Queue shows every review across your projects (or one project) — what is waiting, who decided, and what is ready — filtered by kind, status and project.

What a Client Reviewer sees and does in their dedicated portal: review the content shared with them for a project, comment, and approve or request changes — nothing else.

An overview, for your team, of the isolated experience a Client Reviewer gets — and what they cannot see — so you know exactly what you are sharing.