Skip to main content

Salesforce Permissions Audit: Too Many Admins and an Audit Coming Up

Start the 14-day Platform trial, no card, and run an access review of your production org yourself. Review System Administrators, broad data permissions and integration users before a SOX or SOC 2 review.

Last updated
By the Clientell AI teamHow we write

SOX is Sarbanes-Oxley, the US law on financial controls. SOC 2 is System and Organization Controls 2, a security audit report.

Clientell supports access reviews of your connected org. Nothing changes in your org without your approval.

For the wider picture, see the Salesforce health check.

Access review checks

What should you review in your org?

Each pattern has a cause, a risk and a fix path.

FINDING ACritical
Too many admins

System Administrator overuse

Check every System Administrator assignment against a current business need. Agree on narrower access where that need does not require full administration.

FINDING BCritical
Full admin

Integration users with admin access

Check whether each integration needs its current permissions. Record an owner and a test plan before reducing access.

FINDING CCritical
Never cleaned up

Stale permission sets

Sets created for a project, abandoned and never removed. Each one is a future "where did this access come from" question.

FINDING DCritical
Paid but idle

Inactive users still licensed

Review users with old login dates alongside their managers and integration owners. Confirm whether the account is still needed before changing its access or license.

Review
User access
Changes
Your approval required
Examples
Patterns to investigate
The Risk Matrix

Where did each risky permission come from? Example risk matrix.

Illustrative example: explore fictional profiles and users to see access paths to investigate. Names, counts and grant sources are not customer results or product guarantees.

Access pathsProfiles and permission sets
Source visibilityProfile + permset
Sample orgDemo org
illustrative figures
Coverage Areas

What does a Salesforce permissions audit cover?

Six areas to review with your access owners before changing production.

A

Users with broad access

Review users with System Administrator, View All Data or Modify All Data. Record why each person needs that access and who will approve any change.

B

Effective access drill-down

Review the profiles, permission sets and sharing paths that grant access. Clientell supports access reviews using the structure of your connected org.

C

Profile review

Compare profiles and document their purpose. Before consolidating them, check which users depend on each grant and test proposed changes in a sandbox. Source: Comparing Security Models (Salesforce Help).

E

Integration user least-privilege audit

Identify integration users with admin-level access. Work with the integration owner to document required permissions and test a narrower access model before changing production.

F

Role hierarchy + sharing review

Review role hierarchy, sharing rules and organization-wide defaults alongside profiles and permission sets. Record which paths grant access to sensitive records.

How can I review access? Illustrative example

Illustrative access paths and review actions, not product output.
Grant sourceAccessWhat it meansRecommended action
Admin profileModify All DataBroad administrative permissions require a documented business need.Confirm the need with the owner and test narrower access.
Reporting permission setView All DataThis permission grants visibility beyond sharing rules.Confirm the reporting requirement and test narrower access.
Data Loader permission setAPI EnabledThe user can access enabled APIs within their permissions.Review the integration owner and required object access.
Sales profileAccount ReadObject access still depends on field permissions and record visibility.Document the business need and test expected record access.
Warning Signs

Should you run the audit before any of these?

Cleanup is easier before an auditor, an agent or a breach forces it.

A

Your SOC 2 audit is coming up

Document who has access to customer data, why they need it and when it was reviewed. Agree on the evidence your auditor needs rather than treating a product report as proof of compliance.

B

An admin or contractor just left

Review the departing person’s account, permission assignments and integration ownership. Document any retained access and the person responsible for removing it.

C

Your org has dozens of profiles

Compare profile purposes and assignments. Document overlap before proposing consolidation, then test the proposed changes in a sandbox. Source: Comparing Security Models (Salesforce Help).

E

You inherited the org from a previous admin

Start by documenting who has access to what. Connect your production org and run an access review yourself before proposing permission changes.

Deliverables

What do you get with the audit?

Five areas to investigate during your self-serve access review.

A

Broad-access user review

Use the access review to examine users with broad permissions. Document their business need and agree on which assignments to review first.

B

Access paths to investigate

Review profiles, permission sets and sharing paths. Keep your findings and decisions in the evidence format agreed with your compliance team.

C

Profile cleanup review

Use your org’s permission structure to investigate overlapping profiles. Test proposed changes before approving them for production.

D

Permission set review

Review sets with no active users alongside their owners. Confirm dependencies and business requirements before deciding what to remove.

E

Approval before changes

Nothing changes in your org without your approval. Review the proposed change and its business impact before proceeding.

Access review

Who in your org can see, export or delete everything?

