Every save keeps a full copy of the record. Nothing to switch on — it works on every content type.
The timeline
Open the editor’s History tab. Since 0.12.0 it is one timeline, newest first and grouped by day (Today, Yesterday, then the date): the record’s versions, and between them what happened to it — created, published, unpublished and so on, with who did it. All, Versions and Activity above the list choose what it shows; a line beside them counts the versions and events.
Each version is a row — v3, Saved version 3, its time — with a badge:
| Badge | Means |
|---|---|
| Live | The version the live site shows. It keeps the badge while newer drafts pile up above it, until another version is published or the entry is unpublished |
| Draft | Saved, never published |
| Superseded | Was live; another version replaced it |
- The newest version is also marked Current draft. After you publish an older version, Live and the current draft are on different rows.
- Saving a published entry adds a Draft on top; the Live version below it stays on the site until you publish again.
- On a translated type, each language has its own timeline.
- History lives only in this tab — the properties panel has no copy of it. The record’s old activity address opens it showing activity.
Comparing
Beside the list, the selected version is compared with the current draft: how many fields differ, and each changed field as the version’s value struck through over today’s. Click a version to select it; until you do, the one before the newest is selected. The comparison carries the version’s actions — Preview, Restore and Publish this version.
- Click Preview for the full field-by-field diff against the current version.
- Tick Hide unchanged to fold untouched fields.
- With segments installed, the preview also shows Who can read this — audiences are saved with each version.
- Going from empty to
""is not shown as a change. - Reordering linked records is a change.
- Linked records show their titles. One since deleted or moved away shows as Unavailable record (or Unavailable asset).
Restore versus publish
| You want | Use | What happens |
|---|---|---|
| Old content back, and keep editing | Restore | A new Draft on top, identical to the old version. Nothing is rewritten |
| An old version live now | Publish this version | That version becomes Live; the previous Live becomes Superseded. No new version is added |
After publishing an older version, the newest is not the live one
Publish v2 while v5 exists: v2 is Live, v5 is still the Current draft on top. That is correct — your next save puts a version matching the live content back on top.
Publishing a version runs the publish gate. If it fails, the content stays applied as a Draft — nothing is half-done.
On a translated record, an old version can carry shared values or synced links that differ from today’s. Restoring or publishing it would then change the other languages too, so since 0.11.0 the editor asks first, with the same preview a save shows — see what else a save changes. Its button reads Restore or Publish, or Save anyway if a published language would be left incomplete.
Who can do what
| Action | Needs |
|---|---|
| View the timeline and a version | content:read |
| Restore a version | content:update |
| Publish a version | content:publish |
Records shared from another workspace have their history in their own workspace.
What it does not do
History is append-only, and never pruned
Versions cannot be edited or deleted, and nothing trims them. Permanently deleting an entry removes its history with it.