Core Workflow
History, milestones, and restore
See what changed, keep important versions, and recover an earlier workspace safely.
Documentation, Structure, and Pages each have a History panel. Open the workspace, wait for Saved, then select History in the main project header.
History records saved changes and who made them. Named milestones keep important versions beyond the normal working-history window. Restoring creates a new change in the timeline rather than erasing what happened afterwards.
Review what changed
- Open History and choose All changes or Milestones.
- Select an entry to see its author and time.
- Use Changes since this version to compare that saved version with the current workspace.
- Choose View saved document, View saved layout, or View saved pages to inspect the saved content itself.
The comparison shows the Saved version in red and the Current version in green. It highlights additions, removals, and changed content. It compares the selected version with the current state; it is not a record of only the single edit named in that timeline entry. Layout or other property changes may require opening the saved view to inspect them.
Continuous edits can roll into one history entry, so the timeline does not list every keystroke or autosave. A change of editor, a milestone, a restore, or a new editing period can create a separate entry. Reviewing a version fixes that entry so subsequent edits do not change the version you inspected.
Save a named milestone
Save milestones for moments such as Brief approved, Structure signed off, or Before content revision.
- Finish editing and wait for Saved.
- Open the relevant workspace's History.
- Enter a name in Name a milestone… and select Save milestone.
- Use Milestones to find it again.
A milestone saves the current state of that workspace. It is not one combined snapshot of the entire project. For a project-wide approval, save a milestone in each relevant workspace, using matching names if helpful.
Retention and storage
| History type | How long it remains available |
|---|---|
| Automatic saved versions, including pre-restore recovery points | 30 days for preview and restore. |
| Audit records | One year; after the saved content expires, the entry is labelled Audit record only. |
| Named milestones | No time expiry while protected, within the milestone allowance. |
Each workspace's History panel shows its milestone count and storage usage: up to 25 milestones and 64 MB of saved milestone content. When an allowance is full, remove protection from an unneeded milestone before saving another.
Select a milestone and choose Remove milestone to remove its protection. The normal 30-day policy applies from its original creation date, not the removal date. An older version may therefore become unavailable immediately. Removing protection does not change the current project.
History is not an unlimited backup of every intermediate edit. An expired audit record cannot be previewed or restored. Archiving a project does not pause these retention rules.
Understand restore scope
A restore affects the selected workspace, not just the item shown in the comparison.
| Restore from | What is restored |
|---|---|
| Documentation | The whole document, including sections, rich text, palettes, typography, references, and checklists. |
| Structure | The combined graph of pages, journeys, architecture, connections, and layout. Page composition content is retained. |
| Pages | Page composition and the shared Section library together. Structure graph content and positions are retained. |
Restoring can replace teammates' later changes in the same workspace. For a small correction, editing the affected content may be more appropriate than restoring the workspace.
Restore a version
- Tell active collaborators what you plan to restore and let them finish saving.
- Select the version and inspect both the comparison and saved view.
- Choose Restore this version.
- Read the scope shown in the confirmation, then select Confirm restore.
- Let the workspace reload and check the result and save status.
Skafold saves a Before restore recovery point first. The restore is recorded as a new history event, and later audit entries remain visible. If the result is wrong, inspect that recovery point and restore it through the same workflow while it is still available.
If someone changes the workspace after your preview was loaded, the restore can be rejected. Refresh History, select the version again, and review the updated comparison before trying again.
Other editors and unsaved work
After a restore, other open editors may pause and require a reload. Preserve or download any unsaved work before reloading. Do not blindly reapply an old draft over the restored content; inspect the latest state and carry across only the edits still needed.
Project viewers can inspect available history, but creating or removing milestones and restoring versions require edit access. Computer-use agents act under the signed-in account and appear in that account's normal history; there is no separate AI import history or automatic history group for a whole agent task.
See Collaboration and saving for conflicts and interruptions. After reviewing the restored plan, use AI Context → Update AI Context when available to publish it to trusted AI tools.