Compliance Evidence Packs
Build one downloadable, checksummed archive of the records an auditor asks for — audit logs, approvals, deletion history, access history, document activity and signature coverage — instead of exporting six screens by hand.
Evidence Packs live under Security → Evidence Packs. An audit request is rarely "show me a screen"; it is "give us the records for this period, and let us confirm nothing changed after you sent them". A pack is that deliverable.
What You Can Include
| Section | Answers |
|---|---|
| Audit Logs | What was done, by whom, when. |
| Approvals | What was authorised, and by whom. |
| Trash Lifecycle Ledger | What was deleted, restored, or permanently removed — and under what hold. |
| Access History | Who reached the workspace, and from where. |
| Document Activity | Who opened or downloaded which vault documents. |
| Handover Signature Coverage | Which custody handovers were signed for — and which were not. |
Pick the sections you need and set the filters — typically a date range — so a pack answers the request rather than dumping everything.
How Generation Works
- You name the pack, choose sections and filters, and submit it.
- The pack appears immediately as generating — building the archive happens in the background, so a large range does not tie up your screen.
- When it finishes it becomes ready, with the row count per section, the file size, and a SHA-256 checksum.
- A pack that cannot be built is marked failed rather than left half-finished.
Refresh the list to see a pack move from generating to ready; it does not need you to stay on the page.
The Checksum Is The Point
Each ready pack carries a SHA-256 checksum of the archive. Send it alongside the file and the recipient can confirm that what they received is exactly what you generated. Downloads are served through short-lived signed links, and the download is recorded on the pack.
Scope
A pack contains only your organization's records — every section is scoped to your workspace when it is built, not filtered afterwards. For the integrity of the audit section itself, see Audit Logs.
Need help with this topic?
Capture the module, record number, branch or warehouse, user, visible message, and what you expected to happen before contacting support.