Open version history from the **status chip** in the editor header —
the one that says whether you have unpublished changes. It lists every
version with its number, title, who published it and when.

Each version offers five things, in order of how much they touch.

## Its own link

A link that always opens that version, however many times you publish
afterwards. See [Sending a class to one
version](/support/articles/sending-a-class-to-one-version).

## Preview

Opens that version in a new tab, exactly as a learner received it.
Changes nothing, and is the sensible first move before pressing any of
the rest.

## Serve this version

Re-points the plain share link at that version for everybody, until you
change it again. Your draft is untouched.

## Copy to new

Writes that version out as a **new experience** in the same workspace
and leaves this one exactly as it was. This is the safe way to pick up
an older direction without losing the current one.

## Restore

Replaces your working draft with that version, discarding anything
authored since. It is the only destructive control here, and the only
one that asks before it runs.

One consequence is worth reading twice: **scenes come back as new
ones**, so attempts learners have already taken will no longer line up
with them. Restore is for recovering a direction, not for correcting a
live assessment.

> Both start from an old version. One writes over your draft; the other leaves everything alone.

## "Published before restoring was possible"

Restoring and copying both read the authored snapshot taken at publish
time. Versions published before those snapshots existed do not carry
one, so both controls are unavailable on them.

They cannot be rebuilt from the learner's copy instead: that copy never
contained your author-only contexts, so a draft rebuilt from it would
quietly delete the content you chose to keep back.