Skip to main content

Moving Salesforce permissions from profiles to permission sets, safely

Most mature Salesforce orgs carry a few dozen profiles that started as clones of Standard User and drifted. Each one mixes object access, field access, system permissions, page layouts and login settings, and nobody is quite sure which differences are deliberate. Moving permissions out of profiles and into permission sets fixes that, but it is also one of the easiest ways to lock users out on a Monday morning or, worse, quietly hand someone more access than before. This post covers why to make the move, how permission set groups and muting fit in, a migration plan, and how to prove that effective access did what you intended.

Why move away from profile permissions

A profile is one-per-user. That forces every combination of job duties into its own profile, which is how orgs end up with "Sales User - EMEA - Can Export - Temp". Permission sets are additive and many-per-user, so access can be built from small, named pieces that match real duties.

The security argument is least privilege. When permissions live in a profile, removing one capability from one person means cloning a profile. When they live in permission sets, you unassign a set. Access reviews also get easier: "who holds the Export Reports set" is a question with a short answer.

Salesforce has recommended a permission-set-led model for several years, with the profile kept for the settings that still belong there, such as login hours, login IP ranges, default apps and record types. Salesforce previously announced an end of life for permissions on profiles and later stepped back from enforcing a fixed date, so plan this work on its security merits and check the current release notes for timing rather than working to a deadline.

Permission set groups and muting

A permission set group bundles several permission sets into one assignable unit, usually one per job function: "Service Agent", "Sales Manager", "Integration - ERP". A user in the group gets the union of every set in it.

Two details matter for security.

The union can be bigger than it looks. Each permission set in a group can look harmless on its own while the combination is admin-equivalent. A group built from a set with View All Data and another with Manage Users is effectively an administrator, even though neither set is.

Muting removes, but only inside the group. A group can contain one muting permission set, which switches off chosen permissions for members of that group. As Trailhead's unit on muting points out, a user who gets the same permission from their profile, a directly assigned permission set or another group still has it. Muting is a way to reuse a broad set for a narrower role, not a way to take access away from a person.

A migration plan

The safe version of this project is mostly bookkeeping. The risky version is "create the permission sets and swap everyone's profile on Friday".

1. Inventory what each profile actually grants

Retrieve every profile and permission set into source so you can diff them as files, not by clicking through Setup:

sf project retrieve start --metadata Profile PermissionSet PermissionSetGroup --target-org prod

For each custom profile, list its object permissions, field permissions, system permissions, Apex class and Visualforce page access, and tab settings. Most of the work is noticing which differences between two similar profiles are intentional.

2. Design permission sets by duty, not by profile

Group permissions into sets that match tasks people do: "Edit Opportunities", "Export Reports", "Manage Cases". Keep the powerful ones separate and small: Modify All Data, View All Data, Author Apex, Manage Users and API Enabled each deserve their own set with a named owner, so they never arrive bundled with ordinary access.

3. Build groups per job function

Assemble the sets into permission set groups. Use a muting set where a role needs most of a set but not all of it.

4. Shrink the profiles

Move users to a minimal profile that keeps only the settings that still belong on a profile. A profile that grants Modify All Data next to ordinary object access is exactly what this step removes:

<!-- Before: Sales_EMEA.profile-meta.xml -->
<userPermissions>
    <name>ModifyAllData</name>
    <enabled>true</enabled>
</userPermissions>
<objectPermissions>
    <object>Opportunity</object>
    <allowEdit>true</allowEdit>
    <allowRead>true</allowRead>
    <viewAllRecords>true</viewAllRecords>
</objectPermissions>
<!-- After: Edit_Opportunities.permissionset-meta.xml -->
<objectPermissions>
    <object>Opportunity</object>
    <allowCreate>true</allowCreate>
    <allowEdit>true</allowEdit>
    <allowRead>true</allowRead>
    <viewAllRecords>false</viewAllRecords>
</objectPermissions>

Modify All Data does not move into a job-function set at all. If someone needs it, they get the separate, owned set, and the assignment is reviewed.

5. Migrate in waves and verify each one

Move one team at a time, starting with a small group whose work you can watch. After each wave, compare effective access before and after (next section) and fix gaps before moving on.

6. Delete what is left

Retire profiles that no longer have users, and remove permission sets nobody holds. Leftover sets are where ad hoc grants accumulate later.

How to verify effective access

The question that matters is not "what does each profile and set say" but "what can each user do now, and is it the same as before, minus what we meant to remove?"

In Setup, the user record's access summary and the permission set group summary both show resolved permissions, including the effect of muting. That is fine for spot checks. For a migration you want the whole org, before and after, as data you can diff.

Vulkro for Salesforce resolves profile, permission sets and groups per active user against a live org:

vulkro-sf org effective-perms --target-org prod --format json > before.json
# ... migrate a wave ...
vulkro-sf org effective-perms --target-org prod --format json > after.json

org effective-perms reports SF-PERM-ASSIGN-001 for any set granting Modify All Data, View All Data, Author Apex or Manage Users that an active user holds, listing every holder. A diff of the two files shows whether a wave added a holder you did not expect. org psg-composition reports SF-PSG-COMPOSITION-001 for groups whose members each grant the same powerful permission, the union problem described above.

Before anything reaches production, run the change through a review in the pull request:

vulkro-sf review --range origin/main...HEAD --fail-on high

When the change touches metadata, the review reports what it grants and to whom, so a permission set that quietly picked up a dangerous permission is visible to the reviewer. For the admin-equivalent population and MFA, see our least-privilege checklist.

FAQ

Should I still use profiles in Salesforce?

Yes, every user still needs one. The recommended pattern is a minimal profile for settings that only profiles hold (such as login hours, IP ranges and defaults) and permission sets or permission set groups for object, field and system permissions.

Does a muting permission set remove access from a user?

Only for permissions that come from that permission set group. If the user also gets the permission from their profile, a directly assigned permission set or another group, they keep it.

How do I check a user's effective permissions in Salesforce?

Use the user's access summary in Setup for a single user. For an org-wide before-and-after comparison, export resolved permissions for all active users and diff them, so every change in access is visible and deliberate.

Review access across a whole org with Vulkro for Salesforce, or Start a 14-day trial. Related: the sharing rule that shares too much.