Documentation
Content history & revisions
Every entry keeps a timeline of past versions. gluso snapshots an entry when you publish and when you save a draft, so you can look back at what changed, who changed it, and roll back to an earlier version — without ever losing your place.
When a version is saved
Versions are captured on the actions that matter — not on a timer, and not on every keystroke:
| Publish | Always records a Published version — the canonical snapshot of what went live. |
| Save draft | Records a Draft saved version — unless nothing changed since the last one (identical saves are skipped, so the timeline stays clean). |
Each version stores the entry's field values plus a snapshot of the field layout at that moment, so an old version still reads correctly even after you rename or remove fields later.
Viewing an entry's history
Open any entry and select the History tab in the right-hand panel. Versions are listed newest-first, each showing who made it, when, and whether it was a publish or a draft save. Select one to see which fields changed compared with your current draft.
Restoring a version
Expand a version and choose Restore to draft. This loads that version's values back into your working draft so you can review them — nothing goes live until you Publish yourself.
Restoring is non-destructive: it records a new version rather than deleting anything, so your forward history is always preserved and you can undo a restore by restoring a later version.
Retention
gluso keeps the most recent versions per entry and expires very old ones automatically, so history never grows unbounded. Restore and diff always work against the versions currently retained.
Who can see history
- History contains draft content, so it's available to owners, admins and editors — the same people who can author the entry. View-only guests don't see it.
- History is scoped to your space; there's no way to read another space's versions.
- The public content API only ever returns published content — draft versions and history are never exposed through it. See the API reference.