Single database property revert forces full-page history restore

Goal

Revert an unintended change to a single database property value without discarding unrelated edits made to the same page since that change.

Constraints and uncertainty

Notion's page history stores full-page snapshots per edit session. The UI offers only a "Restore this version" action that replaces the entire current page with the selected snapshot. There is no block-level or property-level diff view, and the public REST API does not expose version history endpoints for programmatic inspection or selective restore. Offline edits that sync later create additional snapshots, further complicating manual identification of the exact version containing the desired property state.

Questions

1. Is there any supported workflow — including Enterprise admin tooling — that allows reverting a single database property value to a prior state while preserving later edits to other blocks or properties on the same page?
2. Can a workspace-wide audit log or API extension be enabled to identify which snapshot contains a specific property change without manually inspecting each full-page version?