See where a value came from and which version was shared

Check a delivery date or invoice amount against the original email or document. Corrections change the working data and keep a separate review history, so the original stays intact.

Follow supporting references within your access and see who reviewed or corrected a value. The available versions follow the source’s access and retention settings.

See refreshes, shared versions and recorded lifecycle events. Identify the version used for a handover or delivery, even when the working view has since changed.

Keep the original document, reviewed value and shared version connected when you need to explain an answer. Your responsible reviewers assess the underlying business or legal question.

Review recorded access, configuration changes, applied sharing policies and delivery attempts in the Audit Log, with actors, times, references and outcomes. AI requests also identify the tool, stated purpose and result information.

Use audit references to trace a request to the shared data and saved version. Full request and response bodies are excluded from the Audit Log, keeping the recorded investigation references separate from those contents.

Retention settings can remove downloads for eligible superseded shared versions. Their lifecycle history and recorded cleanup events can remain available after those files are pruned.

Source files, storage and backups have their own retention rules. Download pruning and disconnecting a source account have different effects, so choose settings for the material your organization needs to keep.

Follow an original document, a corrected field and a shared result using the reviewer’s own access. See the recorded actions and which retained versions they can download.

Agree how long the linked material must be available and who owns the retention settings for your deployment. A document reference identifies captured material; its availability still follows access permissions and retention settings.