# Versions and history

> Every publish snapshots the blueprint, and restoring a snapshot replaces the current content.

Publishing writes a version. The **History** tab lists them, newest first.

> [!IMPORTANT]
> Version history is a **Teams** feature. Without a Teams-licensed
> organisation the tab explains that rather than opening. Publishing still
> snapshots, but the snapshots cannot be browsed or restored.

## What a version holds

A complete frozen copy of the blueprint at publish time: tabs, diagram sources,
strata and files. It is not a diff, so an old version renders as it did rather
than being reconstructed.

## Comparing

The panel offers four views of a version:

| | |
| --- | --- |
| Snapshot preview | The version rendered faithfully, as it was |
| Diff | What changed against the previous version |
| Compare with this version | Pick any earlier version as the baseline instead |
| Raw JSON | The snapshot itself, when the rendered view is not enough |

Diffing against the previous version answers "what did that publish change".
**Compare with this version** sets an older baseline and answers "what has
changed since the release we shipped against".

## Restoring

> [!IMPORTANT]
> Restore **replaces the current content**. It deletes and recreates the
> blueprint's tabs, strata and files from the snapshot, and anything you have
> not published since is gone. Confirming takes two clicks, and the second one
> says so.

History is append-only, so the state you replaced is itself still a version.
A restore you regret is undone by restoring the one before it.

## Pinning

An [embed](/foliums/blueprintr-user-guide/sharing/embedding-blueprints) can be pinned to
a version rather than tracking the latest. A blueprint quoted in a report then
stays as it was on the day it was quoted.