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

# Inspect audit events within a granted scope

> Inspect immutable actor, subject and time records while preserving content and clearance boundaries.

You need an explicit audit-reader scope and sufficient clearance. Product or administrative status alone does not define the subjects you should inspect.

## Confirm the granted scope

Inspect the grant and identify permitted subjects and any supported time boundaries. Confirm the clearance applicable to the records.

Audit access grants no ordinary access to the underlying resource. A compliance subject-read path can also differ from an ordinary resource page.

## Query and inspect records

1. Open the permitted audit view in Compliance or Console.
2. Filter by the actor, subject, operation and period relevant to the question.
3. Open each material event and check its recorded identity and time.
4. Inspect the exact subject version and delegated principal where applicable.
5. Follow linked review, publication or grant records through authorised reads.

The record can include grant changes, clearance changes, reviewer decisions, publication, withdrawal, erasure, secret resolution and auditor reads.

A secret-resolution event identifies use and version. It does not contain a retrievable secret value.

## Preserve the inspection boundary

Read-only inspection does not permit editing the reviewed subject, changing its audience or deciding another person's review.

An export is still a protected read. Keep exported records within the permitted audience and destination. The inspection itself is auditable.

## Interpret missing history

Check filters, scope, clearance and audit retention before drawing a conclusion. A deleted subject can leave an audit record. An expired audit record cannot be recreated by editing its subject.

Audit events cannot be edited. Retention deletion records its cutoff and deleted count through the authorised process.

Record the query scope, material event identifiers and any missing or inaccessible path. An empty query establishes no match within that permitted query, rather than proof that an event never occurred.

For result provenance, continue with [Trace a published result to its evidence and decisions](/audit-and-compliance/trace-published-result).


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.