Lizzard Solutions

User Access Review Template: Quarterly Checklist for SMBs

· Lizzard Solutions
User Access ReviewAccess ControlCybersecuritySmall Business ITTemplates

By Nemanja Vukmirović, Lizzard Solutions. Last updated 16 November 2026.

Ask a small business owner who can open the company bank account, the accounting software and the website admin panel, and the honest answer is often "probably the right people". Access piles up quietly: a contractor who finished in spring, an intern who still has the shared drive, an old admin login nobody remembers creating.

This user access review template fixes that with one short session per quarter. You get a ready-to-copy review sheet, a seven-step quarterly process, a worked example, clear rules for shared, ex-employee and admin accounts, and a list of the evidence to keep so you can prove the review happened.

TL;DR

  • A user access review is a scheduled check that every person still needs each access they have, decided by the person who owns the system.
  • Use one sheet with eight columns: person, role, system, access level, last login, owner decision (keep, reduce, remove), date and reviewer.
  • Review quarterly, admins and finance systems first, and keep the signed sheet plus screenshots as evidence.

What is a user access review?

A user access review is a regular, documented check of who has access to each business system and at what level. For every account, the system owner decides whether to keep, reduce or remove it, based on the person's current role. The goal is least privilege: everyone has exactly the access their job needs, and nothing left over.

This is not a big-company idea. The UK NCSC's guidance on identity and access management tells organisations to review user accounts and systems for unnecessary privileges on a regular basis and to have a joiners, movers and leavers process. CISA's Cyber Essentials for small organisations asks you to grant access and admin permissions based on need-to-know and least privilege.

Key takeaway

Offboarding removes access when someone leaves. An access review catches everything offboarding missed, plus people who changed roles and kept their old rights.

Action for today: write down the five systems where wrong access would hurt most, such as email, banking, accounting, the website and file storage.


The user access review template (copy this sheet)

Copy the table into a spreadsheet. One row per person per system. The example rows show how to fill it in; replace them with your own data.

PersonRoleSystemAccess levelLast login / usedOwner decisionDateReviewer
Marko P.Sales leadCRMAdmin3 days agoReduce to user2026-12-15Owner (CEO)
Jelena S.Accountant (external)Accounting softwareFull12 days agoKeep2026-12-15Owner (CEO)
Ivan T.Former internShared driveEditor4 months agoRemove2026-12-15Office manager
office@Shared mailboxEmailDelegated to 3 peopleTodayKeep, remove 1 delegate2026-12-15Office manager
[name][current role][system][admin / editor / viewer][date from admin panel][keep / reduce / remove][date][system owner]

Fill "Last login" from the system, not from memory. Most admin consoles show the last sign-in per user. An account that has not been used for 90 days is a strong candidate for removal, whatever the person says.

If you do not yet have a list of your systems, start from your IT asset inventory template: every SaaS subscription on that list is a row source for this sheet.

Action for today: create the sheet and add one row for every admin account you know of.


Who reviews what?

The person who reviews access must understand the system and the business need. In a small company that usually means three roles:

System typeReviewer (owner)What they check
Email and office suiteOwner or IT personActive users, admins, shared mailboxes, forwarding rules
Banking and paymentsOwner or directorWho can view, who can pay, signing limits
Accounting and invoicingOwner with the accountantExternal accountant access, export rights
Website, domain, hostingWhoever pays for itAdmin logins, registrar account, DNS access
CRM, shop, project toolsTeam lead for that toolRoles match current jobs, no leftover guests

Nobody reviews their own access. If the owner is also the only admin, a second person (a partner, the accountant or your IT provider) should sign off on the owner's rows.

Action for today: write a reviewer name next to each of your five critical systems.


The quarterly access review process in 7 steps

  1. Set the date. Put a recurring calendar entry in the first week of each quarter and name one coordinator.
  2. Export the user lists. From each system's admin panel, export or screenshot users, roles and last sign-in. Date the file.
  3. Fill the sheet. One row per person per system, copied from the exports, not typed from memory.
  4. Compare with your staff list. Anyone not on the current staff or contractor list is marked Remove unless the owner explains why.
  5. Owners decide. Each reviewer marks keep, reduce or remove for their rows, with a short reason for any admin or finance access.
  6. Apply the changes within five working days. Remove or downgrade access, then re-export the user list to confirm.
  7. Sign and file. The coordinator saves the sheet, the before and after exports and the date in one folder.

