Manage Salesforce Profile and Permission Set Access
Jetstream makes it easy to view and modify object, field, tab, system and custom permissions across many profiles and permission sets at the same time.
To get started, choose at least one profile and/or permission set, then select the objects whose permissions you want to manage. Objects are optional: system permissions and custom permissions do not depend on them, so you can continue without any objects selected to manage just those.
Permission Analysis is the read-only companion to this page. It scans the profiles and permission sets you pick for over-access, dangerous system permissions, field security that is not backed by object access, and unused permission sets, then lets you export any of it to Excel, CSV or JSON. Jump straight there with the Open in Permission Analysis button on this screen.
Creating and cloning permission sets
Click New Permission Set to create an empty permission set, or Clone to create one that starts with every permission from an existing profile or permission set. If exactly one profile or permission set is selected when you click Clone, it is chosen as the starting point.
Cloning copies object permissions, field permissions, tab settings, system permissions, and access to Apex classes, Visualforce pages, apps, connected apps and custom permissions. The license and session activation setting default to match what you are cloning, and you can change them before you save. Cloning a managed permission set gives you an editable copy of it.
When it finishes, the new permission set is selected so you can start editing its permissions straight away.
Profiles can have permissions that permission sets cannot, and some permissions are only allowed with a specific license. Anything Salesforce does not allow is skipped. Jetstream lists each one with the reason Salesforce gave, so you can see exactly what was not copied. Profile-only settings like page layout assignments, record type defaults, login hours and login IP ranges are not part of a permission set, so they are never copied.
Comparing against managed package permission sets
Permission sets installed from a managed package, and the standard permission sets Salesforce provides (such as Sales Cloud User), are hidden by default because Salesforce does not allow their permissions to be changed. Turn on Show managed permission sets above the Permission Sets list to include them in your selection.
These appear with a lock icon and the name of the package they came from, or Salesforce standard. You can view and export everything they grant and compare it side by side with your own permission sets, but every checkbox in their column is read-only, and they are never included when you save.
A permission set in your own org's namespace is not treated as managed - you publish that package, so Jetstream leaves those fully editable.
What can be managed
The editor has one tab per kind of permission. Every tab works the same way: one row per item, one group of checkboxes per selected profile or permission set.
- Object Permissions - Create, Read, Edit, Delete, View All, Modify All and View All Fields for each selected object.
- Tab Visibility - Whether the object's tab is available and visible.
- Field Permissions - Read and Edit access for every permissionable field on the selected objects, grouped by object.
- System Permissions - Every user permission Salesforce allows to be set on a permission set in your org, such as API Enabled or Modify All Data. Dependencies between system permissions are applied automatically.
- Custom Permissions - Which profiles and permission sets are granted each custom permission in the org, including custom permissions from installed packages.
Custom permissions
Custom permissions are how Salesforce lets you grant access to things it has no built-in permission for. Once a
profile or permission set has a custom permission, you can check for it with $Permission.Name in formulas, validation
rules and flows, or with FeatureManagement.checkPermission('Name') in Apex.
The Custom Permissions tab lists every custom permission in the org, with its API name and description. Check a box to grant the custom permission to that profile or permission set, uncheck it to revoke it, then save.
Use New Custom Permission on that tab to create one without leaving Jetstream. It is created through a metadata deployment, which takes a few seconds, and then appears in the table ready to be granted.
Creating a custom permission requires the Manage Custom Permissions or Customize Application user permission. Custom permissions cannot be deleted or renamed from Jetstream because other metadata (formulas, flows, Apex) may reference them; use Setup for that.
To see which users end up with a custom permission, click a profile or permission set name in the column header to see the users assigned to it.
Adjusting Permissions
By default, field permissions will be shown. You can toggle the Object Permissions by clicking on the Object Permissions tab.
As you make changes, a number will appear in the tab bar indicator the number of modified items.
Changing permissions for an individual item
Click any individual checkbox to toggle the permission setting for the specific object or field.
Some permissions are dependent on other permissions, so as you make changes other checkboxes may get automatically checked or unchecked.
Changing permissions for all fields for one Profile or Permission Set
To apply a change to all visible fields for a specific profile or permission set, click the checkboxes icon or the unchecked outline icon.
You can reset all changes for a profile the same way.
If you apply a filter to limit which fields are shown, only the non-filtered fields will be modified when selecting or unselecting all.
Changing permissions for all Profile and Permission Sets for one field
Click the Edit Row link next to the field to apply a specific permission to all profiles and permission sets for that row.
Click the Edit All link to apply a change to all profiles and permission sets for the non-filtered fields.
See also
- Permission Analysis — read-only audit of object, field, tab and system permissions with automatic issue detection and export.
- Data Analysis (Field Usage) — find unused fields and measure data coverage across your objects.