What your client sees in review
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.
Before you invite a client to review content, it helps to know exactly what they will — and will not — see. This page describes the Client Reviewer experience from your team's perspective, so you can share content with confidence.
Who this is for
Owners and Admins, who invite Client Reviewers and decide what to share.
What you are sharing
When you submit a content item for review, the Client Reviewers assigned to that project can review it in their portal. You control this at the item level: an item shows its Client Delivery state — for example, how many portal reviewers have access — so you always know what a client can currently see.
A focused, isolated view
A Client Reviewer's experience is deliberately narrow. For the one project they were invited to, they can:
- Read the content you shared for review.
- Add client-visible comments.
- Approve the content or request changes.
They cannot browse your other projects, see your repository or deployment setup, view billing or workspace settings, or read your internal comments. This isolation is a feature: it lets you bring a client into the loop without exposing the rest of your work. See The Client Reviewer portal for the reviewer's side.
Internal vs client-visible
Your team sees the full review thread; the client sees only client-visible comments. Keep editorial discussion in internal comments, and use client-visible comments to talk directly with your client. See Leave review comments.
How their feedback reaches you
A Client Reviewer's approvals, requested changes, and client-visible comments appear in the item's review thread and history alongside your team's, so everything stays in one place.