Version history, Trash, and recovery

Document history records meaningful changes and their actors. It lets collaborators inspect earlier versions, compare content, and restore a known state without manually recreating it.

Review history

Open a document's history to see its sequence of changes. Entries distinguish human and agent activity and retain the responsible user or agent session where applicable.

Restoring an earlier version creates a new current state; it does not erase the intervening history. This preserves an auditable chain of what happened.

Trash and restore

Deleting a document moves it to Trash. From Trash, an authorized user can restore the document. A permanent purge is a separate destructive operation and is not a v1 webhook event.

For webhook consumers, document.deleted specifically means the document moved to Trash. Restoring it does not emit a document.created event, so an automation that needs restore awareness should reconcile current state through MCP when appropriate.

Permanent purge removes the recoverable document record. Confirm that the content and any attached material are no longer required before purging.