You can start by hand. Each check below uses a Setup page and a query that Salesforce documents. Run the queries with the Salesforce CLI (sf data query -o your-org -q "...") or your SOQL tool. Match each result to an owner and a business reason. For a self-serve product review, start the Platform trial and connect your production org.

Check 1

Who holds Modify All Data?

Setup path: Quick Find box, type Permission Sets, then open Permission Sets. Open a set and click App Permissions or System Permissions to read what it grants.

Salesforce calls Modify All Data "the highest level of data access". It overrides all sharing rules and object-level permissions. The first query lists every active user who holds it, from a profile or a permission set. Profiles show up because each profile keeps its permissions in a permission set it owns (IsOwnedByProfile = true).

SELECT AssigneeId, PermissionSet.Name, PermissionSet.IsOwnedByProfile
FROM PermissionSetAssignment
WHERE PermissionSet.PermissionsModifyAllData = true
AND Assignee.IsActive = true

SELECT PermissionSetGroupId
FROM PermissionSetAssignment
WHERE PermissionSetGroupId IN (
  SELECT PermissionSetGroupId FROM PermissionSetGroupComponent
  WHERE PermissionSet.PermissionsModifyAllData = true
  OR PermissionSet.PermissionsViewAllData = true)
AND Assignee.IsActive = true

Swap PermissionsModifyAllData for PermissionsViewAllData to find who can read every record. The second query finds permission set groups, assigned to active users, that include either permission.

Sources: Modify All Data Permission in Salesforce (Salesforce Help); PermissionSet object reference (Salesforce Developers); PermissionSetAssignment object reference (Salesforce Developers).

Check 2

Who can take data out, or delete it for good?

Setup path: Quick Find box, type Data Export, then open Data Export. See whether a weekly or monthly export is scheduled.

Export Reports lets a user export report data. Weekly Data Export lets a user export all org data as CSV files. By default, Salesforce gives it only to the System Administrator profile. Bulk API Hard Delete lets a user delete records permanently, bypassing the Recycle Bin. It is not on the standard System Administrator profile.

SELECT AssigneeId, PermissionSet.Name
FROM PermissionSetAssignment
WHERE PermissionSet.PermissionsDataExport = true
AND Assignee.IsActive = true

Run it again with PermissionsExportReport, then with PermissionsBulkApiHardDelete. Three short runs show everyone who can export or delete.

Sources: Export Backup Data from Salesforce (Salesforce Help); How to Enable the Bulk API Hard Delete Permission (Salesforce Help); User Profile permission descriptions (Salesforce Help).

Check 3

Who holds Modify All Data and has not logged in for 90 days?

Setup path: Quick Find box, type Users, then open Users to see the user list.

Powerful access that nobody uses is the easiest access to remove. Salesforce updates a user's LastLoginDate when at least 60 seconds have passed since their last login, which is accurate enough for a stale-login test. Users who never logged in have no date, so the query checks for that too.

SELECT AssigneeId
FROM PermissionSetAssignment
WHERE PermissionSet.PermissionsModifyAllData = true
AND Assignee.IsActive = true
AND (Assignee.LastLoginDate < LAST_N_DAYS:90
  OR Assignee.LastLoginDate = null)

Sources: User object reference (Salesforce Developers); View and Manage Users (Salesforce Help).

Official Salesforce sources: Modify All Data Permission in Salesforce (Salesforce Help); Comparing Security Models (Salesforce Help); User Profile permission descriptions (Salesforce Help); How to Enable the Bulk API Hard Delete Permission (Salesforce Help); Export Backup Data from Salesforce (Salesforce Help); Permissions in Profiles Retirement Cancelled (Salesforce Help, published 6 Jun 2026); PermissionSet object reference (Salesforce Developers); PermissionSetAssignment object reference (Salesforce Developers); Boost Security by Auditing Your Privileged Users with SOQL (Salesforce Developers blog); Salesforce Best Practices Around IT Compliance for SOX (salesforce.com, PDF); User object reference (Salesforce Developers); View and Manage Users (Salesforce Help).

FAQ

You have
questions,
we have
answers.

What compliance, security and admin teams ask before a permissions audit.

A

How do I audit Salesforce permissions before a SOX or SOC 2 review?

List users with System Administrator, unused permission sets, integration users with admin profiles and inactive licensed users. Keep the report as evidence for your auditor.

B

Is there a free Salesforce permissions audit?

Start the 14-day Platform trial, no card, and run an access review of your production org yourself.

C

What should permission audit software check?

Review broad data access, permission assignments, integration users with admin rights and accounts that may no longer be needed.

D

What is a Salesforce permissions audit?

