Blog ·

User access review checklist: steps, evidence, schedule

A user access review checklist is the fixed list of steps you run every time you confirm that the people who can reach a system still need that access: define the scope, export the current users, send each list to the person who can vouch for it, remove what nobody vouches for, and keep the evidence. The list itself is short. What makes access reviews fail an audit is rarely a missing step. It is a review that happened late, happened unevenly, or happened without a record that anyone can find a year later. This guide gives you a checklist you can copy today, explains what each step is for, and shows how to make the review arrive as a ticket on the same day every quarter so the schedule stops depending on someone remembering it.

This is a practical guide, not audit advice. Your security team, internal audit and external auditor decide which systems are in scope and how often each one is reviewed.

What a user access review is for #

An access review answers one question for one system: does every account that can sign in still belong to someone who needs it, at the level they have? Accounts drift. People change teams and keep their old groups. Contractors finish and nobody tells the admin. A project admin role granted for a migration stays after the migration ends. None of this is malicious, and all of it is the kind of finding an auditor writes up.

Reviews usually come in two kinds:

Review Who is in it Typical cadence
User access review Every account on an in-scope system Quarterly or twice a year
Privileged access review Admins, owners and service accounts Quarterly, sometimes monthly
Leaver check Accounts of people who left since the last review Every review, as a separate step

The cadence column is a common pattern, not a rule from any one standard. The cadence that matters is the one your own policy writes down, because that is what an auditor tests you against. If the policy says quarterly, four reviews with even spacing pass. Three reviews, or four bunched into the second half of the year, do not.

The user access review checklist #

Copy this into whatever holds your reviews: a ticket description, a checklist app, a document. Each step has a short note on why it is there.

Before the review #

  1. Name the period and the system. "Q4 2026 user access review: Jira Cloud." One review covers one system for one period, so the evidence for any period is one record.
  2. Confirm the scope. Which sites, projects or environments are in scope this time, and has anything been added since the last review?
  3. Pull last period's review. Open the previous record and note any removals that were promised and not yet done. Those carry over first.

Collect the current access #

  1. Export the user list from the system itself, never from memory or an old spreadsheet. Include each account's status, role and group membership.
  2. Include the last sign-in date where the system records one. An account nobody has used in months is the fastest finding you will make.
  3. List privileged accounts separately: admins, owners, and any shared or service accounts. These get a closer look and usually a different reviewer.
  4. Save the raw export with the date in the filename. The export is the "before" picture, and auditors often ask for it.

Review with the people who know #

  1. Send each manager or system owner only their own people. A reviewer facing a list of four hundred names approves everything. A reviewer facing their own twelve actually reads it.
  2. Ask for a decision on every row: keep, change, or remove. A blank is not a keep.
  3. Set a reply date, usually a week or two, and chase on that date rather than at the end of the quarter.
  4. Have privileged access reviewed by someone other than the account holder. An admin approving their own admin rights is the classic finding.

Act on the answers #

  1. Remove or downgrade every "remove" and "change" and note the date each was done.
  2. Check leavers against HR's list of people who left during the period. Anyone on that list with an active account is a finding to fix today.
  3. Re-export after the changes. The second export is the "after" picture and proves the removals happened.

Close the record #

  1. Attach the evidence: both exports, the reviewers' replies, and the list of changes made.
  2. Record the sign-off: who approved the review as complete, and when.
  3. Book the next review. The review is not finished until the next one has a date. This is the step most teams skip, and it is the one that causes the uneven spacing.

Running the review for Jira Cloud #

If Jira itself is one of the systems in scope, Atlassian gives you most of step 4 directly. As of October 2026, Atlassian's support page Export users from a site says an organization admin can export the user list as a CSV from Atlassian Administration, under Directory → Users → Export users in the centralized user management experience, or from the site's Users page in the original one.

The export dialog lets you choose:

Atlassian emails you when the CSV is ready. The column that does the most work in a review is the last-seen date, which Atlassian's page describes as:

The date the user last viewed the app's workspace for a minimum of 2 seconds.

Sort by that column first. Then check the role column, which shows whether each person is a user, an admin or a guest for each app, and the group membership column, which is where leftover access from old teams usually hides. For the project side of Jira, project roles and permission schemes decide who can see what inside each project, so a review of a sensitive project also lists who holds its project roles.

Make the review arrive on time #

Everything above is easy to do once. The hard part is doing it four times a year, evenly spaced, for every system in scope, while the people responsible are busy with other work. A calendar reminder tells one person. It does not create a record, it does not carry the checklist, and it disappears when that person leaves. A review that arrives as a ticket fixes all three: it has an owner, a due date, the steps, and a history.

You have three practical ways to get that ticket created on a schedule in Jira:

Option How it works Good for
Create it by hand Someone clones last quarter's ticket One system, one owner who never forgets
Jira Automation A scheduled rule creates the issue Teams already running rules site-wide
A scheduling app A rule in the project creates the issue Controls kept in one project, with a run history

Our guide to Jira recurring tasks compares these in detail. Whichever you pick, set the ticket up so the checklist above lives inside it.

Setting it up with Recurring Work Items #

Recurring Work Items for Jira creates issues on a schedule from rules that are scoped to one project, so the review calendar can live inside your security or controls project and nowhere else. For a quarterly access review:

  1. Create a monthly rule that repeats every 3 months, starting in the first month of the quarter.
  2. Pick the day: "the 1st", or a weekday pattern like "the first Monday of the month", so every quarter starts on the same footing.
  3. Choose what happens on a non-working day. Under If it falls on a non-working day, Move it to the next working day keeps a review from landing on a weekend or a public holiday you have set.
  4. Name each period with tokens, for example User access review {{now.year}}-{{now.month}}: Jira Cloud, so each quarter's ticket has a title of its own.
  5. Fill in the template: the control owner as assignee, a due date a set number of days after the run, a label such as access-review, and the checklist in the description.
  6. Add subtasks for the steps that different people do: export users, manager review, privileged review, removals, evidence and sign-off.
  7. Leave "If the previous issue is still open" on Create it anyway. For most recurring work, waiting for the last ticket to close stops a pile-up. For an access review, a missed quarter is itself the finding, so you want the next review created on its date even when the last one is still open.

Each rule keeps a history of its runs, recording whether the ticket was created, skipped or failed and why, which is useful when someone asks whether the review was ever missed. For a privileged access review on a tighter cadence, make a second rule with its own owner rather than folding it into the first.

When the manual way is enough #

A scheduled ticket earns its place once reviews outnumber what one person tracks without effort. You may not need one if:

The checklist itself still applies in all three cases. Only the reminder changes.

Access reviews rarely live alone. If you run them for a compliance programme, the Jira SOX compliance, Jira ISO 27001 and Jira HIPAA compliance guides each set out a review calendar that includes this one. The Jira audit log guide covers the other half of the evidence: what changed, and who changed it.

FAQ #

How often should a user access review happen? As often as your policy says, and evenly. Quarterly is common for systems that hold sensitive or financial data, with privileged accounts reviewed at least as often as everyone else.

Who should review access? The person who can say whether each account still needs it: usually the user's manager or the owner of the system. Privileged accounts are reviewed by someone other than their holders.

What evidence does an auditor want? The export from before the review, the reviewers' decisions, the changes made with their dates, the export after, and a sign-off. Keeping all of it on one ticket per period makes the sample request a single search.

Can Jira remind us to run access reviews? Not on its own from a date field. A scheduled rule, in Jira Automation or an app like Recurring Work Items for Jira, can create the review ticket on the first working day of each quarter with the owner, due date and checklist already filled in.