The flow replayed with sample data. Use ↻ to play it again.
Content moves Draft → signed preview → exact-version review → publish. Approvals bind to the precise version queued for publish.
Because approval binds to a specific version, there is no risk of content being swapped after review and publishing something no one signed off on. The signed preview shows reviewers the exact finished result, so decisions rest on the real thing rather than a guess.
AI review scoring assists with quality signals, and because only the reviewer and admin roles can approve, ownership of every release is clear.
- From draft to signed preview
- Review the exact version that ships
- Approvals bind to the exact version
- AI review scoring assists with quality
How it works
- 1Open the review queue and pick a draft that is pending review.
- 2Check the signed preview, the AI review verdict and the quality findings.
- 3Confirm that publish-blocking items such as critical SEO issues, encoding problems and missing citations are resolved.
- 4Approve the exact version and schedule approved articles into a publishing slot. If it needs more work, withdraw approval and send it back to draft.
FAQ
What happens if content is edited after approval?
Approval is bound to a version, so any edit after approval needs to be reviewed again.
Which roles can approve?
Reviewers and admins approve. Creators draft, edit and submit for review.
Can an approval be withdrawn?
Yes. Withdrawing approval sends the article back to pending review or draft, and it must be reviewed again.