Skip to main content
Dashboard Versioning introduces a draft/publish model for dashboards and their widgets. Every change you make creates a draft that does not affect the version users are viewing. Saving promotes the draft to a new published version and preserves the previous version in history. Admins can revert to any prior version at any time. This guide walks you through the draft and publish flow, version statuses, and how to restore a prior version.

​
How it works

A continuous lifecycle process that lets admins safely modify analytics interfaces without impacting what users see in production until changes are published.

Create a draft

When you make any change to a dashboard, a draft is automatically created as an isolated copy of the current published version. The published version remains unchanged, and users continue viewing it normally. For changes that affect widget data (SQL, filters, visualization config), a draft is created only for the affected widget. Other widgets on the same dashboard are not touched. For layout-only changes (repositioning widgets), only a dashboard draft is created with no widget rows cloned.

Save and publish

Click Save to promote the draft to the new published version. The previously published version moves to history.

Manage version statuses

Every dashboard version exists in one of three statuses.

Revert to a prior version

Open the version history panel for the dashboard, find the version you want to restore, and confirm. The selected version becomes the new published version. Reverting creates a new version entry and history is append-only. Widget membership is restored exactly as it was in the selected version.
Multiple admins can maintain separate drafts simultaneously. If two admins try to publish from drafts based on the same version, the second publish is blocked with a conflict notice until the conflict is resolved. When viewers apply temporary filter changes, a session-only draft is created scoped to that session. These changes are never published and are cleaned up automatically.

​
Target users

Dashboard Versioning is available to:
  • Dashboard Admins: Create, edit, publish, and revert dashboard versions.
  • Support and Operations teams: Use version history to diagnose what changed and when without reconstructing issues from memory.
  • Viewers and Explorers: Can apply temporary filters without creating permanent versions or disrupting the published dashboard.

​
FAQs

Yes. Widgets are independently versioned. A change to one widget creates a new widget version for that widget only. Other widgets on the same dashboard are unaffected.
Dashboards gain versioning from the point this feature is enabled. Historical status prior to the release is not retroactively captured.
Each admin works in their own draft. The first to publish goes through. The second admin’s draft is flagged as a conflict and they must resolve it before publishing.
No. Viewer filter changes create a temporary session-only draft that is never published.
All published versions are retained. There is no automatic pruning in the current release.

​
Next steps

Understand domains

Explore how domains organize the data logic that powers your dashboards.

Domain Health

Monitor the readiness and accuracy of the domain your dashboards query against.