A user access review template is a worksheet and schedule for checking who can get into each system and whether they still should. List your systems below and give each a risk tier. You get a review cadence, a 12-month calendar and a CSV worksheet to record every keep, revoke or modify decision.
Five example systems are filled in. Edit them, remove them or add your own.
| System | Risk tier | Owner | Cadence | Reviews in 12 months | Next review |
|---|---|---|---|---|---|
| OktaSOC 2 | Critical | IT team | Every 2 months | ||
| AWS production consoleSOC 2 | Critical | Platform engineering | Every 2 months | ||
| Payment admin dashboardPCI DSS | Critical | Finance | Every 2 months | ||
| Salesforce | Standard | Sales operations | Every 6 months | ||
| Training platform | Low | People team | Yearly |
Pick a first review date to build the calendar.
A CSV with one block of rows per system and these columns: system, risk tier, framework, review cadence, review due, reviewer, user, email, role or entitlement, last login, decision (keep/revoke/modify), justification, date reviewed, ticket link. Open it in Excel or Google Sheets and paste in each system’s user export.
Cadences follow our guide to how often to run user access reviews: critical systems every 2 months (the guide says 30 to 60 days), standard systems every 6 months and low-risk systems once a year. Systems tagged PCI DSS are reviewed at least every six months, per requirement 7.2.4 of the PCI DSS standard. Other frameworks are labels only and don’t change the schedule.
From multiplierhq.com/tools/user-access-review-template
A user access review is a check, system by system, of who has access and whether they still need it. The system owner or each user's manager decides to keep, revoke or modify every account, and the decisions are recorded as evidence for auditors.
Match the cadence to risk. Review critical systems, such as admin consoles, production and payment systems, every 30 to 60 days. Review regular business apps every 6 months and low-risk tools once a year. This template schedules critical systems every 2 months.
For each account: the system, user, email, role or entitlement, last login, reviewer, the decision (keep, revoke or modify), a justification, the date reviewed and a link to the ticket that made the change. The CSV worksheet on this page has all of these columns.
PCI DSS v4.0.1 requirement 7.2.4 asks that all user accounts and related access privileges are reviewed at least once every six months. When you tag a system with PCI DSS, this template never schedules it less often than that.
It is free and needs no signup. Everything runs in your browser: the systems you type are not sent anywhere, and the CSV is built on your device.
Yes. Multiplier runs user access reviews inside Jira Service Management, with users pulled from your identity provider, and exports the evidence for auditors. It has a 30-day free trial on the Atlassian Marketplace.
See how Multiplier access reviews replace the spreadsheet.
Multiplier sends reviewers their lists in Jira Service Management and keeps the evidence for your audit. Free for 30 days.
Start a free trialSee access reviews