# Revisions

Every change you make to a template is saved as a revision. That means you can experiment freely, knowing you can always get back to a working version. No change is permanent unless you want it to be.

## What gets tracked[​](#what-gets-tracked "Direct link to What gets tracked")

Every time you save, Allegro creates a new revision automatically. Each revision stores:

* A full snapshot of the content at that moment
* Who made the change
* When it happened
* An optional note describing what changed

Revisions are numbered starting from 1. The first save after creating a template is revision #1.

## Viewing history[​](#viewing-history "Direct link to Viewing history")

Open a template and click the **History** tab. You'll see every revision listed newest-first — the revision number, who made it, when, and any note that was attached.

## Adding notes[​](#adding-notes "Direct link to Adding notes")

You can attach a note to any save to explain what you changed and why. Notes are optional, but they're worth adding for anything meaningful — a bug fix, a new section, a major rewrite.

Use notes for team communication

Think of revision notes like commit messages. A short note such as "Updated pricing for Q3 launch" saves your teammates from having to diff two versions to understand what happened.

## Rolling back[​](#rolling-back "Direct link to Rolling back")

Made a mistake? Restore any previous revision:

1. Open the template's **History** tab.
2. Find the revision you want.
3. Click **Restore**.
4. Optionally add a note explaining why you rolled back.

A rollback creates a **new revision** — it doesn't erase history. That means you can always undo a rollback, too. Restored revisions are labeled **\[RESTORE]** in the history so you can tell them apart.

## Permissions[​](#permissions "Direct link to Permissions")

Revision access follows the template. If you can view a template, you can view its full revision history.

Revision limits

Templates keep unlimited revisions by default. If a maximum is configured (for example, keep the last 20), the oldest revisions are pruned automatically. Revisions that were used as the source of a rollback are never pruned, so the audit trail for restores is always preserved.

## Related[​](#related "Direct link to Related")

* [Templates](/product/interactions/templates.md) — the primary content type that uses revisions
* [Interactions](/product/interactions.md) — interactions also track revision history