Reviews, approvals and an audit trail, built in
How CMS Orbit keeps content right: reviews on every plan, approval steps and review dates on Growth, approved claims, emergency publishing and a record of every change.
4 min read
On this page
For some organisations, a wrong word on a website is more than embarrassing. A retailer that overstates a product's safety, a lender that leaves out a condition or a brand that publishes an expired offer can face complaints, regulators or worse. These organisations need to know that the right people checked a page before it went live, and to prove it afterwards.
CMS Orbit builds those checks into publishing, so they happen as part of the work rather than in a spreadsheet beside it.
Send for review, on every plan
Any page can be sent for a second opinion, and some content types can only go live after an approval. To send one:
- Choose Submit for review.
- Pick reviewers, or leave it empty so everyone who can approve is told.
- Say what to look at, such as 'New results claims in the second section'.
- Leave Publish as soon as it is approved on if it should go live straight away.
Reviewers are told in CMS Orbit and in Orbit, and by email. An approval covers the exact version that was sent, so editing a page in review means sending it again. Nobody can approve their own changes.
Approval steps for content that needs sign-off
On Growth and Enterprise, a content type can require approval in steps, such as Product safety, then Legal, then Brand. Each region can have its own steps, and a step can be limited to one role, so only the product team can sign off the product safety step.
The record keeps who approved each step, their role and the version they approved. Publishing › Reviews shows each review as a trail of sign-offs: done, waiting and still to come.
Wording that must be exact
Claims and disclaimers are written once per region in a library, by the people allowed to, and placed on pages by key. Change the wording once and every page that uses it updates. Editors can't retype an approved claim with a small, risky change.
Other guards sit in the editor itself:
- Protected prices: Only people allowed to change prices and promotions can edit those fields.
- Locked brand components: Only the brand team can add, change or remove them, and a change can ask for a Brand sign-off.
- Consent on images: Before-and-after images can carry a consent reference, and a page with an image that lacks consent can't be published.
Review dates, so pages don't quietly go stale
A page that was right last year may not be right today. On Growth and Enterprise, content types such as product pages can carry a review-by date, every 3, 6, 12, 18 or 24 months. The owner is reminded a month before the date and again when it passes, and Mark reviewed sets the next date. Every change is recorded in the audit trail.
Emergencies without shortcuts in the record
Sometimes a notice must go up now, such as shops closing because of a storm. People with the emergency publish permission, which Administrators and Owners have, can publish a banner on every page straight away, skipping review and schedules. They must give a reason. Approvers are told, and the audit trail records who did it, why and what the banner's settings were before.
An audit trail for everything
Every change, approval and setting is recorded with who, when and what, in the organisation's audit log. When an AI agent makes a change, the log names the agent and the person it acted for.
Version history keeps every publish, promotion and rollback. Compare any version with your draft side by side on the real website, see exactly what changed and restore a version in one step. Restoring adds a new version rather than removing any, so you can always go back again.
| Plan | History shown | Approval steps and review dates |
|---|---|---|
| Starter | Last 30 days | Single review only |
| Growth | Last 365 days | Included |
| Enterprise | Everything | Included |
Older versions are never deleted because of the plan. They're kept and shown again after an upgrade.
Mistakes you can undo
Deleting a page, entry, file or website moves it to the bin, where it can be restored. Only the Owner can erase things for good, and erasing is recorded too.
Why it matters
Take an outdoor retailer. A new climbing harness page needs product safety sign-off for its safety claims, legal sign-off for its terms and brand sign-off for its design. In CMS Orbit, the page moves through those steps in order, each signed off by the right role. The safety claim comes from the library. The page gets a review date six months out. If a regulator asks next year who approved the claim and when, the answer is one click away.
See it for yourself
Read how governance fits together in the docs, compare plans, or start a 14-day free trial and send your first page for review.