How Client Reviewers stay isolated
Client Reviewers work from a separate portal and only see the projects and content you assign — never your repository, deployment, billing, team, or other projects.
Client Reviewers let you bring a client into the review loop without giving them the keys to your workspace. They work from a separate portal and only see what you assign. This page explains how that isolation works.
Who this is for
Workspace Owners and Admins who invite clients to review content and want to know exactly what those clients can see.
A separate surface
The Client Reviewer Portal is a different surface from the customer app. A Client Reviewer authenticates into the portal and never inherits workspace app access. See The Client Reviewer portal.
What a Client Reviewer can see
For the projects you assign, a Client Reviewer can:
- See the content shared with them for review.
- Read and add client-visible comments.
- Approve content, or request changes.
What a Client Reviewer cannot see
A Client Reviewer cannot reach:
- Your repository, GitHub Setup, or Deployment Setup.
- Billing, workspace settings, or the team.
- Other clients or other projects.
- Internal-only review comments.
Why it is built this way
Isolation is the point: it lets you get client sign-off on content without exposing your repository, deployment, billing, or other clients. The boundary is enforced server-side, not just hidden in the interface.