Overview
Review workflows add an editorial approval step to the content publishing process. When enabled, posts must be reviewed and approved before they can be published, ensuring content quality and consistency across your blog.
Enabling Reviews
Review workflows are configured per blog. To enable reviews:
- Navigate to your blog's Settings
- Find the Review Workflow section
- Toggle Enable Reviews to on
- Save the settings
When reviews are enabled, Authors can no longer publish posts directly. Instead, they submit posts for review, and users with the Reviewer or Admin role approve or reject them.
The Review Process
Step 1: Submit for Review
When an Author finishes writing a post, they click Submit for Review instead of Publish. The post's status changes from Draft to InReview.
Step 2: Reviewer Assignment
Admins or Editors can assign specific reviewers to a post. Assigned reviewers receive a notification and can see the post in their review queue. Any user with the Reviewer or Admin role can also review unassigned posts.
Step 3: Review
Reviewers read the post and provide feedback:
- Review comments — Add inline feedback and suggestions for the author
- Approve — Mark the post as approved for publication
- Request changes — Send the post back to the author with comments
Step 4: Revision (if needed)
If changes are requested, the post returns to Draft status. The author can see the reviewer's comments, make the requested changes, and resubmit for review.
Step 5: Publication
Once approved, the post can be:
- Published immediately by an Editor or Admin
- Scheduled for future publication
- Held in approved state until the right time
Roles in the Review Workflow
| Role | Can Submit | Can Review | Can Approve | Can Publish |
|---|---|---|---|---|
| Author | Yes | — | — | — |
| Editor | Yes | — | — | Yes |
| Reviewer | Yes | Yes | Yes | — |
| Admin | Yes | Yes | Yes | Yes |
Note that Reviewers can approve but not publish. This separation ensures that publication timing remains in the hands of Editors and Admins, while Reviewers focus on content quality.
Review Comments
Review comments allow structured feedback on a post:
- Reviewers can add comments with specific feedback
- Authors can see all review comments when revising
- Comments persist through revision cycles, creating a history of editorial feedback
- Comments are internal and never visible to public readers
Best Practices
- Assign specific reviewers for domain expertise — technical posts should be reviewed by technical team members
- Set clear review criteria so reviewers know what to check (accuracy, tone, formatting, SEO)
- Keep review cycles short — aim to review within 24-48 hours to maintain publishing momentum
- Use review comments constructively — provide specific, actionable feedback rather than vague suggestions
Without Review Workflows
When review workflows are disabled (the default), Authors, Editors, and Admins can publish posts directly without an approval step. This is suitable for smaller teams or blogs where speed is prioritized over editorial oversight.