> For the complete documentation index, see [llms.txt](https://docs.groundcover.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.groundcover.com/investigate/dashboards-and-alerts/dashboard-version-history.md).

# Dashboard Version History

Every save to a dashboard creates a new revision. Use Version History to review past changes, compare them against the current version, and recover from an unwanted edit — without duplicating the dashboard or relying on Terraform state.

## Opening Version History

1. Open the dashboard.
2. From the **Actions** menu, select **Version History**.

A panel opens showing every revision, grouped by date, most recent first.

## Reviewing a revision

Select any revision in the list to preview a diff against the dashboard's current state — added, removed, and changed widgets are highlighted.

## Restoring a revision

From a previewed revision, choose **Restore** to make it the dashboard's current version. Restoring creates a new revision on top of the history rather than deleting anything, so you can always go back further if needed.

## Exporting a past revision

A revision doesn't have to be restored to be reused. Choose **Export** on any revision to get its JSON (or Terraform, see [Managing Dashboards with Terraform](/investigate/dashboards-and-alerts/managing-dashboards-with-terraform.md)) without changing the dashboard's current state — useful for diffing a past layout or pulling an old widget's query.

{% hint style="info" %}
For dashboards managed by Terraform, Version History is a good first check before assuming a change needs to be re-applied from code — a revision may already contain what you're looking for.
{% endhint %}


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.groundcover.com/investigate/dashboards-and-alerts/dashboard-version-history.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.