Overview
The content review process is an editorial workflow that ensures posts meet quality standards before publication. Unlike comment moderation (which handles reader-submitted content), content review applies to posts authored by your blog team members.
How Content Review Works
When review workflows are enabled on a blog, the publishing process adds an approval step:
- Author writes a post and saves it as a Draft
- Author submits for review — the post moves to InReview status
- Reviewer evaluates the content and either approves or requests changes
- If approved — an Editor or Admin can publish the post
- If changes requested — the post returns to Draft for revisions
This cycle repeats until the post is approved and published.
Assigning Reviewers
Reviewers can be assigned to specific posts for targeted editorial feedback:
- Open a post that is in InReview status
- Navigate to the Review panel
- Select a reviewer from the list of blog members with the Reviewer or Admin role
- Save the assignment
Assigned reviewers see the post highlighted in their review queue. While any user with review permissions can review any post, assignments help distribute the workload and ensure subject matter experts review relevant content.
Review Actions
When reviewing a post, a reviewer can take the following actions:
Approve
The reviewer confirms the post meets publishing standards. After approval, the post can be published by an Editor or Admin, or scheduled for future publication.
Request Changes
The reviewer identifies issues that need to be addressed. They should add review comments explaining what changes are needed. The post returns to Draft status, and the author can see the feedback.
Add Comments
Review comments provide structured editorial feedback:
- Comments are visible only to blog team members, never to public readers
- Multiple comments can be added during a single review
- Comments persist through revision cycles, building a review history
- Authors can read and respond to comments before resubmitting
Review Permissions
Not all blog roles can participate in the review process:
| Action | Author | Editor | Reviewer | Admin |
|---|---|---|---|---|
| Submit for Review | Yes | Yes | Yes | Yes |
| View Review Queue | — | Yes | Yes | Yes |
| Add Review Comments | — | — | Yes | Yes |
| Approve Post | — | — | Yes | Yes |
| Request Changes | — | — | Yes | Yes |
| Publish Approved Post | — | Yes | — | Yes |
The deliberate separation between "can approve" (Reviewer) and "can publish" (Editor/Admin) provides checks and balances in the editorial process.
Managing the Review Queue
The review queue in the dashboard shows all posts currently in InReview status:
- Post title and author — Identify what needs review
- Submission date — Track how long posts have been waiting
- Assigned reviewer — See who is responsible
- Review comments — View the feedback history
Filter the queue by assigned reviewer or submission date to manage your workload efficiently.
Disabling Review Workflows
If your team does not need editorial oversight, you can disable review workflows in blog settings. When disabled:
- Authors can publish posts directly (if they have sufficient permissions)
- The InReview state is skipped in the post lifecycle
- The review queue is hidden from the dashboard
You can re-enable review workflows at any time without affecting existing published posts.