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.
Restoring a Previous Version
To roll back to an earlier snapshot:
- Open the History tab in the right panel
- Find the version you want in the list
- Click Restore on that version to make it the current content
You can also open the same list from the floating toolbar's More actions (…) menu via Version history. There are no undo/redo version-stepping arrows in the toolbar — you always restore a specific version directly.
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
The new upload silently becomes the latest version — there is no confirmation dialog. Previous versions remain accessible in the history.
Uploading a New Version from the Toolbar
You can also upload a new version directly from an open file:
- Open the uploaded file
- Click the More actions (…) menu in the floating toolbar
- Choose Upload new version and pick the file
Viewing Version History
For both editor documents and uploaded files:
- Open the document or file
- Open the History tab in the right panel
- 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
- 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