Deleted by mistake? How CMS Orbit lets you undo it

Everyone deletes the wrong thing eventually. A page that looked unused turns out to be linked from a campaign. A well-meant edit replaces the paragraph legal approved. An assistant's draft goes further than anyone intended. What matters is how quickly you can put it right, and whether anything is lost for good along the way.

CMS Orbit is built so that ordinary mistakes are easy to undo, and permanent ones are rare, deliberate and recorded.

Nothing is deleted straight away

Deleting a page, entry, file or even a whole space moves it to the bin. Open Library › Bin, find it and choose Restore. A page comes back as a draft at its old address, or you're asked for another address if that one has been taken in the meantime. You can delete several pages at once by ticking them in a list, and restore them just as easily.

Every published version is kept

Each publish, promotion and rollback keeps a version of the page. In the page editor, Version history lists them with what happened and when, and any note added at the time.

• Compare side by side: See the old version and your draft next to each other, both on the real website, on desktop or phone.
• What changed: A list of every field and block that differs, including the search title and description, which don't show on the page itself.
• Restore: Make the draft match an older version and publish it as usual. Restoring adds a new version rather than removing any, so you can always go back again.

Starter shows the last 30 days of history and Growth the last 365; Enterprise shows everything. Older versions aren't deleted on the smaller plans. They're kept, and appear again after an upgrade.

Only the Owner can erase for good

Permanent deletion is a decision, not an accident. Only the organisation's Owner can erase something for good, from the organisation's bin, and the audit trail records who did it and when. A space can also empty its bin by itself after 30, 60 or 90 days, if you choose that in its settings.

Two things skip the bin, and only Administrators and Owners can delete them: releases, and claims that no page uses. If you might want a claim back, archive it instead.

Every action leaves a trail

Restores, rollbacks and erasures all appear in the audit trail, with the person or AI agent that made them. Restoring an earlier version needs a permission that editors and the roles above them have by default, so you decide who can turn back the clock. See reviews, approvals and an audit trail for how the rest of the record works.

And behind it all, backups

Beneath the bin and version history, the platform's database is backed up to encrypted, versioned storage in Ireland. Those backups are for disasters, not everyday mistakes, which is why the bin and version history exist. When you erase personal data for good, it leaves the backups within 14 days.

Read more

The docs explain the bin and restoring and version history step by step, and our security page covers where your data lives and who can reach it.