> For the complete documentation index, see [llms.txt](https://docs.nested-knowledge.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.nested-knowledge.com/your-nests/nest-versions.md).

# Nest Versions

Learn how to save nest versions and restore them at a later date.

Save a nest version before a significant change or at a project milestone. A saved version lets an admin create an editable copy of the nest as it existed at that time.

{% hint style="info" %}
**Versions can only be saved manually.** A version includes work saved when you create it. Later changes aren't reflected in that version.
{% endhint %}

### Saving A Version

1. In **Settings**, scroll to **Nest Versions**.
2. Select **Save a Version**.

After you save a version, it shows the date and time, record count, included record count, and **Synthesis Version** checkbox. To edit the **Version Name**, select the pencil icon.

{% hint style="warning" %}
You can only save a version at the present time. You cannot save a version from a past date.
{% endhint %}

<figure><img src="https://305208404-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fxb7uNGATUgwQAjDVQRXG%2Fuploads%2F3jj2RVHN5Hzij7p2wC0X%2FNest%20versions.png?alt=media&amp;token=aa4b8efb-c753-40e2-8b72-41089e1a6df3" alt="The Nest Versions section in Settings, showing saved versions with their names, dates, record counts, and Synthesis Version checkboxes."><figcaption><p>Saved nest versions in <strong>Settings</strong>.</p></figcaption></figure>

### Synthesis Versions

Each saved version includes **AutoLit** and **Synthesis** data. To keep the nest's **Synthesis** display at a saved state while you update the nest, select that version's **Synthesis Version** checkbox.

If you don't select a **Synthesis Version** checkbox, **Synthesis** updates as the nest changes.

### Restore A Copy

A saved version remains in **Settings** until you delete it.

{% hint style="danger" %}
**Deleting a version can't be undone. Once deleted, you can't restore a copy of that saved nest version.**
{% endhint %}

To restore a version, create a copy of the saved nest:

1. Select **Restore Copy**.
2. In the dialog, enter a name for the copy.
3. Select **Create**.

**AutoLit** opens the new nest copy.

You can always generate a copy of the nest in its current state in [Nest Settings.](/your-nests/nest-settings.md#copy-rename-and-delete-a-nest)

### When To Save A Nest Version

Save a version before a significant change to your nest. For example:

* Changing **Settings**, such as screening modes
* Applying a bulk action that might not be reversible
* Deleting searches, exclusion reasons, or tags
* Changing the tag hierarchy or study design

You can also save versions at regular project milestones.


---

# 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.nested-knowledge.com/your-nests/nest-versions.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.
