Build and share an audit package

Build the packageCopy Anchor Link

1. Set the framework scope, audit type and period.
2. Review missing, stale and unresolved evidence on the checklist.
3. Open Reports, request the scoped package and wait for its build to complete.
4. Download the package and retain its hash manifest with the review record.

A successful export means the package was built, not that every control passed. Review its contents before handing it to an auditor.

Share with an auditorCopy Anchor Link

Invite the auditor with an access end date and explicitly share the required report. Auditor roles retain report and resource-level access checks.

Treat download links as private. Retrieve packages through the authenticated workspace and avoid placing links or evidence in public tickets.

Verify integrityCopy Anchor Link

Use the supplied manifest to check transferred files. Investigate a mismatch before relying on the package. Integrity hashes detect changed bytes; they do not validate the truth of a claim or replace an auditor's assessment.

See SOC 2 audit types before choosing Type I or Type II package scope.