At a glance
| Input | Action | Output | Limit |
|---|---|---|---|
| Selected scope and period | Filter supported records | Scoped export dataset | Current export paths are bounded |
| Term and review records | Include governed history | Version and approval evidence | External decisions need external references |
| Scanner records | Include findings, resolutions, scans, and page status | Terminology-control evidence | Rows require correlation by identifiers |
| Enterprise baseline | Export through archive workflow | Frozen verifiable package | This is separate from standard audit CSV output |
How it works
- Define the audit scope and review period.
- Open the audit export area.
- Select the supported evidence categories.
- Generate the CSV or print-ready output.
- Review identifiers, limits, and missing evidence.
- Add baseline or archive evidence when a frozen package is required.
Example
An auditor requests the approval history and remediation state for one Confluence space. The export contains the governed term records, finding rows, latest resolution records, scan history, and page status. The team uses identifiers to correlate them and adds a verified baseline archive for the release state.
What this does not mean
The export does not create an auditor narrative, certify control effectiveness, or include decisions never recorded by the app. Bounded export limits and selected scope must remain visible.
Related questions
Next step
Define scope first, then export only the evidence needed for that review.
View on Atlassian Marketplace