What Snapshots Capture
A snapshot preserves your complete model state:Accessing Snapshots
The snapshot manager is located in the model header toolbar:- Open your model
- Click the clock icon in the tab header
- The snapshot dropdown shows your version history
- Today
- Yesterday
- Last 7 days
- Last 30 days
- Older

Creating Snapshots
Create a snapshot to save the current state of your model before making significant changes.- Click the clock icon in the tab header
- Click New Snapshot
- Optionally enter a descriptive name (e.g., “Before restructure” or “CDR baseline”)
- Press Enter or click the checkmark to confirm
When to Create Snapshots
Create snapshots before:- Major architectural changes
- Deleting parts or requirements
- Design reviews or milestones
- Experimenting with different approaches
- Handing off to another team member
Restoring Snapshots
Restore your model to a previous snapshot state.- Click the clock icon in the tab header
- Find the snapshot you want to restore
- Click the restore icon on that snapshot
- Confirm the restore in the dialog
What Happens During Restore
When you restore a snapshot:- All model elements are replaced with the snapshot version
- Documents and files are restored
- Action scripts are restored
- The current state is overwritten (not merged)
Managing Snapshots
Rename a Snapshot
- Click the clock icon to open the snapshot dropdown
- Click the edit icon on the snapshot you want to rename
- Enter the new name
- Press Enter to save
Delete a Snapshot
- Click the clock icon to open the snapshot dropdown
- Click the delete icon on the snapshot you want to remove
- The snapshot is permanently deleted
Deleting a snapshot is permanent and cannot be undone. The snapshot data is removed from storage.
Automatic Snapshots
Dalus may create automatic snapshots in certain situations:- Copilot checkpoints — Created before AI-assisted changes so you can revert if needed
- Migration backups — Created during system updates
Best Practices
- Snapshot before major changes — Always create a named snapshot before restructuring your architecture or deleting significant content.
- Use descriptive names — Names like “Pre-CDR baseline” or “Before port refactor” are more useful than timestamps alone.
- Regular checkpoints — Create snapshots at natural milestones—end of day, before reviews, after completing features.
- Don’t rely solely on snapshots — For formal version control, also use Model Export to create external backups.
- Clean up old snapshots — Delete snapshots you no longer need to keep your history manageable.
Permissions
Snapshot management follows model permissions:
Viewers cannot access the snapshot manager. Only team members with edit permissions can create, restore, or manage snapshots.