History, undo and revert
Open an item’s history and read ordinary changes in order:
- Mina renamed “Outline” to “Release outline”
- Build agent updated 3 files
- You moved budget.ods to Planning
- Ravi restored the version from 14:32
Each entry names the person or agent, the affected item and the action. Open it to inspect the change in context.
Undo your last action
Undo reverses your own recent action in the current context. Ctrl+Z works for typing, moving a file and changing a setting because the desktop records named actions below the apps.
Undo does not silently remove work another collaborator added afterwards. When later work depends on your action, the preview shows what else changes or offers a targeted revert instead.
Revert a selected change
Use Revert changes for an earlier action, another collaborator’s edit or an agent run. Revert creates a new change that reverses the selection. It leaves the original entry in history, along with the author and everything that happened after it.
This makes disagreement legible. History shows the edit, the revert and who made each decision instead of rewriting the past until nobody can explain the current document.
Restore a version
Use Restore this version when you recognise the state you want more easily than the individual actions that produced it. The selected version becomes the new current state, recorded as a new change. Newer history remains available.
The preview names the item and summarises what differs. Restoring a folder or workspace lists the affected children before it proceeds.
History follows access
History uses the same boundary as the item. A person who cannot open a private file cannot learn its name or activity from a workspace counter. Removing a member stops new history from reaching them; it cannot erase copies they received while authorised.
Apps supply descriptions for their own actions. Generic summaries such as Changed a property, Added 5 characters or Reordered items appear only when no more useful description exists. Internal object IDs and raw CRDT operations stay in developer tools.