Use exports to turn live evidence into reviewable packets.
The exports surface is for packaging already-recorded evidence into formats that audit, compliance, and internal reviewers can consume without working directly inside the console.
Who this is for
Operators, compliance managers, and incident teams preparing evidence for external review or internal sign-off.
When to use it
Use this after you have confirmed the necessary evidence exists and need to produce a JSON, PDF, or Markdown artifact for distribution.
Required setup
Required setup: connected tenant context and confirmed evidence records. Missing or incomplete evidence should be resolved before export rather than patched afterward.
How to use
1. Open exports
Start in /console/exports/ after confirming the tenant and time range you need.
2. Choose the export scope
Define whether you are exporting a narrow incident packet, a release bundle, or a broader audit slice.
3. Pick the output format
Use PDF for regulator or auditor review, JSON for automation and pipeline handoff, and Markdown for internal operational review.
4. Generate and verify
Build the export and check that hashes, record counts, and references line up with the evidence ledger before sharing it.
5. Share the right artifact
Distribute the smallest export that answers the stakeholder question instead of sending a tenant-wide dump by default.
What success looks like
Related console surfaces
/console/exports/ - exports surface/docs/exports/ - export model docs