NIST describes the same control for larger organisations: in SP 800-53 Rev. 5, control AC-2 (Account Management) includes reviewing accounts for compliance at a defined frequency, and AC-6 covers least privilege. You are applying a lightweight version of that.

Action for today: book the first review in your calendar, with the coordinator invited.


Shared, ex-employee and admin accounts

These three account types cause most problems, so give them their own rule:

Shared accounts

A shared login (one password for info@, a supplier portal or social media) has no single owner and no trail. Where the tool allows it, replace it with named accounts or delegated access. Where it does not, store the password in a password manager for small business, list who can see it, and change the password every time someone on that list leaves.

Ex-employee and ex-contractor accounts

Any account belonging to someone who left is a Remove, unless the mailbox is kept for handover. In that case, block sign-in, convert or delegate the mailbox and set a deletion date. If you find more than one, your leaving process has a gap: follow the employee offboarding IT checklist next time.

Admin accounts

Admins get the strictest review. Aim for at least two admins per critical system, so you are never locked out, and no more than you need. Admins should use multi-factor authentication and, ideally, a separate admin account instead of their everyday login, as the NCSC guidance above recommends.

Watch out

Do not forget access outside your office suite: the domain registrar, hosting control panel, Google Business Profile, payment gateway and any agency that built your website. These rarely appear in a staff list.

Action for today: count your admins per system and remove any that belong to people who no longer need them.


Worked example: a 12-person design studio

This is a fictional example to show the process, not a real client. A studio with 12 staff and two freelancers runs its first quarterly review in December.

  1. The coordinator exports users from the office suite, the accounting software, the file storage, the website hosting panel and the project tool.
  2. Comparing exports with the staff list shows one freelancer who finished in the summer still has editor rights on client folders. Marked Remove.
  3. Three people have admin rights in the project tool because it was easier during setup. Two are reduced to member.
  4. The website hosting panel has one login, owned by the agency that built the site years ago. The owner requests a company-owned login and removes the old one.
  5. Changes are applied within the week, new exports saved, and the sheet signed by the owner.

The second review, three months later, is shorter, because the sheet already exists and only changes need checking.

Action for today: pick the system with the oldest setup in your company and export its user list first.


What evidence should you keep?

Evidence lets you show a client, insurer or auditor that access is controlled. Keep it in one dated folder per quarter:

  • The completed review sheet with decisions, dates and reviewer names.
  • User list exports or screenshots from before and after the changes.
  • A short note of exceptions, for example "kept shared login for supplier portal, password rotated 15 Dec".
  • Approval from the owner, which can be a signed PDF or a reply email.

If customer personal data sits in these systems, the review is also part of showing that you take reasonable security measures. Add it to your cybersecurity plan for small business, and pair it with an external website security check so both inside access and the public site are covered.

Action for today: create the folder structure, for example Access reviews / 2026-Q4.


Frequently asked questions

How often should a small business review user access?

Quarterly works for most small businesses. Review admin, banking and accounting access every quarter, and less critical tools at least twice a year. Also run an extra check after any security incident, a merger of systems, or when several people join or leave at once. Consistency matters more than frequency.

Who should perform a user access review?

The owner of each system, meaning the person who understands what access the business needs there. A coordinator collects the exports and the sheet, but decisions come from the owners. Nobody should approve their own access, so another person signs off the owner's or main admin's rows.

What is the difference between an access review and offboarding?

Offboarding removes access when a specific person leaves, on a specific day. An access review is a scheduled check of everyone's access across all systems. It catches what offboarding missed, people who changed roles, forgotten guest accounts and admin rights that were never reduced after setup.

Can I use a spreadsheet for access reviews?

Yes. For a company with a few dozen people and systems, a spreadsheet with the eight columns above is enough, as long as it is filled from system exports, dated and signed. Larger teams may later move to identity management tools that automate the exports and reminders.

Want help with your first access review?

We can export users from your systems, find leftover and admin access, and set up a quarterly review your team can run alone. Book a free consultation.

Book a free consultation