On this page
- How is a permissions audit different from a user access review?
- What does a Salesforce permissions audit cover?
- How do I run a Salesforce permissions audit, step by step?
- Which compliance controls does a permissions audit support?
- What can go wrong when you fix permissions, and how do I undo it?
- Which tools audit Salesforce permissions?
- How does Clientell AI run a permissions audit?
- Common questions about Salesforce permissions audits
A Salesforce permissions audit is a check of how access is built in your org, not only who holds it. It walks six layers: profiles, permission sets and groups, object and field permissions, sharing, special users, and the change trail. Run it once a year and before any big change.
Clientell AI, the AI Salesforce admin, audits profiles and permission sets, traces every risky grant to its source and proposes the smallest fix. The free, read-only permissions audit runs it on your own org.
How is a permissions audit different from a user access review?
They answer different questions, so run both. The audit fixes the design, such as a profile that grants Modify All Data. The review checks the people, such as a manager who left last month.
Swipe sideways to see all columns
| Permissions audit (this guide) | User access review | |
|---|---|---|
| Question | Is our access model sound? | Does each person still need their access? |
| Scope | Profiles, permission sets, groups, object and field permissions, sharing, special users | Holders of high-risk permissions such as Modify All Data |
| When | Once a year, and before a big change such as an Agentforce launch or an org merge | Every quarter |
| Who signs | The platform owner or security lead | Each user's manager |
| Output | A fix plan for profiles, permission sets and sharing | A signed list of holders, and the removals |
For the quarterly people check, follow the Salesforce user access review steps. This guide covers the design.
What does a Salesforce permissions audit cover?
Six layers grant access in Salesforce. Each one fails in its own way.
Swipe sideways to see all columns
| Layer | What it controls | What usually goes wrong | Where to look |
|---|---|---|---|
| Profiles | A user has exactly one profile (Trailhead) | Cloned profiles pile up with near-identical access | Setup > Users > Profiles |
| Permission sets and groups | A user can hold many permission sets. A permission set group bundles them by job role | Sets nobody owns, and sets assigned to nobody | Setup > Users > Permission Sets |
| Object and field permissions | Read, edit, delete, View All and Modify All Records per object. Field-level security per field | Sensitive fields readable on every profile | Object Settings on each profile or permission set |
| Sharing | Org-wide defaults, the role hierarchy and sharing rules decide which records a user sees | Public Read/Write defaults on objects with private data | Setup > Security > Sharing Settings |
| Special users and apps | Integration users, guest users, Agentforce agent users, and connected apps that sign in as users | An integration running on the System Administrator profile | Setup > Users > Users, and Setup > Apps > Connected Apps > Manage Connected Apps |
| Change trail and settings | Setup Audit Trail and Health Check | Changes nobody approved, and session or password settings below baseline | Setup > Security > View Setup Audit Trail |
Salesforce recommends a least-privilege model: profiles for baseline settings, permission sets for access (Salesforce Help). The profiles vs permission sets migration guide covers how to get there.
How do I run a Salesforce permissions audit, step by step?
Run these 10 steps in order. Every query below is read-only and runs with sf data query -o <your-org> -q "...". Start in a full sandbox if you have one.
-
Save a baseline of the metadata. You need it to undo any fix. Retrieve profiles, permission sets and permission set groups with
sf project retrieve start -m Profile -m PermissionSet -m PermissionSetGroup -m CustomObject. KeepCustomObjectin the same call. A retrieved profile only includes field-level security for objects returned in the same request (Metadata API Developer Guide). -
Count users per profile. Profiles with one or zero active users are candidates to merge or delete.
SELECT Profile.Name, COUNT(Id) users FROM User WHERE IsActive = true GROUP BY Profile.Name ORDER BY COUNT(Id) DESC -
Find permission sets assigned to nobody. Add
AND NamespacePrefix = nullto skip managed package sets and see only your own.SELECT Id, Name, Label, NamespacePrefix FROM PermissionSet WHERE IsOwnedByProfile = false AND Type = 'Regular' AND Id NOT IN (SELECT PermissionSetId FROM PermissionSetAssignment) -
Map each high-risk permission to its source. Query
PermissionSet, not users. Every profile owns a permission set, and every group has one with its combined permissions (PermissionSet object reference).TypeshowsProfile,RegularorGroup. Fix the source, not the user.SELECT Name, Type, Profile.Name FROM PermissionSet WHERE PermissionsModifyAllData = true OR PermissionsViewAllData = true OR PermissionsModifyMetadata = true OR PermissionsManageUsers = true OR PermissionsDataExport = true -
Check object-level overrides. View All Records and Modify All Records ignore sharing for one object (Salesforce Help). Run it for every object that holds money, health or personal data.
SELECT Parent.Name, Parent.Type, SobjectType, PermissionsViewAllRecords, PermissionsModifyAllRecords FROM ObjectPermissions WHERE SobjectType = 'Account' AND (PermissionsViewAllRecords = true OR PermissionsModifyAllRecords = true) -
Check field-level security on sensitive fields. List every profile and permission set that can read one field.
Contact.Birthdateis the example. Swap in your own fields.SELECT Parent.Name, Parent.Type, Field, PermissionsRead, PermissionsEdit FROM FieldPermissions WHERE SobjectType = 'Contact' AND Field = 'Contact.Birthdate' AND PermissionsRead = true -
Read the sharing defaults. Org-wide defaults set the floor for record access. Then review the role hierarchy and each sharing rule in Setup > Security > Sharing Settings.
SELECT QualifiedApiName, InternalSharingModel, ExternalSharingModel FROM EntityDefinition WHERE QualifiedApiName IN ('Account', 'Contact', 'Opportunity', 'Case') -
Review the special users. Integration users should run on an API-only profile with only the objects they touch. Agent users run on the Einstein Agent User profile and start with minimal access, which you expand on least privilege (Salesforce Help). With secure guest user record access on, guest users get Private defaults and Read Only sharing rules only (Salesforce Help).
Then open each connected app. With Permitted Users set to "All users may self-authorize" (the default), any user can connect it. "Admin approved users are pre-authorized" limits it to the profiles and permission sets you pick (Salesforce Help).
SELECT Name, Username, Profile.Name, UserType FROM User WHERE IsActive = true AND (Profile.PermissionsApiUserOnly = true OR UserType = 'Guest' OR Profile.Name = 'Einstein Agent User') -
Run Health Check. Setup > Security > Health Check scores your security settings against the Salesforce Baseline Standard, and you can upload up to five custom baselines (Salesforce Help). It covers settings such as password and session policies. It does not list who holds what.
-
Read the recent permission changes. Setup Audit Trail keeps 180 days of history (Salesforce Help). Check that each change below matches an approved request.
SELECT CreatedDate, CreatedBy.Username, Action, Display FROM SetupAuditTrail WHERE CreatedDate = LAST_N_DAYS:90 AND Action IN ('PermSetEnableUserPerm', 'PermSetGroupUserPermEnabled', 'profilePermChangedCustom') ORDER BY CreatedDate DESC
Write each finding as one row: layer, finding, risk, owner, fix and test plan. For example: "Profiles. Sales Ops profile grants Modify All Data. High. Owner: platform lead. Fix: move it to a named permission set for two admins. Test: run the lead routing flow in the sandbox." You are done when every high-risk permission in step 4 has a named owner and a decision.
Which compliance controls does a permissions audit support?
Most frameworks ask for the same thing: access granted on least privilege, changed only with approval, and reviewed on a schedule. The AICPA's SOC 2 criterion CC6.3 says it plainly:
"The entity authorizes, modifies, or removes access to data, software, functions, and other protected information assets based on roles, responsibilities, or the system design and changes, giving consideration to the concepts of least privilege and segregation of duties." AICPA Trust Services Criteria, CC6.3 (AICPA)
Swipe sideways to see all columns
| Framework | Control | What it asks | Salesforce evidence from this audit |
|---|---|---|---|
| SOX (IT general controls) | Access to financial systems | Approval of changes to privileged access, including roles, profiles and permission sets (Salesforce SOX best practices) | Step 4 map, step 10 changes with approvals |
| SOC 2 | CC6.1, CC6.2, CC6.3 | Least privilege, removal when no longer needed, periodic review of access roles | Steps 2 to 8, plus the quarterly review |
| ISO/IEC 27001:2022 | Annex A 5.15, 5.18, 8.2 | Access control policy, access rights reviewed, privileged rights restricted (ISO) | Steps 4, 5 and 8 |
| HIPAA Security Rule | 164.308(a)(4), 164.312(a)(1), 164.312(b) | Access only for authorized people, and audit controls on systems with health data (eCFR) | Steps 5, 6 and 10 |
| PCI DSS v4.0.1 | Requirement 7.2.4 | Review every account and its privileges at least once every six months (PCI SSC) | The quarterly user access review |
Your auditor's test plan decides the exact evidence. Bring the step 4 map, the step 10 export and the signed quarterly review.
What can go wrong when you fix permissions, and how do I undo it?
Most breakage comes from access that something quietly relied on. Plan for these cases:
- A flow or integration fails. It ran as a user who lost object or field access. Test each reduced profile or permission set in a sandbox with the real integration user before production.
- A profile deploy does less than you expect. Profile deployment overlays the settings in the file onto the target org (Metadata API Developer Guide). A permission missing from your file is left alone, not removed. Set it to
falseexplicitly. - A group change is not live yet. Salesforce recalculates a permission set group after each change. Test only when the group's status in Setup > Users > Permission Set Groups shows Updated.
- Removing a set does not remove the permission. Another set or group may still grant it. Use a muting permission set inside the group, or remove every source (Salesforce Help).
A fifth case catches teams tightening connected apps: switching Permitted Users in either direction revokes the app's existing tokens, so every integration on it must sign in again (Salesforce Help). Schedule that change with the integration owner.
To undo, deploy the baseline from step 1 back to the org. Because deploys overlay, this restores every permission the baseline held.
Which tools audit Salesforce permissions?
Swipe sideways to see all columns
| Tool | What it covers | Fits when |
|---|---|---|
| SOQL and Setup | Everything in the 10 steps. Nothing to install | You have a free afternoon per layer |
| User Access and Permissions Assistant | Free Salesforce app. Shows where a user's permissions come from, reports by user, permission set or group, and manages muting (Salesforce Admins) | Tracing one user or one permission |
| Health Check | Security settings against a baseline (Salesforce Help) | Password, session and network settings |
| Security Center | A separate Salesforce product that tracks permission assignments and Health Check scores across orgs (Salesforce) | Many orgs, and you already buy it |
| Clientell AI | All six layers in one pass, each risky grant traced to its source, with a drafted fix | You want the audit and the fix plan together |
How does Clientell AI run a permissions audit?
Clientell AI connects to your org and reads profiles, permission sets, groups, object and field permissions, and users. It flags users with admin-level access, integration users on admin profiles, and permission sets nobody uses. For each finding it proposes the smallest fix.
Safety, in plain words. The audit is a read-only scan. Clientell AI asks before it changes anything in production, and you can test every fix in a sandbox first. Each change it makes shows up in your own Setup Audit Trail. Details are on the security page.
Try it in Clientell AI: "List every user who can edit Opportunity amounts, show which permission set or profile grants it, and propose the smallest change that removes the extra access." Start the 14-day trial, no card.
For the quarterly people check, the access review checklist puts it on one page, and the step-by-step access review guide adds the Setup click paths.
Common questions about Salesforce permissions audits
How do I audit Salesforce permissions before a SOX or SOC 2 review?
Map every high-risk permission to its source (step 4), list unused permission sets and special users, and export Setup Audit Trail for the period. Then run a user access review so each holder is signed off. Hand both to your auditor.
How often should you audit Salesforce permissions?
Run the full audit once a year and before big changes, such as an Agentforce launch, a merger or a move from profiles to permission sets. Review the people who hold high-risk access every quarter.
Does Salesforce Health Check audit user permissions?
No. Health Check scores security settings, such as password and session policies, against a baseline. It does not show which users hold Modify All Data or which permission set grants it.
Is Salesforce removing permissions from profiles?
No. Salesforce cancelled the planned Spring '26 retirement in a Help article published 6 June 2026. As of October 2026, profiles still carry permissions, and Salesforce recommends permission sets for access (Salesforce Help).
What access should an Agentforce agent user have?
Only what its actions need. Salesforce creates the agent user with minimal access on the Einstein Agent User profile, and you add object access and permissions on least privilege (Salesforce Help). An agent can do anything its user can do, so audit agent users like admins.
Last updated: October 22, 2026




