How to run a user access review in Salesforce

The short answer: A Salesforce user access review is a scheduled check that every active user’s access still matches their job, with a named person’s decision recorded. You can run one by hand: list active users, open each one’s access summary, query who holds the high-risk permissions, record keep or remove, and save the export. Do it at least yearly, and quarterly for the riskiest permissions.

Say a contractor’s agreement ended in June. In November, someone notices the user is still active, still on a permission set called “Temp”, and still able to export reports. Nobody did anything wrong in the moment. Access doesn’t expire by itself, and nobody was assigned to look.

That’s what a review is for. It’s an unglamorous job, and the manual version is more doable than the dread suggests.

What is a user access review, and why do auditors ask for one?

It’s a periodic check, owned by a person with authority, that each user’s access is still appropriate, plus a record of what was decided. Auditors ask because access piles up quietly: people change roles, contracts end, and nobody removes what is no longer needed.

As reported by Security Boulevard, its SOC 2 guidance is to review user access at least annually, with quarterly reviews recommended, and to keep logs of each review and of how any problems were resolved. The same article tells readers to confirm the exact expectations with their auditor, which is good advice. Your auditor sets the frequency and the evidence format, so ask before you design the process.

What should the review cover?

Cover every active user, plus the other things that can act like one. That means:

  • Active users: their profile, role, and the permission sets and permission set groups assigned.
  • Integration users, which usually hold broad access and rarely get reviewed.
  • Any agent user, if you run AI agents. Our post on telling what an AI agent changed explains why the agent’s user matters.
  • Public groups and queues, which grant record access that isn’t visible on the permission screens.
  • Users who haven’t logged in for a long time but are still active.

One housekeeping note: permissions on profiles aren’t going away on a fixed date. As reported by Salesforce Ben in July 2026, Salesforce updated its knowledge article to say the planned retirement was cancelled, while still recommending a permission-set-led model. So you’ll be reviewing both profiles and permission sets for a while.

How do you run a user access review with native tools?

Use five steps. Each uses something already in Setup or the query editor.

  1. Export the active users. A report or list view with name, username, profile, role, active flag and last login. This is your population, and you’ll attach it to the evidence file.
  2. Open a user’s access summary. In Setup, search Users, open a user and choose View Summary. As reported by Salesforce Ben, it arrived in Summer ’24 and shows object and field permissions, user permissions, public group and queue membership and custom permissions on separate tabs. Do this for a sample, or for everyone with broad access.
  3. Open the permission sets they hold. View Summary on a permission set shows its object, field and custom permissions and the permission set groups it belongs to. Salesforce Ben described this summary as beta at the time and heading for general availability, so check what your org shows.
  4. Query who holds the high-risk permissions. In the Developer Console query editor or your preferred client, run the query below. Swap the permission field for each one on your list.
  5. Record a decision for each person. Keep, change or remove, with the reviewer’s name and the date. Then make the changes and note when you did.
SELECT Assignee.Name, Assignee.Username, PermissionSet.Label, PermissionSet.Profile.Name
FROM PermissionSetAssignment
WHERE Assignee.IsActive = true
AND PermissionSet.PermissionsModifyAllData = true

As we understand the data model, every profile has a permission set behind it, so don’t filter those out. Check that your results include a known administrator before you trust the query. Users who get a permission through a profile should appear alongside those who get it through a permission set.

For a single field, there is a newer option. As reported by salesforcebreak, a Field Access Summary in Object Manager shows one field’s access across profiles, permission sets and permission set groups. That source described it as in preview in Summer ’26, not generally available, so treat it as a bonus.

Which permissions should you check first?

Start with the ones that bypass the sharing model or move data out. This is our short list, from practice, not an official Salesforce one. As reported by Salesforce Ben, its least-privilege guidance flags Modify All Data, API access and report exports among high-risk permissions to monitor.

PermissionWhy it goes firstQuery field
Modify All DataRead, edit and delete every record, whatever sharing saysPermissionsModifyAllData
View All DataRead every record, whatever sharing saysPermissionsViewAllData
Export ReportsSends report data out of SalesforcePermissionsExportReport
Manage UsersCan create users and change what others can doPermissionsManageUsers
API EnabledOpens the door to data loaders and integrationsPermissionsApiEnabled

API Enabled is the one that trips people up. Integration users need it, but a sales rep who has it can pull data through tools you never see. Ask for every holder to have a reason you can write in one line.

How often should you run a user access review?

Run a full review at least once a year and a short one every quarter, covering only the five permissions above. That follows the pattern Security Boulevard reports, though your auditor has the final say.

Add triggers on top of the calendar. Review someone’s access when their role changes, when a contract ends, and when an acquisition or reorganization moves people around. Those events are where access piles up, so don’t wait for the next quarter.

What evidence should you keep?

Keep enough that someone who wasn’t there can follow what happened. For each review:

  • The exported user list, dated.
  • The query results for each high-risk permission, dated.
  • Each decision, with the reviewer and the date.
  • A note of every change made and when.
  • A Setup Audit Trail export covering the period.

On that last item: as reported by Salesforce Ben, Setup Audit Trail shows the last 20 changes on screen and a CSV download covers the last 180 days. It records permission and profile changes with the user who made them, so it’s your proof that the removals happened. Save the file, because it won’t keep it for you. Also as reported, Winter ’27 moves access to the trail behind a dedicated View Setup Audit Trail permission, as a release update that preserves existing access. We’ll cover it in a separate post.

User Access Policies can automate granting and removing access, but as reported by Salesforce Ben, their Recent User Access Changes view shows only changes from policies still in effect. It isn’t a complete history, so don’t treat it as evidence.

What to do Monday:

– Run the query above for Modify All Data and write down every name.

– Next to each name, write one line saying why they need it. Where you can’t, flag it.

– Export the active user list and the Setup Audit Trail, and save both in a dated folder.

– Ask your auditor how often they expect a review, and what format they want.

Where we come in

Watchbill, by GTM Cloud, is pre-release and isn’t publicly listed yet. It shows every permission with what grants it, answers who can do a thing, compares users and permission sets, keeps snapshots and a change history, and runs a review campaign that managers finish and that closes with a sign-off. Version 1 only reads access and changes none. See the Watchbill page, or ask our Salesforce services team to work through an audit with you.

Questions people ask

How do I find everyone with Modify All Data in Salesforce?

Query PermissionSetAssignment for active users where the permission set’s PermissionsModifyAllData is true, as in the example above. Profiles are included because each has a permission set behind it. Check that a known administrator appears in the results, then compare the count against what you expected.

Does Salesforce have a built-in access review?

We didn’t find a native review-and-sign-off workflow in the sources we read. The native tools show access: View Summary, permission set summaries and queries. A manager’s decision and the evidence of it still need a document or spreadsheet that you keep yourself.

How long should I keep access review records?

Ask your auditor. Retention periods come from your compliance framework and your contracts, not from Salesforce. Keep the records somewhere the audit team can reach, with the dates visible, and plan to keep the export files even after the org’s own logs have rolled off.

Sources