Approvals before publish
Set who must sign off before content goes live, so the wrong version never reaches a reader. Approval and publishing are off by default for new projects until you turn them on.
Review & WorkflowsQuality, approved.
Quality, approved.
Every version, tracked.
Draft, review, approve, publish, with role-based permissions and full version history. Nothing goes live until the right people sign off.
Approval flows Version history Role-based publishing
How it works
From draft to published, with sign-off
A clear path for every change, and a record of every decision.
1. DraftWrite or edit a page, alone or together, with autosave.
2. Request reviewSend it to the right approvers when it’s ready.
3. ApproveReviewers comment, request changes, or sign off.
4. PublishOnly approved versions go live, tracked in history.
Trust & control
Approved content only. No surprises.
Govern publishing without slowing your team down.
Full version history
Every change is tracked. See who changed what, compare versions, and roll back with confidence.
Roles & permissions
Give each teammate the right level of access (author, reviewer, publisher), so collaboration stays safe at scale.
FAQ
Common questions
Is approval required to publish?
It’s your choice. Approval and publishing controls are off by default for new projects; turn them on to require sign-off before any page goes live.
Can I see who changed what?
Yes. Full version history records every edit with the author and timestamp, so you can review, compare, and roll back to any previous version.
How do roles work?
Role-based permissions let you separate authoring, reviewing, and publishing, so teammates only have the access appropriate to their role.
Does review slow teams down?
No, it scopes review to what matters. Low-risk edits can flow quickly while sensitive pages require sign-off, keeping speed and control in balance.