Skip to content

Blog

User access review: a process and a template

How to run a user access review in a small company: who reviews what, how often, the evidence auditors want for SOC 2, and a template you can copy.

· 9 min read

A user access review is a regular check of who has access to which tools, and whether each of them still should. You list every account in every tool, match each one to a current person and role, and remove or downgrade whatever does not fit. Then you record that you did it.

For a small company, a quarterly review takes an afternoon once the first one is done. Below is a process you can run, what auditors want to see, a template, and where to go next in this part of the blog.

What a user access review is

It is a comparison of two lists. The first is who has access: every account, in every tool, with its role. The second is who should: your current people, and what their job needs. Anything on the first list that is not justified by the second is a finding. An ex-employee still in Figma. A contractor whose project ended. A marketer who is still a GitHub admin from the week they helped with the website. A shared login nobody owns.

It also goes by user access recertification, access audit, entitlement review or access certification. The job is the same; the names differ in emphasis. "Access audit" usually means a one-off check, often before a fundraise or a customer's security review. "Certification" stresses the reviewer's signed approval, which access certification covers on its own.

What a review is not

It is not a password audit, a device check or a log review. Those are worth doing, but they answer different questions. A user access review answers one: does every account that exists today have a reason to exist, at the role it has? Keeping it to that question is what makes it fast enough to run every quarter.

How often

Review quarterly for the tools that hold customer data, money or code: your CRM, support desk, cloud accounts, GitHub, finance tools. Twice a year or yearly is enough for everything else. And review after any big change, such as a reorganization, a round of departures, an acquisition, or a security incident, whatever the calendar says.

If you are working toward SOC 2 or ISO 27001, your own policy sets the frequency, and the auditor checks that you kept to it. Quarterly for important systems is a common choice. Pick something you will actually do: a yearly review you run beats a quarterly one you skip, because the skipped one is a finding against you. Healthcare companies have it in regulation too: the HIPAA Security Rule includes procedures to "establish, document, review, and modify a user's right of access" as an addressable implementation specification in 45 CFR 164.308, as we read it on 27 October 2026.

Who reviews what

The person who knows whether someone should have access is usually their manager, or whoever owns the tool, not IT. In a 20-person company that might be three kinds of reviewer. Tool owners confirm each account in their tool: the head of engineering for GitHub, the head of sales for HubSpot. Managers confirm what their direct reports have, across tools. And one coordinator, often the operations lead, collects the lists, chases answers, makes the changes and keeps the record.

Two rules matter more than the org chart. Nobody approves their own access, so if the coordinator is a GitHub owner, someone else signs for that line. And the coordinator is never the only reviewer, because the person who made the changes all quarter is the worst-placed to spot their own mistakes.

At five people, the founder may be all three. That is fine, as long as a second person looks at the founder's own admin accounts.

The review, step by step

Pull the list of people. Export active and suspended users from Google Workspace or Microsoft 365. This is your source of truth for who works here.

Pull the members of each tool. From each admin console: name, email, role, and last login if the tool shows it. This is the slow part, and the one most worth automating.

Match accounts to people by email. Mark each account as matched (a current person), departed (a suspended or deleted person), or unknown (personal emails, contractors, shared accounts).

Ask reviewers to decide. For each account: keep, change role, or remove. For unknowns, the first question is who owns this.

Make the changes. Remove, downgrade, transfer ownership. Note the date for each.

Record the result. Who reviewed, when, what was found, what was changed. Keep the exports.

Fix the cause. If the same kind of finding keeps appearing (contractors never removed, admins never downgraded), change the offboarding checklist or the provisioning process so it stops happening.

What reviewers should look at hardest

Not every line deserves the same attention. Admin and owner roles come first, because a forgotten admin can do far more damage than a forgotten member. Next come accounts that match nobody: personal email addresses, old contractors, test accounts and shared logins. Then accounts belonging to people who are suspended or gone. Then paid seats with no sign-in for months, which are both a security finding and a refund. Last come integrations and API tokens, which no directory lists and which outlive the person who created them.

A reviewer who checks those five groups carefully and skims the rest has done a better review than one who reads every line with the same half-attention.

Evidence for auditors

An auditor wants to see that the review happened, on schedule, and that findings were acted on. For each review, keep the list of systems in scope; the member export for each system, dated; who reviewed each system, with their sign-off (an email or a ticket comment is fine); the findings and the change made for each, with dates; and, for removals, a screenshot or log entry from the tool showing the account removed.

A spreadsheet and a folder of exports is acceptable evidence. What auditors push back on is a review with no findings at all, every quarter, which usually means nobody looked. For a SOC 2 user access review specifically, the test is usually against your own written policy, so make sure the access control policy promises a frequency and a sign-off you actually deliver. Do you need SSO for SOC 2? covers what else that audit asks about access.

