Whenever you save a change to a document's content, the previous version is archived automatically. You can browse, preview, and restore any past version from the document's history. Versioning runs only on content changes — renaming, retagging, or relinking a document doesn't create a version.
What you can do
Open a document's history to see a timeline with the current version plus every archived version, newest first. Open any archived version to view its content read-only, with a Restore button to bring it back.
When versions are created
When you save a document, Ceum compares the new content to what was stored. If they differ, the content as it was before this save is archived, and only then is the document updated. If they're the same — or you only changed details like the name, description, client, project, or tags — no version is created.
This keeps the archive lean: it captures real content history, not bookkeeping noise.
What's kept per version
Each archived version contains:
- Content — the full Markdown text as it was before the next edit replaced it.
- Content length — used in the timeline.
- When it was current — the last-updated time the document carried while this content was live.
- When it was archived — when the next save replaced this content.
Versions don't record who made the change — there's no actor on a version. If you need authorship-level history, use the document's comment trail; this archive is content-only.
The history timeline
The timeline shows:
- The current version at the top, labeled "Current Version" (no actions).
- Archived versions below, newest first. Each row shows when it was archived, when it was current (hidden on narrow screens), and Preview and Delete actions.
There's no side-by-side diff — versions are shown as standalone snapshots. To compare, open two versions in two tabs.
Restoring a version
Open an archived version and use Restore. Restore works like a normal save that writes the archived content back to the document. Because the document's current content differs from the archived content at that moment, the current content is archived first. The history therefore always grows, and restoring is non-destructive.
Deleting a version
Each archived row has a Delete action that removes just that snapshot from the timeline. The current version can't be deleted from the timeline — to remove the live document, delete the document itself, which also removes all of its archived versions.
Tips and edge cases
- Two caps keep the archive bounded, and the tighter one wins. Ceum keeps the newest 50 archived versions per document, so older snapshots fall off as new ones are added. On top of that, an archived version is kept for a window set by your plan — 7 days on Free, 30 on Starter, 90 on Plus, 365 on Pro — and is removed once it is older than that, even if the document has nowhere near 50 versions. See Data retention. You can also delete individual snapshots yourself.
- Restore is a save. It creates one new archived version, since the live content is replaced.
- Editing details never adds to the history. Changing tags, name, description, or links won't appear here.
- Edits made through an integration behave the same. A content change made through an integration still archives the previous version.
On mobile
Not available on the mobile app — manage from the web app. The mobile app shows a document's current content but doesn't expose version history or restore.