Access Governance for Jira

Jira Cloud

See who has access to what in your Jira site, and what a permission change will break before you make it.

What it does

Jira spreads access across groups, permission schemes, project roles, and licenses, and no one screen shows you the result. To find out what a single person can get to, you open four admin pages and piece it together yourself.

Access Governance reads all of that and puts it on one screen. You’ll find it under Settings → Apps, and only Jira administrators can open it.

Effective access. See what one person can reach, and which group or role gave them that access. Or start from a project and see everyone who can get into it.
Preview a change. Pick a group and see who would lose access, and to what, if you removed it. Then make the change, with a record you can undo.
Unused licenses. Find the accounts nobody has used in a while, and see what freeing those seats would save at the per-seat price you pay.
Access reviews. Run recurring reviews where you decide who keeps access, sign off, apply the changes, and export the evidence for your auditors.

Read the guide

Where your data lives

Access Governance is built on Atlassian Forge, and it’s read-only by default. It reads your permission settings to work out who has access, and stores the result only in Atlassian-hosted Forge storage, in your own site’s data-residency region.

The app declares no external network access, so nothing is sent to Schema Software or anyone else. We don’t run a server it could send to. If you uninstall it, the stored data is removed too.

Read the privacy policy

What it can’t see

Last activity isn’t last login

“Last issue activity” is the last time someone did something on an issue. It’s a good sign of who’s active, but an app that keeps your data inside Atlassian can’t see last-login times. Double-check before you remove anyone.

Some access isn’t visible to it

Membership in issue security levels, and global permissions like Administer Jira, can’t be read by an app that keeps your data inside Atlassian, so they don’t appear. Where they matter, the app links you to the Jira admin page where you can check them yourself.

Get it on the Atlassian Marketplace

Trials, purchases, renewals, and refunds all go through Atlassian.

Documentation and terms

User guide: Installing, running a scan, and every tab in the app, with screenshots.
Support: How to get help, how quickly we aim to reply, and where to send feedback.
End User License Agreement: The Bonterms Standard End User Agreement, plus our Provider-Specific Terms.
Data Processing Addendum: How personal data is processed, with the schedules and subprocessor list.
Privacy Policy: What the app reads, where it is stored, and your rights.
Security Measures: The technical and organizational controls we have in place.
Subprocessors: Third parties that process customer data. There’s currently one.