All docs pages (49)

Permission Builder

Build permission sets with object and field permissions, check the objects they depend on, preview the payload, and compare two permission sets.

Updated 2026-02-15

Permission Builder in SFDC Police

Permission Builder creates permission sets without clicking through Setup page by page. You pick objects, set object and field permissions, check dependencies, and create the permission set in your org.

Top screenshot: 1 The tabs: Setup, Permissions, Fields, Graph, Payload. 2 Template name. 3 Object search. 4 Add Object. 5 Objects added. 6 Missing-dependency warning.

Features

Permission Set Creation

Permission Builder has five tabs: Setup, Permissions, Fields, Graph and Payload. A bar at the bottom stays on screen with the dependency check and the Create New, Export XML, Copy JSON and Download buttons.

  1. Setup: name the template, search for objects and click Add Object for each one. To start from a permission set that already exists, click Load Existing PS at the top.
  2. Permissions: tick the object permissions for each object (Create, Read, Edit, Delete, View All Records, Modify All Records, View All Fields).
  3. Fields: set field permissions.
  4. Graph: see the objects you added with the objects they relate to, as a graph or a table, so you can see what else the permissions may need.
  5. Payload: see the Salesforce API payload that Create New would send, before you create anything.

Permission Builder Permissions tab with Account and Contact rows and Create, Read, Edit, Delete, View All, Modify All and View All Fields columns

1 Fields tab, for field permissions. 2 Filter objects. 3 Read ticked for Account. 4 Auto-Add for the missing dependencies. 5 Export XML, Copy JSON and Download.

When an object you picked needs another one (for example a parent object), the bottom bar says how many dependencies are missing, and Auto-Add adds them.

Permission Builder Graph tab showing Account and Contact with their related objects

1 Depth buttons: Direct, Extended, Full Schema. 2 Graph and Table views. 3 The objects you added (Account). 4 Export PNG.

Create New creates the permission set in the connected org. Download saves the payload as a JSON file and Copy JSON copies it; Export XML gives a .permissionset-meta.xml file. Save Template keeps your choices to reuse later.

Permission Builder covers object and field permissions. It does not set system permissions, tab settings or Apex class access, and it does not assign the permission set to users.

Side-by-Side Comparison

PS Comparison (its own entry in the sidebar, called Compare from the release after 1.1.13) lets you select any two permission sets in the connected org and see their object and field permission differences in a color-coded view. Use it to:

  • Find gaps between similar permission sets
  • Check changes before deployment
  • See which object and field access each set grants

Assigning permission sets

Permission Builder does not assign permission sets. To assign or remove a permission set for many users at once, use the bulk operations in Access Editor: search and pick users, then assign or remove the set. Each assignment is recorded in the transaction log.

Best Practices

  1. Start minimal — create permission sets with the least access needed
  2. Use consistent naming — follow a naming convention like PS_[Team]_[Access]
  3. Review quarterly — use PS Comparison (Compare) to spot drift between similar permission sets
  4. Test in sandbox — test permission changes in a sandbox before production