Compliance guide

Jira access review for SOC 2 and ISO 27001

Jira holds plans, customer names, incident details and security tickets. When your company is audited, someone will ask who can see and change what in it. Here are the six checks that answer that question, how to run each one by hand in Jira Cloud, and what to keep as evidence.

Published 2 November 2026 · Jira Cloud · A practical checklist, not legal or audit advice

Why auditors ask about Jira access

Both frameworks expect you to control access to information and to review that access on a regular schedule. Jira is a system where access builds up quietly: a permission scheme edited for one space, a filter shared with everyone for a one-off meeting, an admin group nobody pruned after a reorganisation.

An auditor usually wants three things: that you know who has access, that broad access is deliberate, and that you review it on a fixed rhythm and can show it. A dated record of each quarterly review answers all three.

Names changed. Jira Cloud now calls projects spaces and issues work items. This guide uses the new names; older articles and screenshots use the old ones. If a menu path below does not match your screen, use the search box in Jira settings.

1. Permission schemes

Permission schemes decide who can browse, create, edit and administer in each space.

  • By hand: Settings (the gear icon) → Work items → Permission schemes. Open each scheme and read every permission. Look for grants to Public (anyone on the internet, without logging in) and to Any logged in user, especially on browsing a space, administering it and editing work items. Then check which spaces use the scheme.
  • Question to ask: is each broad grant deliberate, and does someone own it?

2. Shared filters

A saved filter shared with everyone exposes the work items it returns to everyone.

  • By hand: Settings → System → Filters. Review the sharing column and look for filters shared publicly or with all logged-in users. Open each flagged filter to see what it returns. Admins can change a filter's owner or delete it there; its owner changes the sharing from the filter's details.

3. Dashboards

Dashboards share the same way, and their gadgets can list work items, names and counts.

  • By hand: Settings → System → Dashboards (under Shared items). Look for dashboards shared publicly or with all logged-in users, and for dashboards whose owner has left.

4. Space roles

Roles are how most schemes grant access, so the people and groups inside them matter as much as the schemes.

  • By hand: Settings → System → Space roles (formerly project roles) for the default members, then each important space's Space settings and its people page (People in company-managed spaces, Access in team-managed ones). Look for broad groups placed in roles, and for people who changed teams but kept their role.

5. Administrative groups and inactive admins

Administrators can change everything above, so this list should be short and current.

  • By hand: Settings → System → Global permissions: note which groups hold Administer Jira. Then open each of those groups in Atlassian Administration (admin.atlassian.com → Directory → Groups) and read its members. Look for deactivated or departed accounts that are still members, and for groups that are bigger than they should be.

6. Account types

Not every account is an employee. Customer accounts (Jira Service Management), app accounts and guests carry different risk.

  • By hand: admin.atlassian.com → Directory → Users. Filter by status and account type, and note how many are active, inactive, app and customer accounts. Look for inactive accounts that still have access and for unexpected account types.

What evidence to keep

An auditor cannot verify a review that left no trace. For each quarter keep:

  • the date of the review and who did it;
  • what you checked (the six areas above) and what you found;
  • every broad grant or share you decided to keep, with the reason and the owner;
  • every change you made, with its date, and a note that you re-checked afterwards;
  • anything you could not check, and why.

Store this where your auditor already looks, such as your document system or a ticket in a dedicated space. Screenshots help, but a short written record that stays comparable from quarter to quarter helps more. For the hands-on steps behind each check, see the Jira permission audit checklist.

Doing it unattended with Ledgerstone

Ledgerstone is a Jira Cloud app that runs these checks for you and keeps the results. It covers the same six areas: permission schemes, shared filters and dashboards, space roles, administrative groups with inactive members, and account counts by type. Findings are graded High (public, or admin-level for everyone), Medium (every logged-in user) or Could not verify, and each finding links to the Jira page where it is fixed. The first audit runs when you open the app, then it runs by itself every week. The last 12 weekly results are kept as a trend, and a "Since last week" card lists findings that appeared or were resolved, comparing only the areas that were fully read in both runs.

  • Read-only: built on Atlassian Forge with granular read scopes only, so it cannot change anything in Jira.
  • Nothing leaves Atlassian: no network calls outside Atlassian, and no names or account IDs stored. Only counts and configuration names are kept; people's names are shown live.
  • Not a certificate: Ledgerstone is not certified for SOC 2 or ISO 27001 and does not make you compliant. It gives you a dated, repeatable record to put into your own quarterly review.
  • Free for sites up to 10 users; then $1.50 per user per month, with a 30-day free trial.

Try Ledgerstone free on the Atlassian Marketplace, read how it works, or send us a message.

Spotted a menu that moved, or a check your auditor asked for that is missing here? Tell us and we will update this page.