Snapshots: getting back a good version
Manual restore points, so a bad edit is never permanent.
A snapshot records the dashboard's published state at a moment you choose, so you can return to it.
Why manual
Snapshots are created only when you press the button. They are not tied to autosave — that fires constantly, and a snapshot for every autosave would produce hundreds of entries for moments nobody chose. Every snapshot means something to the person who made it.
Restoring
Restoring replaces the current published state with the saved one — pages, visuals, layout and formatting.
Restoring takes a snapshot first, automatically, so the restore itself can be undone. Changing your mind is always possible.
What a snapshot does not include
- Data. It records the dashboard, not the rows. Restoring an old layout does not bring back old data.
- Sharing settings. Visibility is not rolled back, deliberately — quietly re-opening a dashboard that was since made private would be a security problem, not a convenience.
If a dataset was deleted since the snapshot was taken, restoring succeeds and the visuals that used it show their usual "dataset missing" state.
Retention
A limited number are kept per dashboard, and the oldest is dropped to make room. Pin the ones that matter — "before the Q3 rebuild" — and they are exempt.