Registration is coming soon. Acrosite is not open for sign-up yet.Contact us
On this page
Collaboration

Leave review comments

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

GuideFor EveryoneUpdated June 8, 2026

Review comments are how your team and your client discuss content during review. Acrosite keeps two kinds of comments — internal and client-visible — in the item's review thread. This guide explains the difference and how to add them.

Who this is for

Everyone involved in a review: Team Members who coordinate internally, and Client Reviewers who give feedback on the content shared with them.

Internal vs client-visible comments

Comments come in two visibilities:

  • Internal comments — visible to Team Members only. Use these for internal coordination, editorial notes, and decisions your client does not need to see.
  • Client-visible comments — visible to your team and to the Client Reviewers assigned to the item. Use these to talk with your client.
Important
Team Members can see both internal and client-visible comments. Client Reviewers see only client-visible comments. Keep anything you do not want your client to read in an internal comment.

Add a comment

  1. Open the content item and find the Review Comments thread.
  2. Write your note in the Add Internal Comment box.
  3. Choose Add Comment to post it to the review thread.

Each comment appears in the thread with the author's name, a label showing whether it is Internal or Client Visible, and the time it was added. Client-visible comments — including the ones your Client Reviewers add from their portal — are visible to both your team and the assigned Client Reviewers.

Review history

Alongside comments, each item keeps a Review History of key events — submitted for review, comments added, approvals, requested changes, and Client Reviewer activity — so you can see how a piece moved through review.

What happens next

Comments stay with the item through the review loop, so context is not lost when content goes back for changes and returns. When the content is ready, a reviewer approves it — see Approve or request changes.

Next steps