All docs pages (49)

Compare (PS Comparison)

Put two permission sets side by side and see which object and field permissions differ, which objects only one of them covers, and export the diff as CSV.

Updated 2026-11-09

PS Comparison answers "what does this permission set grant that that one doesn't?" You pick two permission sets and see their object permissions next to each other, with the differences marked, and you can open any object to compare its field permissions. Open Permissions → PS Comparison. The page heading is Permission Set Comparison.

In the release after 1.1.13 the sidebar entry is called Compare and has two tabs: Permission sets & profiles (this screen, which opens first, so old links behave as before) and Users (two users side by side, the same comparison as Explain Access → Compare Users). The rest of this page describes the permission set screen as it works in 1.1.13.

How to use it

  1. Under Side A, pick a permission set from the list (-- Select permission set --). Each entry shows the label and the API name.
  2. Under Side B, pick the second one. A permission set chosen on one side is greyed out on the other; if both sides end up the same, the page says Please select two different permission sets to compare.
  3. Click Compare. It reads Comparing... while it loads.
  4. Use the filter tabs to narrow the table: All, Different, Only in Side A's label, Only in Side B's label. Each tab shows its count.
  5. Click an object row to open its field permissions. Click it again to close it.
  6. Click Export Diff as CSV to download the comparison.

What you see

Summary chips above the table count the objects that are identical, different, only in Side A, and only in Side B.

The object table has one row per object that either permission set has an object permission row for, sorted by API name. For each permission there are two columns, A and B: Create, Read, Edit, Delete, View All Records, Modify All Records and View All Fields. A granted permission shows Y, a missing one shows -, and cells that differ between the sides are highlighted. Objects that only one side covers carry an Only A or Only B badge.

The Different tab lists objects both sides cover where at least one permission differs. Objects covered by only one side are counted under their own tabs, not under Different.

Field permissions. When you open an object, a second table lists every field that either permission set has a field permission row for, with Read and Edit for each side. If neither has any, it says No field permissions configured for either permission set on this object.

The CSV (permission-diff-<timestamp>.csv) has one line per object with true/false for each permission on each side and a Diff column (YES or NO). Fields are added only for the objects you opened before exporting.

What it reads and writes

  • The permission set list: PermissionSet records that are not owned by a profile, ordered by label.
  • For each side: its ObjectPermissions rows.
  • When you open an object: the FieldPermissions rows for that object, for each side.

It reads from the org you are connected to and changes nothing. It is a read-only view; to change a permission set, use Access Editor or Permission Builder.

Limits

  • Profiles are not in the list. Only permission sets that are not owned by a profile can be picked, so you can't compare a profile with a permission set here.
  • View All Fields always shows "-" on both sides in version 1.1.13: the object permission query does not read that permission, so the column can't show a grant. Check it in Salesforce Setup. Fixed in the release after 1.1.13.
  • Field rows in the CSV are misaligned in version 1.1.13: a field's Read and Edit values are written under the Create and Read columns of the header. Use the on-screen field table for field permissions. Fixed in the release after 1.1.13.
  • Results are cached: the permission set list for 15 minutes, and object and field permissions for 30 minutes. A change made in Setup during that time may not show yet.
  • An object with no object permission row on either side does not appear, even if a field on it has field permissions.
  • It compares two permission sets as stored. It does not show what a user gets from all their permission sets, groups and profile together; for that, see Explain Access (called Permission Intelligence in 1.1.13).