The review workflow
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.
Review is how content gets a second set of eyes before it publishes. In Acrosite, an author submits a draft, your team and any assigned Client Reviewers give feedback, and a reviewer either approves the content or asks for changes. This page explains the flow end to end.
Who this is for
Everyone who creates, reviews, or approves content — authors, editors, managers, admins, owners, and Client Reviewers.
The review loop
Most content moves through review like this:
- An author or editor writes a Draft and chooses Submit For Review. The item becomes In Review.
- Team Members and any assigned Client Reviewers read it and leave comments.
- A reviewer with the right role either Approves the item, or chooses Request Changes with a short summary. Requesting changes moves it to Needs Changes.
- The author revises and resubmits, and the loop repeats until the item is Approved.
See Understand content statuses for what each status means.
Approval prepares, it does not publish
This is the most important thing to understand about review:
Internal team and Client Reviewers
Review brings two audiences together in one place. Team Members coordinate internal review and can see both internal and client-visible comments. Client Reviewers work from their own portal and see only what you share with them. See Approve or request changes and Leave review comments.
Where to track review
Each project has a Review Queue showing what is waiting, what changed, and what is ready for its next step. See Use the Review Queue.