All docs pages (49)

Import from Excel (Apply Changes)

Upload an edited Permission Matrix Excel file, review the differences from your org, and push the object and field permission changes you select.

Updated 2026-11-10

Import from Excel (Apply Changes) in SFDC Police

Import from Excel pushes permission edits made in Excel. Export the Permission Matrix (called Data Dictionary in versions up to 1.1.13) to Excel, change the permissions in the file, and upload it here. It compares the file with your org, shows what is different, and pushes the changes you select.

Where to find it: in the release after 1.1.13, open Permission Matrix and choose the Import from Excel tab, next to Matrix. In version 1.1.13 and earlier it is its own page, Apply Changes, in the sidebar. The flow is the same in both; old Apply Changes links open the new tab. The rest of this page calls it Apply Changes, the name in the current store version.

Top screenshot: 1 Drop an exported .xlsx file here, or click to browse. 2 Show Transaction History.

Features

Change Review

After you upload the .xlsx file, you see every difference between the file and the org:

  • Object permission changes
  • Field-level security changes

Only settings that already exist in the org can change: if the permission set or profile has no permission row for that object or field (usually because it gives no access to it at all), that change is skipped. To grant access for the first time, use edit mode in the matrix instead. Blank cells in the file are ignored, not read as "no access". Type permissions the way the export writes them, letters together (for example CRED for an object, RE for a field). In version 1.1.13 a cell that isn't written that way, such as R E, Read or FALSE, is read wrongly: R E as no access at all, and Read as Read, Edit and Delete. Check the Current and New columns before you deploy. In the release after 1.1.13 such a cell is skipped and listed instead.

You also see which permission sets and profiles change, with a count, and a warning when a profile changes, because a profile change affects every user on that profile.

If the uploaded file has nothing different from the org, the page shows nothing in version 1.1.13. In the release after 1.1.13 it says "No differences", which means everything the file can change already matches the org.

In the release after 1.1.13, the extra sheets of a Permission Matrix export (System Permissions, Setup Access, Record Types & Layouts and About this export) are ignored.

Apply Changes after uploading an edited file: one object change, Edit on Account for the Sales Agreements permission set, from not granted to granted, with the Deploy 1 Change button

1 The uploaded file. 2 How many object and field changes it holds. 3 Show all, object or field changes. 4 The current value in the org. 5 The value in the file. 6 Deploy the ticked changes.

Selective Deployment

You don't have to push everything at once:

  • Check or uncheck individual changes
  • Filter to object or field changes, or search the list
  • Changes go to the org you are connected to. Try them in a sandbox first.

Deployment

Apply Changes updates the permission records (ObjectPermissions and FieldPermissions) through the Salesforce REST API. No XML, no Change Sets. If a profile changes, you must type DEPLOY to confirm.

Results and Log

  • The results screen shows how many rows succeeded and lists each failed change with Salesforce's error.
  • Successful changes are also listed in Access Editor's Transaction History, stored in this browser only: the time, the action, the status and a short summary. The User column shows the org Id, not the person who made the change.

Undo

Keep an unedited copy of the exported file: uploading it again pushes the old values back. That works in every version.

A push is also listed in Access Editor → Transaction History, with the old values of each row:

  • A push of up to 25 rows of one kind (object or field permissions) is logged row by row, and Rollback puts a row back.
  • A larger push is logged as one entry. In version 1.1.9, rolling that entry back can show as done without anything changing, so check the values in Salesforce. From version 1.1.13 it is refused instead, with nothing changed. In the release after 1.1.13 it is reversed all or nothing, up to 200 rows.

Rows that failed were never written, so there is nothing to undo for them.

Best Practices

  • Apply to a sandbox before production
  • Check which profiles change: a profile change affects all of its users
  • Keep the exported and edited Excel files as your record of the change
  • Pair with Persona Simulator to verify changes after the push