Jira Cloud · Documentation
Permission Audit
Who can access this project, and how they got that access.
Getting started
- What Permission Audit doesThe question the app answers, who it is for, and what is in scope for the first release.
- Installing the appWhat the app needs, what permissions it requests, and how to find it after install.
- Running your first scanStarting a scan, what happens while it runs, and how to read the result when it finishes.
Using the report
- Reading the reportThe shell every report tab shares — coverage, the at-a-glance row, findings, and the activity log.
- How access is derivedThe chain from account to permission, why every route matters, and how to read the derivation rail.
- People and installed appsThe two populations the report covers, why they are separate, and what each detail page shows.
- ProjectsThe project view, who can reach each project, and how access with no individual to attribute is reported.
- Permission historyAsking what an account held on a given date, and seeing what changed between two scans.
Running it
- Continuous scanningThe one toggle that keeps the report current and records what changed, and what turning it on actually does.
- Exporting to CSVGetting the report out for an evidence pack, choosing columns, and what the export contains.
- SettingsSensitive permissions, review flags, export columns, and the continuous scanning control.
- Scan cost and quotaWhat a scan actually consumes, why incremental scanning matters, and where to see the cost of a run.
Reference
- EditionsWhat Standard and Advanced each include, how trials work, and what happens on a downgrade.
- Security and data handlingWhat the app can reach, every scope it requests and why, what it stores, where that lives, what QuinTek can and cannot see, and how to report a vulnerability.
- TroubleshootingPartial coverage, scans that do not finish, unexpected results, and what to send us if you need help.