All docs pages (49)
Which permission set gives a user access in Salesforce?
In Setup, open the user, click View Summary, then choose Access Granted By on a permission to see the profile, permission sets or groups that grant it.
Updated 2026-11-09
In Setup, open the user, click View Summary, find the permission, open its row-level action and click Access Granted By. Salesforce then lists the profile, permission sets or permission set groups that grant it. You can get the same answer with SOQL by joining PermissionSetAssignment to ObjectPermissions or FieldPermissions. In SFDC Police, open Access Editor, pick the user, and use Explain Access to see which permission set, permission set group or profile grants one object, field, record type or page layout permission, or that none does.
In Salesforce
User Access Summary. Salesforce documents this in View a User's Access Summary and Troubleshoot Feature Access Issues:
- From Setup, in the Quick Find box, enter Users, then select Users.
- Select the user and click View Summary. You need View Setup and Configuration.
- Find the permission among the user's object, user and field permissions.
- Click the permission's row-level action, then click Access Granted By.
To see everything inside one permission set or permission set group, open it and click View Summary (permission set summaries).
SOQL. The PermissionSet object reference explains that every profile has a permission set that stores the profile's permissions, marked IsOwnedByProfile = true. So one query covers the profile and the permission sets. Adapted from the reference's example, this query lists what grants Edit on Account to one user:
SELECT PermissionSet.Label, PermissionSet.IsOwnedByProfile,
PermissionSet.Profile.Name, PermissionSetGroupId
FROM PermissionSetAssignment
WHERE AssigneeId = '005XXXXXXXXXXXX'
AND PermissionSetId IN (
SELECT ParentId FROM ObjectPermissions
WHERE SobjectType = 'Account' AND PermissionsEdit = true)
For a field, query FieldPermissions instead. Apex class access is stored in SetupEntityAccess, not in these objects.
The catches:
- Profiles appear as permission sets. For a profile-owned permission set, read
Profile.Name. Salesforce says the Name and Label of these permission sets can change. - No row means no access. Salesforce stores a permission as a record and stores no record when there is no access, so you can't query for "no access" directly.
- Permission set groups. A group assignment fills
PermissionSetGroupId. The group's members are inPermissionSetGroupComponent, and a member can be a muting permission set. - Muting. A muting permission set removes permissions only inside its own group. If the profile, another permission set or another group grants the same permission, the user keeps it.
- Session-based permission sets. These are valid only for the session in which they are activated, and
PermissionSet.HasActivationRequiredmarks them. An assignment row does not prove the user has the permission right now. - Who can query. Only users with View Setup and Configuration, Assign Permission Sets or Manage User can read
PermissionSetAssignment.
With SFDC Police
- In the sidebar, open Permissions, then Access Editor.
- Search for the user by name or email and select them.
- In the Explain Access panel, choose a Permission Type: Object Permission, Field Permission, Record Type or Page Layout.
- Pick the Object, then the Permission (Read, Create, Edit, Delete, View All Records or Modify All Records for an object; Read or Edit for a field), or the field or record type.
- Click Explain.
The result shows a GRANTED or NOT_GRANTED badge and a Top Reason, such as Granted via Permission Set "Sales Ops". Three tabs show the detail:
- Grant Paths: each permission set that grants it. A permission set inside a group shows "via" and the group's name. Badges show PS, PSG or MUTED.
- Muted: muting permission sets that mute this permission in one of the user's groups.
- Overrides: the profile, if the profile grants it.
To find the permission sets inside groups, Explain Access reads the group's members and recognizes muting permission sets by their 0QM Id prefix. For a field, it counts the grant only when the user also has object Read (and object Edit for field Edit). When that object access is missing, the Top Reason says so. For a page layout, it shows the layout that the user's profile assigns. Export Evidence saves the result as a JSON file.
To compare two users, open Permissions, then Permission Intelligence, then Compare Users (from the release after 1.1.13: Explain Access → Compare Users, or Compare → Users). Pick User A and User B, and click Compare. Leave Object blank to compare object permissions across all objects, or pick an object to compare its fields. Each row is marked Divergent or Match.
Limits. Explain Access checks one permission at a time. It does not explain user or system permissions (such as API Enabled), Apex class access or custom permissions; use the User Access Summary for those. For object permissions in 1.1.13, it reads object permission records only, and does not list View All Data or Modify All Data as a source. In the release after 1.1.13 they count: View All Data gives Read and View All, Modify All Data gives every object permission except View All Fields, and the answer names the profile or permission set that holds them. Neither overrides field-level security. It does not check whether a session-based permission set is active, so it lists one as a grant path even when it is not activated.
Record access is a different question
Object and field permissions decide what a user can do with a type of record. They do not decide which records the user can see. That is decided by sharing: ownership, roles, sharing rules and similar layers. For that question, read Why can this user see this record? and The 10 Layers of Record Access.