> ## Documentation Index
> Fetch the complete documentation index at: https://docs.elevatedsignals.ai/llms.txt
> Use this file to discover all available pages before exploring further.

# Audit Trail

> Review covered audit events and verify the organization audit chain.

The **Audit Trail** page at `/audit` presents covered quality-system events for the signed-in
organization and provides an on-demand integrity check. It is available when the `audit-trail`
feature is enabled.

## Event Log

Review covered events in chronological order with timestamp, actor, actor type, action, affected
entity, and record identifier. Human, AI, and system actions are labelled separately so attribution
remains explicit. Use **Load more** to continue through older records when additional pages are
available.

## Verify Integrity

Select **Verify Integrity** to recompute the organization's stored tamper-evident chain from genesis.
The verification report returns one of two results:

* **Chain intact** reports how many covered records were verified.
* **Integrity issue detected** identifies the first detected divergent record and the reported reason.

A passing result shows that the stored covered chain is internally consistent at that point in time.
It does not prove audit-event completeness or protect against every action available to a privileged
database owner. Treat a detected issue as an investigation trigger, and retain the as-of result
according to your data-integrity procedure.

<Note>
  Invariant describes this control as **tamper-evident**, not immutable. It is built to Part 11 and
  Annex 11 expectations, but a passing verification is not a certification or a complete validation
  conclusion.
</Note>

For the control design and claim boundary, see
[Audit trail & tamper-evidence](/invariant/compliance/audit-trail-tamper-evidence).

## Open the affected record

Select a linked record identifier in the event log to open its detail page. Supported links cover
documents, deviations, CAPAs, complaints, change controls, and quality tasks that resolve in your
organization. The destination still applies its normal access and feature checks.

An identifier stays as text when the record is unavailable or the event type has no supported detail
page. Import batches, document versions, training assignments, and configuration events do not gain
record links from this release. A missing link does not mean the audit event is missing.

## Validation events

Where onboarding imports are enabled, each successful **Validate only** request saves a validation
batch and an audit event. It does not create the records predicted by the report. Recent activity may
show the action as `dry_run`. See [Validate and import CSV](/invariant/reference/settings#validate-and-import-csv)
for the difference between predicted and committed results.