Registration is coming soon. Acrosite is not open for sign-up yet.Contact us
Feature · Client ReviewClient review portal

Let clients approve content without GitHub access.

Acrosite gives Client Reviewers a dedicated review dashboard where they can see assigned projects, review assigned content, comment, approve, or request changes — without seeing GitHub, deployment settings, billing, team settings, or unrelated projects.

Client dashboardAssigned projectsNeeds ReviewApprove / request changesGitHub hidden
The client review problem

Approvals get messy when feedback lives everywhere.

Client sign-off should be simple. Without one place to do it, feedback scatters, status blurs, and clients end up closer to your internal tools than they should be.

Scattered

Feedback lands in too many places.

Client comments can end up in email, Slack, Docs, calls, spreadsheets, and screenshots.

Exposure

Clients should not see internal tools.

GitHub, deployment triggers, billing, team roles, and project settings should stay inside the team workspace.

Unclear

Review status becomes unclear.

Teams need to know what is waiting for a client, approved, or sent back for changes.

Out of context

Approvals need context.

Clients should review the actual content item, not disconnected copy pasted into another tool.

Boundary

Every client should see only their work.

Client Reviewers should not see unrelated projects, internal notes, or other clients.

Gating

Publishing should wait for the right approval.

Approved content can move forward. Content with requested changes should return to the team.

Client Reviewer dashboard

Clients get their own review dashboard, not a pile of one-off links.

Client Reviewers log in once and see the projects and review work assigned to them. They can find what needs review, what was approved, what needs changes, and what has already been published — without entering the internal workspace.

acrosite.com/client/overviewClient portal

Client Reviews

Needs ReviewChanges RequestedReviewedPublishedAll
3Needs Review1Changes Requested8Reviewed5Published3Assigned Projects
Assigned projects
Acme DentalShared by Northwind Agency3 to review
Ridge PlumbingShared by Northwind Agency1 to review
Luma LegalShared by Acme StudioAll reviewed
Recent review activity
Dental Implants Landing PageNeeds Review
FAQ: Pricing QuestionsChanges Requested
Local SEO GuideReviewed
Emergency Plumbing AustinPublished
Review detail

A focused review screen for assigned content.

From the Client Reviewer dashboard, reviewers can open an assigned item, read the content, leave comments, approve, or request changes — on one screen, with nothing technical and nothing from other projects.

acrosite.com/client/reviews/review-requestAssigned content only
Back to /client/overviewReview content
TitleDental Implants Landing Page
TypePage
StatusWaiting for Client
Assigned reviewerSarah Chen
ProjectAcme Dental
Content preview
Same-day dental implants in Austin
Trusted implant care with transparent pricing and flexible appointment hours for new patients.
SEO title previewDental Implants Austin · Acme Dentalacrosite.com/dental-implants-austin
Review actions
CommentPlease update the opening hours in the contact section.Tied to this content item
Previous review history
Changes requested by Sarah ChenMon
Re-submitted for review by teamTue
Review statusWaiting for ClientIn ReviewApprovedChanges Requested
Access boundary

Client Reviewers only see what they are assigned.

Project-level access lets a Client Reviewer participate in reviews for that project, but individual content visibility depends on assignment or review submission status. The boundary is built in, not bolted on.

Client can seeinvited projects · assigned content
Projects they were invited to review
Content assigned or submitted for their review
Review history where they were involved
Comments, approval status, and request changes
Published content history where allowed
Client cannot seeinternal settings hidden
Unrelated content
Unrelated projects
Workspace settings
Billing
GitHub
Deployment settings
Team management
Content structure builder
Scheduling and publishing controls
Review actions

Keep approval decisions attached to the content.

Comments, approvals, and requested changes stay tied to the content item so the team can act without searching through scattered messages.

/app/acmeagency/projects/acme-project/reviewsReview thread
Sarah ChenClient Reviewer2:14 PMPlease update the opening hours in the contact section.
Jordan M.Team Member2:38 PMUpdated to 8am–6pm, Mon–Sat. Re-submitting for review.
Changes RequestedIn ReviewApproved

Comment

Client leaves context-specific feedback.

Request Changes

Content moves back to the team with a clear review status.

Approve

Approved content can move toward scheduling or publishing.

Visibility control

Internal teams keep the full workflow. Clients get the review view.

The internal team works with the complete platform. Client Reviewers get a deliberately smaller surface — only what review needs.

Internal team workspaceTeam Members · full workflow
DraftsReview QueueContent CalendarPublish NowScheduled PublishingPublish LogsGitHub settingsDeployment trigger profilesTeam MembersBilling
Client review viewClient Reviewer · review only
Assigned contentCommentsApproveRequest ChangesSimple statusNo GitHubNo billingNo internal settings
Review status