A permissions audit checks who can do what in your org. It surfaces over-permissioned users, stale permission sets, integration users with too much access, and the gap between what users can access and what they need. Every permission is traced back to the profile or permission set that granted it.

E

How much does a Salesforce permissions audit cost?

The Clientell Platform is $500 a month and includes access review. You can start a 14-day trial with no card. The trial clock starts when you connect your first org.

F

How do I start a permissions audit?

Start the Platform trial, connect your production org and run an access review yourself. Review the findings with the people who own the affected access. Nothing changes in your org without your approval.

G

Is the permissions audit free?

Access review is included in the 14-day Platform trial, no card required. After the trial, the Platform is $500 a month.

H

What is "effective access" in a Salesforce permissions audit?

Effective access is every permission a user really has, whether it came from a profile, a permission set, a permission set group or a role hierarchy. Most audits stop at "this user has this profile and these permission sets". Effective access traces each single permission to the assignment that granted it. Auditors want this view in a SOC 2 or ISO 27001 review.

I

What does Clientell add to a manual review?

Clientell supports access review using your connected org’s structure, including permissions. You still decide which access is justified and approve changes before they happen.

J

How many profiles should a Salesforce org have?

Choose a profile structure that fits your org’s business needs. Compare existing profiles and permission sets, document overlap and test any consolidation before changing production. Source: Comparing Security Models (Salesforce Help).

K

What percentage of users should hold System Administrator?

Use business need, not a universal percentage, to decide who needs System Administrator. Review broad permissions with each user’s manager and test narrower access before removing it. Source: Modify All Data Permission in Salesforce (Salesforce Help).

L

Does the audit work for integration users?

Include integration users in your access review. Identify accounts with admin-level access, confirm the permissions needed with each integration owner and test any reduction before changing production.

M

What permissions does the audit need to scan my org?

Clientell reads records live under your own Salesforce permissions and does not store record data. Its graph holds structure, not contents. Review the connection permissions before connecting. Nothing changes in your org without your approval.

Trusted by leaders at

LytxTalkspaceNuloPixisAppsmithCoreViewConstella IntelligenceGoviniSunbelt SolomonSafety VisionCurrier PlasticsIESVEGlobusGushworkIrys AIProdigyPAM HotelsPalletized TruckingDallas HabitatRIM AllianceStonewood PartnersEncore FocusCreatiquetechSkyaLynx9DeploidDGAOppcoLytxTalkspaceNuloPixisAppsmithCoreViewConstella IntelligenceGoviniSunbelt SolomonSafety VisionCurrier PlasticsIESVEGlobusGushworkIrys AIProdigyPAM HotelsPalletized TruckingDallas HabitatRIM AllianceStonewood PartnersEncore FocusCreatiquetechSkyaLynx9DeploidDGAOppco

Customer Testimonials

Results that speak for themselves

How teams are clearing backlogs, cutting consulting costs 80%, and actually shipping Salesforce work on time with the AI agent, managed services, or both.

AI Agent
“Clientell AI didn’t tell me what to do in Salesforce. It did it for me. It built the Flow. It created the test data. It let me validate everything right inside my org. My role was still the same: inspect, test edge cases, and make sure the automation made sense. But the heavy lifting was handled by the AI. Clientell AI is not instructions. It is execution inside Salesforce.”

Julian
JulianSalesforce Leader
Managed Services
“Moving to Clientell AI has been a game-changer for our lead routing, giving us full visibility into where our leads are going.”
Tevia Arnold
Tevia ArnoldSVP Marketing, Insite.AI
Managed Services
“Clientell AI has helped us accelerate the pace of developing any Salesforce requests, including complex, custom logic. Their knowledge and experience helps us make decisions faster.We have had multiple use cases completed within a short span of time. If you have Salesforce, their team is a great addition for your GTM stack!”

Neel Pattani
Neel PattaniDirector, RevOps, Appsmith
AI Agent
“As an Admin with 10 years experience, I was skeptical of AI performing system configuration tasks accurately. When I put Clientell AI through some paces I had to rethink what was possible. I checked my Salesforce org and there were 10 new fields in a fraction of the time to configure one-by-one. There are hundreds of hours to be saved each year with repetitive tasks we perform in each sandbox.”

Justin Dux
Justin DuxSr Salesforce Administrator, Minnesota IT Services

Real teams. Real orgs. Real Salesforce instances.

Getting Started

Start your 14-day
Platform trial.

Start the 14-day Platform trial, no card, and run an access review of your production org yourself. Nothing changes in your org without your approval.

14-day free trial  ·  No credit card required

SOC 2
HIPAA
ISO 27001
Salesforce Partner