File version history
SynckHub file history exists to protect collaboration. Use it before manual rework, duplicate uploads, or offline recovery.
What history answers
Use file history and activity when you need to know:
- what changed
- who changed it
- when it changed
- whether a desktop session, coauthoring session, or upload changed the file
- which previous state should be restored
Common file states
Exact labels can vary by deployment, but the model is consistent:
| State | Meaning |
|---|---|
| Current content | The latest committed file content |
| Named version | A durable version saved for review, milestone, or recovery |
| Revision | A lower-level content change recorded in history |
| Draft or session state | Temporary or in-progress desktop/coauthoring state |
| Recovery draft | Non-durable content that may help manual recovery after interrupted work |
Do not confuse a transient draft with a durable version.
Use versions deliberately
Create a named version when the file reaches a useful milestone:
- internal review
- external delivery
- approved baseline
- pre-restore checkpoint
- major content handoff
Avoid creating version noise for every typo-level edit if your workflow supports overwriting or continuing the current working state.
Understand locks and coauthoring
Some file workflows use locks to prevent conflicting edits.
- Exclusive locks protect single-editor workflows.
- Shared or coauthoring sessions may be used for supported Office workflows.
- Session cleanup releases locks and temporary working state.
If a file appears locked, do not bypass the lock by downloading, editing locally, and re-uploading under a new name. That usually creates worse history.
Restore a previous version
Use restore when the current content is wrong and a known-good previous state exists.
- Open the file history or activity view.
- Identify the candidate version.
- Check surrounding activity to understand what happened.
- Confirm with impacted collaborators.
- Restore the chosen version.
- Verify the file opens and collaborators can access it.
- Record why the restore happened in the related note, task, or chat.
When to ask an admin
Ask for help when:
- a lock or session appears stuck
- history is missing expected changes
- a restore would affect active collaborators
- a file was changed through an integration or desktop flow you do not understand
- permissions prevent you from seeing the needed history
Good file hygiene
- Keep one canonical file instead of repeated copies.
- Save meaningful versions at milestones.
- Use activity before guessing what happened.
- Do not restore based on timestamp alone.
- Keep related decisions in a note, task, or chat near the file.
Next step
Continue to Export and Download Files.