All docs pages (49)

How to export field-level security to Excel in Salesforce

Query FieldPermissions and ObjectPermissions and export them with Data Loader, or use SFDC Police to download one Excel grid for many profiles.

Updated 2026-11-09

Salesforce stores field-level security as FieldPermissions records and object access as ObjectPermissions records, one set per profile or permission set, so you can query them and export the results to CSV with Data Loader. You then join and pivot the files in Excel yourself. SFDC Police reads the same records for the profiles, permission sets and permission set groups you pick, and downloads one Excel workbook with a column for each of them and a row for each object, field and tab.

Without an extension

Every profile has a permission set behind it that stores the profile's object and field permissions, and you can query it (PermissionSet reference). To query FieldPermissions and ObjectPermissions you need the View Setup and Configuration permission.

  1. In Data Loader, click Export, choose the PermissionSet object and use this query (Data Loader export steps): SELECT Id, Name, Label, IsOwnedByProfile, Profile.Name FROM PermissionSet Rows where IsOwnedByProfile is true belong to a profile, and Profile.Name tells you which one.
  2. Note the Ids of the profiles and permission sets you want to compare.
  3. Export FieldPermissions for those Ids: SELECT ParentId, SobjectType, Field, PermissionsRead, PermissionsEdit FROM FieldPermissions WHERE ParentId IN ('0PS...', '0PS...') Salesforce says to include both SobjectType and Field in the SELECT (FieldPermissions reference).
  4. Export ObjectPermissions the same way, with PermissionsCreate, PermissionsRead, PermissionsEdit, PermissionsDelete, PermissionsViewAllRecords and PermissionsModifyAllRecords (ObjectPermissions reference).
  5. Open the CSV files in Excel, match ParentId to the names from step 1, and pivot to one column per profile or permission set.

Why ParentId and not Parent.Name: the Data Loader guide says Data Loader doesn't support queries that use polymorphic relationships, and the Parent field on FieldPermissions and ObjectPermissions is polymorphic.

What to watch for:

  • No row means no access. A FieldPermissions record must have PermissionsRead set to true, or Salesforce deletes it. A field with no access for a profile has no row at all, so it is missing from your export rather than shown as "false".
  • Some fields never have rows. Id, CreatedById, CreatedDate, IsDeleted, LastModifiedById, LastModifiedDate and SystemModStamp are always readable; OwnerId, master-detail fields and universally required custom fields are always readable and editable.
  • View All Fields changes the answer. If a permission set has View All Fields on an object, PermissionsRead is true for every field of that object.
  • Modify All Data. Object permissions that come from Modify All Data have a record Id starting with "000" and can't be updated.

With SFDC Police

In version 1.1.13 the module is called Data Dictionary; later versions rename it Permission Matrix.

  1. Open SFDC Police in a full tab and choose Data Dictionary in the menu.
  2. Tick what you want to compare in the Permission Sets, Profiles and Permission Set Groups lists. A permission set group is expanded into the permission sets it contains, and each gets its own column.
  3. Click Generate. SFDC Police queries ObjectPermissions, FieldPermissions and tab settings for your selection and reads every page of results.
  4. Click Download Excel. The file is named DataDictionary_ plus the date.

The workbook has up to three sheets. A sheet with no rows is left out.

SheetColumns
Object PermissionsObject Name, Object API, then one column per profile or permission set. Cells hold C R E D VA MA VAF letters (Create, Read, Edit, Delete, View All, Modify All, View All Fields).
Field PermissionsObject Name, Object API, Field Name, Field API, Data Type, Field Type, Picklist Values, Required, then one column per profile or permission set. Cells hold R or RE.
Tab VisibilityTab Name, then one column per profile or permission set.

Column headers read Profile:<profile name> or PS:<permission set API name>. The download holds every row, not only the rows your search box shows.

Limits in 1.1.13:

  • The data comes from the same records as the native method, so a blank cell means that column has no permission row, and a field appears only if at least one selected column has a row for it.
  • The name columns repeat the API names. Data Type, Picklist Values and Required are present but empty. Field Type is Standard, Custom or Managed, worked out from the API name.
  • The Muting Permission Sets list is there, but in 1.1.13 a muting permission set adds no permissions to the results. Don't use the file to check muting.
  • If tab settings can't be read in your org, the file has no Tab Visibility sheet.

Editing permissions from the file

You can change R/RE or object letters in the file and upload it in Apply Changes (from the release after 1.1.13: Permission Matrix → Import from Excel). It reads the Object Permissions and Field Permissions sheets, compares them with your org and lists the differences. Click Deploy N Changes, then Deploy Changes in the confirm dialog. If any profile changes, you must type DEPLOY first; for permission set changes only, there is no typing step.

In 1.1.13, Apply Changes only updates permission rows that already exist. Blank cells are skipped, so it can't grant access to a field that has none, and emptying a cell doesn't remove access. For those changes, use Edit Mode in Data Dictionary, then Push to Salesforce.