Use version history and restore safely

Name milestones, inspect automatic entries, and understand that restore replaces the current document state.

What history contains

Version history lists automatic and named project snapshots. A version can have a name, description, author, and timestamp. Naming important milestones makes the list useful: “Imported FDX cleanup,” “Producer notes pass,” or “Episode 4 locked outline” is clearer than relying on dates alone.

Restore is a document-level operation

Restoring does not cherry-pick one paragraph. It brings the project's collaborative document back to the selected snapshot and asks for confirmation. In Script projects, the restore path checks episode compatibility and restores both screenplay and project entities. Cinema uses its own full-document reconciliation so entities added after the snapshot do not incorrectly survive.

A safe restore workflow

1. Stop broad team edits and tell collaborators what you are doing.
2. Export or name a version of the current state if it might be needed.
3. Select the intended snapshot and read its name, author, and date.
4. Confirm the restore and wait for the project to reconcile.
5. Inspect representative episodes, entities, and views before continuing.

A historical entry can be renamed or deleted if you have authority. Deleting history metadata should be treated as irreversible from the interface.

History is not external backup

Keep delivery exports for legal, archival, or external workflow needs. Version history is optimized for project recovery and creative comparison inside Laper; it does not synchronize edits made in an exported DOCX or FDX back into the project.