Version Control
Track changes and maintain history for both editor documents and uploaded files.
The Documents app provides version control for all content types. Editor documents use snapshot-based versioning with commit messages, while uploaded files create new versions automatically when you upload a file with the same name.
Editor Documents
Saving Versions
Editor documents use snapshot-based version control. To save a version:
- Click the Save button in the toolbar (or press
Ctrl+S) - Enter a commit message describing your changes (optional)
- Click Save Version
Each save creates a new version entry in the version history.
Navigating Version History
Use the version navigation buttons in the toolbar:
- Undo Version (arrow left) - Step back to the previous saved version
- Redo Version (arrow right) - Step forward to a newer version
- History button - Open the Version History dialog to see all versions
When viewing a past version, a badge shows which version you're viewing.
Discarding Unsaved Changes
If you have unsaved changes you want to discard:
- Click the Discard button in the toolbar (appears when you have unsaved changes)
- Confirm the action
Your document reverts to the most recently saved version.
Uploaded Files
Creating New Versions
Upload a file with the same name to the same folder to create a new version automatically:
- Click the + button and select Upload Files
- Upload a file with the same name as an existing file
- When the duplicate warning appears, choose Continue and Create New Versions
The new upload becomes the latest version, and previous versions remain accessible in the history.
Uploading from the Properties Panel
You can also upload a new version directly from the properties panel:
- Open the uploaded file
- In the Properties tab, find the Version History section
- Use the Upload New Version button
Viewing Version History
For both editor documents and uploaded files:
- Open the document or file
- Open the Properties tab in the right panel
- Expand the Version History section
- See all versions listed with their details
Version Information
| Field | Editor Documents | Uploaded Files |
|---|---|---|
| Version Number | Sequential identifier (v1, v2, v3...) | Sequential identifier (Version 1, 2...) |
| Created Date | When the version was saved | When the version was uploaded |
| Author | Team member who saved the version | Team member who uploaded the file |
| Message | Commit message describing changes | -- |
| File Size | -- | Size of that specific version |
Best Practices
- For editor documents, save versions at meaningful checkpoints with descriptive commit messages
- For uploaded files, upload with the same filename to maintain a clean version chain rather than creating separate files
- Use the Activity section to add comments when uploading new versions
- Reference specific versions when sharing with stakeholders
- Use version history to track document evolution over time
Next Steps
- Document Details - Learn about the rich text editor
- Uploading Files - Upload files to your workspace
- Activity and Comments - Track changes and discussions