Content

Review queue

Inspect the submitted version, request changes and publish exactly what was approved.

GroCMS 0.1.0 · Reviewed 15 September 2026

Download this guide

What a review contains

A review is a request to assess one exact saved revision of an entry. It is not a live window onto whatever the author happens to be typing now. This makes an editorial decision reproducible: the title, body, fields and layout you approve remain identifiable even if newer work has been saved since submission.

Approval and publication are separate actions. Approving a review records the decision, but does not change the public site. Publish reviewed revision deliberately publishes that approved saved version. The normal content editor's Publish button instead targets its current saved working revision, so choose the review dialog when your intention is to publish the approved version.

Sources: Review and schedule screens; Overview and workflow queries; Content and publication service.

Submit work for assessment

  1. Open the entry, finish the changes you want assessed and wait for Saved. Resolve errors or conflicting saves first.
  2. Choose Submit for review when that control is available. Contributors use it for their unpublished Posts; authors and contributors also use it for their own profiles.
  3. Continue editing only with the understanding that later saves do not alter the submitted revision.
  4. If the newer revision should replace the pending submission, save it and submit again. The previous pending review becomes superseded.

The normal editor shows Publish to someone who already has publication capability, rather than offering a separate Submit button alongside it. A review is not enforced as a prerequisite for every permitted publisher. The current permission model also does not enforce that the submitter and reviewer must always be different people; teams that require independent approval should make that responsibility explicit.

Sources: Resource editor; Resource permission policy; Content and publication service; Two-role review browser journey.

Find the right review

Open Review queue, use Search titles and choose Search, or narrow the State selector. Previous page and Next page reach older entries. Refresh reloads the current search. The title comes from the submitted revision, so searching for a title introduced only in a later draft may not find the older submission.

StateMeaning
pendingWaiting for an authorised decision.
approvedThe named revision was approved; it may still need publication.
changes-requestedA reviewer requested revisions, with a note explaining what to improve.
supersededA newer submission replaced a previously pending review.

You see submissions you are allowed to read and either submitted yourself or have authority to publish. Editors do not receive designer-only template reviews. Designers can make decisions for design resources they can publish. A contributor can see their eligible submission without receiving the power to approve or publish it.

Sources: Review and schedule screens; Overview and workflow queries; Resource permission policy.

Inspect, preview and decide

  1. Choose Inspect revision on the relevant row. Read the submitted title, revision date and state.
  2. Start with What changed. Read the highlighted text, settings and added, removed, moved or changed layout blocks. Compare from/to identifies the exact saved versions by title and date. Expand Read the full submitted text to read the complete body and summary.
  3. Notice the warning if newer working edits exist. Open latest working draft is a separate link and is not the submitted version.
  4. Choose Create private preview, then Open submitted preview for the submitted version rendered through the site. The preview belongs to your signed-in account.
  5. For a pending review, write a useful Review note and choose Request changes, or choose Approve revision when the saved version is ready. Approval remains disabled until the selected comparison loads; it records a decision and does not publish.
  6. After approval, choose Publish reviewed revision when you intend to release it. Review the saved-revision checks and choose Publish saved revision. Confirm the message that this reviewed revision is currently published.

Removed text is struck through and added text is underlined. Settings use readable values and layout changes identify each block without requiring saved JSON. Link destinations are visible in the comparison. Reference names are current names available to your account, not historical names stored in the revision; technical details retain exact identifiers. Use the private preview for formatting placement and complete visual appearance. Long or malformed comparisons are marked incomplete and complete JSON downloads remain available.

For example, a contributor submits a 600-word report and then starts adding an unverified quotation. The editor can review and publish the submitted report without accidentally publishing that quotation. The newer working draft remains available, and visitors continue to see the precise revision chosen for publication.

Sources: Review and schedule screens; Overview and workflow queries; Two-role review browser journey.

Resolve review problems

Request changes requires a non-empty note in the interface. Describe the change concretely, such as checking a date or shortening an introduction. The decision's note appears on the review row. After making changes, the writer should create a new saved submission; editing alone does not reopen a decided review.

A review may stop accepting a decision if another reviewer has already acted or the entry moved to trash. Refresh instead of assuming the first decision failed. Publication can still be rejected after approval if permissions, the current publication or required dependencies changed. Approval is an editorial decision, not a promise that later publication checks will be bypassed.

A private preview expires after 30 minutes and is not transferable to an anonymous colleague. Create a fresh preview while signed in if it expires. If the queue looks empty, clear the state/search filters, inspect later pages and confirm your resource access. No matching reviews and no permission to see someone else's review are different situations.

Sources: Review and schedule screens; Overview and workflow queries; Content and publication service.