Hi team,
We’re running a multi-market DatoCMS project where a single record is shared across many locales, with different editors owning each locale(market). We’ve hit a recurring governance problem around the revision history feature that I think would benefit the wider community too.
The problem
Revisions are stored at record level, which means restoring a past revision restores the entire record, across every locale, not just the locale the editor was looking at. In a setup with many markets and many collaborators, a single editor clicking “restore” can silently roll back content for every other market on that record.
We’ve already seen real-world incidents of this on our project, and the current mitigation is a strongly-worded “do not revert pages” internal policy. That’s not a great control to rely on at scale.
What I’d like to see
A new permission, something like:
Can restore content to an earlier state (record versioning)
Behaviour when turned off:
- The restore option is hidden in the DatoCMS UI
- The corresponding CMA endpoint rejects restore calls for that role
- Viewing revision history is still allowed (so editors can see what changed), just not restoring
Default: on, to preserve current behaviour for existing projects.
Happy to share more context on our setup if useful.
Thanks!