# Version history

Available for: ![](/files/gJobc6jemFp7saUYNiKJ) Governance Plan

Smaply automatically saves **versions** of your journey maps every 10 minutes. This makes it easy to review past changes and restore previous versions if needed. 

***

### How it works

* You'll find **auto-saved versions** in the version history panel in the top-right corner of the journey editor.
* Clicking on a version opens a **read-only view.**
* To work with that version, click **"Restore"** — this creates a **new working version**, leaving the original unchanged.
* The restored version opens in a new tab so you can continue editing from there.

<figure><img src="https://lh7-qw.googleusercontent.com/slidesz/AGV_vUee_0mkeG_LtXf3XnyipFQhf0agqTNWi8SudG-NOkyFSAUg2snqqzQS-2weZPGwPqcsN58cQ0JAGUFsIXd-qdR_LNawC-v8WRiYRCFQW_kfM8B_INn5Rv5GmH-pQMk3KzREhpBT=s2048?key=B3fBiVmjXo9DHK_BYOJMXg" alt="" width="375"><figcaption></figcaption></figure>

***

### What is (and isn’t) saved in a version

Only the content of the **journey map** itself is stored in each version.\
**Linked items** (e.g., metrics, personas, portfolio items) are **not** part of the version and will appear as they are **today**, not as they were when the version was saved.

{% hint style="warning" %}
This means the version gives you a snapshot of the journey map layout and content, but not of linked items.
{% endhint %}

***

#### Elements not stored in version history:

* Portfolio items
* Content of metric cards (metrics themselves)
* Content of embed cards
* Content of planning cards
* Personas
* Tags

***

### Tips

* If you’re working on major changes, consider restoring and renaming a version before editing — this makes it easier to track.
* Use versioning like a safety net: it’s there in the background, quietly backing you up.


---

# Agent Instructions: Querying This Documentation

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

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://helpdesk.smaply.app/journey-editor/version-history.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.