Template

Copy this into a spreadsheet, one row per account per tool.

ToolAccount emailNameRole in toolStatus in directoryOwner / managerDecisionChanged onNotes
GitHub[email protected]Ana PopAdminActiveHead of engKeepOwns org settings
GitHub[email protected]Radu IonescuMemberSuspendedHead of engRemove2026-10-27Left in August
Figma[email protected]UnknownEditorNot foundDesign leadRemove2026-10-27Freelancer, project ended
HubSpot[email protected]Mihai StanSuper adminActiveHead of salesChange role2026-10-27Downgraded to sales user

Add a summary tab: date of the review, systems in scope, reviewers, number of accounts checked, number removed, number changed. Next quarter, start from a copy of this one, so the comparison with last time is one glance.

Your first review

The first review is the slow one, because you are building the list of tools as you go. Start with a narrow scope: the five tools that hold customer data, money or code, plus your directory. Finish those, make the changes, and file the evidence before you widen it. A complete review of five tools is worth more than a half-finished review of thirty.

Expect findings. A first review that finds nothing almost always means the member lists were incomplete. Leavers who were never removed from one tool, admins nobody remembers granting and accounts on personal addresses are the usual first harvest. Each one you fix makes the next quarter shorter.

Common mistakes

Reviewing only the directory is the most common: Google Workspace looks clean, while the tools with their own passwords still hold last year's leavers. Close behind is reviewing without acting, where findings are written down and the accounts stay. Then come rubber-stamping, where a reviewer approves every line without reading it; leaving out tools nobody thinks of as "systems", such as the domain registrar or the payment processor; and keeping no evidence of the change itself, so the auditor sees a decision to remove but no removal.

Can access reviews be automated?

Parts of them. The decisions need a person; the collecting and matching do not. Pulling member lists from thirty tools and matching them to your directory is most of the work, and it is the part that is easy to get wrong by hand.

Identity governance products automate the whole cycle, at enterprise prices, and they depend on the tools being connected through SSO and SCIM, which brings back the SSO tax.

Where SmashSSO fits

SmashSSO keeps the "who has access" list current for you. It reads your people from Google Workspace, reads each tool's members and roles, and matches them by email into one access grid. Accounts that match nobody, such as personal emails and contractors, are flagged for review, and people suspended in Google Workspace show where they still have access. Removing or downgrading is one action from the same screen, through a tool's member API where you have added a token or an agent in your own Chrome otherwise, and every change lands in an audit log.

It does not run the review meeting or collect sign-offs for you, it has no CSV export, and it has no SOC 2 report of its own today (security says so plainly). It is not SSO. It costs a flat fee from $199 a month billed annually (pricing).

More on access reviews and security

This post is the hub for reviews, security and audit. The other posts in the cluster fall into three groups.

Start with the controls that a review checks against. Access certification turns a review into a signed record that a named person stands behind, which is what auditors and customers' questionnaires actually ask for. The principle of least privilege in a 20-person company sets the standard each line is judged by, and shows how to cut admin access in an afternoon. And the access control policy template writes down how often you review and who signs, so you have something to be audited against.

Then read about the accounts reviews keep finding. Shadow IT covers the tools you do not know you pay for, which means tools your review will miss unless you look for them. Shared accounts and shared passwords explains why a login used by four people breaks every review, and how to run the few you cannot avoid.

Finally, widen the view to security and regulation. SaaS security for small businesses puts access next to the other risks in a company that runs on SaaS. The Google Workspace security checklist hardens the directory every review starts from. And access control under HIPAA and ISO 27001 maps these practices to what those two frameworks require of a small team.

FAQ

What is a user access review?
A user access review is a regular check of who has access to which tools and whether each of them still should. You match every account to a current person and role, remove or downgrade what does not fit, and record that you did it.
How often should user access be reviewed?
Quarterly is a common choice for tools that hold customer data, money or code, and twice a year or yearly for everything else. If you are audited, your own policy sets the frequency, so choose one you will actually keep.
What evidence do auditors want for an access review?
Auditors want the systems in scope, a dated member export for each, the reviewer's sign-off, the findings and changes with dates, and proof from the tool that removals happened. A spreadsheet and a folder of exports is usually acceptable.
Can access reviews be automated?
Partly. Collecting member lists from every tool and matching them to your directory can be automated, and that is most of the work. The keep, change or remove decisions still need a person who knows the job.

Keep reading

Stop paying for a login button.

Sign in with Google Workspace, connect your tools, and see who has access to what in minutes.

Sign up with Google