Know what is waiting, approved, or blocked.

Teams can use Review Queue and status labels to see which content is waiting for client review, approved, or needs changes.

/app/acmeagency/projects/acme-project/reviewsReview Queue
Review Queue
acme-project · 4 items
AllWaiting for ClientApprovedNeeds ChangesIn Review
Dental Implants Landing PagePage · Acme DentalWaiting for Client
FAQ Pricing QuestionsCustom Content Type · Acme DentalApproved
Service Page Emergency PlumbingPage · acme-projectNeeds Changes
Local SEO GuidePost · acme-projectIn Review
Waiting for ClientSent to the reviewer; awaiting their response.
In ReviewThe reviewer has opened and is reviewing.
ApprovedCleared to move toward scheduling or publishing.
Needs ChangesReturned to the team with requested changes.
Review handoff

Send the right content to the right reviewer.

Acrosite routes review requests to Client Reviewers through account-based access, keeping each review tied to the correct project and content item.

Team MemberInvites Client Reviewer to a project
Client ReviewerAccepts the invitation
Client ReviewerCreates an account or logs in
Client ReviewerLands in /client/overview
Team MemberSubmits content for client review
Client ReviewerOpens /client/reviews/[reviewRequestId]
Client ReviewerComments, approves, or requests changes
Team MemberSees the synced review state
Invitation tokens are used only to accept the invite and link the account — the ongoing review experience is the account-based /client portal.
Clear boundaries

What Client Review means in Acrosite.

A focused review layer with deliberate edges — here is what it does, and what it does not try to be.

Client Review is
  • Account-based Client Reviewer portal
  • /client/overview dashboard
  • Assigned projects
  • Needs Review / Changes Requested / Reviewed / Published status
  • Assigned-content-only review access
  • Comments
  • Approve action
  • Request Changes action
  • Review Queue visibility for internal teams
  • No GitHub requirement
Client Review is not
  • A pile of one-off review links
  • Giving clients GitHub access
  • Giving clients billing access
  • Giving clients deployment settings
  • Giving clients full workspace access
  • Letting clients see other clients
  • Letting clients publish by default
  • A full client portal replacement in the first version
Setup checklist

What you need before your first client review.

A short list to confirm before sending content out — most of it is part of normal content setup.

1

Project access

Invite the Client Reviewer to the project.

2

Account acceptance

The reviewer accepts the invitation and logs in or creates an Acrosite account.

3

Content item

Create the Post, Page, or Custom Content Type item that needs review.

4

Review assignment

Submit or assign the content for client review.

5

Review instructions

Add clear context so the reviewer knows what to check.

6

Client visibility

Confirm that the reviewer only sees assigned projects, assigned content, and review history where they are involved.

Client Review FAQ

Questions about client review.

Access, what a reviewer can do, publishing control, visibility, and which content types apply — the specifics teams ask before inviting a client.

Open documentation
Yes. Client Reviewers use the dedicated /client portal. They can see assigned projects, review work that needs attention, changes requested, reviewed items, and published items where they were involved.
Token links are used for invitation acceptance and temporary legacy fallback only. The main review experience is account-based: Client Reviewers log in and use the /client portal.
Client Reviewers use /client/overview after login. They can also open assigned review items through /client/reviews/[reviewRequestId].
No. Client Reviewers can review assigned content without repository, branch, deployment, billing, team, or internal project access.
A Client Reviewer can view assigned content, leave comments, approve, or request changes.
Not by default. Publishing should remain controlled by authorized internal Team Members.
No. Project-level access gives them review eligibility for the project, but individual content visibility depends on assignment or review submission status.
No. Client Reviewers should only see assigned review content and should not see unrelated projects, clients, or internal workspace areas.
They can see published content history where they were involved, if the project review settings allow it. They should not see unrelated content.
Yes. A Client Reviewer can request changes, which moves the content back to the team with a clear review status.
Yes. Team Members can review content based on their role and permissions. Client Reviewers are designed for external or limited review access.
Yes. Client review usually happens before content is approved, scheduled, or published.
No. GitHub, deployment triggers, billing, Team Members, and internal settings stay hidden from Client Reviewers.
Yes. Client Review can apply to assigned Posts, Pages, and Custom Content Type items.
Start here

Give clients review access, not GitHub access.

Registration is coming soon. Contact us to talk through your publishing workflow, or read the docs to see how Acrosite works.

Registration opening soonClient ReviewersCommentsApprovalsGitHub hidden