Versions & history

Every dashboard keeps a running history of its own changes. Nothing you save is ever the only copy — you can always see what a dashboard looked like earlier, and bring any of those versions back.

Automatic versioning

A dashboard's version number starts at 1 and increases by one every time it's saved — the same convention used by tools like Grafana. There's no separate “publish a version” step to remember: editing panels, moving them around, or changing a query and clicking Save is what creates the next version.

Version history

The catalog's History link opens a full list of a dashboard's saved versions, newest first: when each one was saved, who saved it, and how many panels it had. The current version is marked separately, since restoring onto itself wouldn't do anything.

The last 20 versions are kept per dashboard — enough to recover from a recent mistake without the history growing without bound on a dashboard that's edited often.

Restoring a previous version

Clicking Restore on any past version brings its panels and layout back — after a confirmation, so it's never one accidental click. Restoring doesn't erase anything: it saves the old version's content as a brand-new, later version, the same way any other edit would. That means:

• The version you restored from is never lost — it's still in the history, one entry down.
• Restoring is always reversible: if a restore turns out to be the wrong call, restoring again undoes it the same way.

What isn't part of version history

Who is allowed to see a dashboard (see Access & permissions) is saved separately from its panels and isn't recorded as a version — changing who can view a dashboard isn't a content edit, so it doesn't bump the version number or show up in History.