> For the complete documentation index, see [llms.txt](https://docs.tonic.ai/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.tonic.ai/textual/manage-dataset-settings/dataset-version-history.md). # Viewing and restoring dataset versions Tonic Textual tracks each change to the dataset configuration. You can view the list of changes to the dataset configuration, and revert the dataset configuration to a selected version. ## Displaying the dataset version history To display the version history, click the clock icon at the top right of the dataset details page.

Version history icon to display the dataset version history

The **Version history** panel lists the versions in descending order, with the current version at the top of the list.

## Displaying details for a version For each version, the **Version history** list initially displays: * A summary description of the change. * The timestamp when the change occurred. * The name of the user who made the change. To display additional details about the change, expand the version description. For example, for a change to the handling option for an entity type, the details include the entity type, the previous handling option, and the new handling option.

Expanded details for a version in the Version history

## Restoring a version You can restore an earlier version of the dataset. When you restore a version, Textual reverts the changes that occurred since that version. On the expanded description of a version, to restore that version, click the **Restore to \** button. Textual adds a version to the history. The new version is marked as **Restored**, and the description indicates the version that you restored.

The expanded details for the version list the changes that Textual reverted when you restored the earlier version.

--- # 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.tonic.ai/textual/manage-dataset-settings/dataset-version-history.md?ask=&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.