Skip to content
Tutorials Center
My learning

Topics

Lesson 16 of 36 ยท Security and Access

Profiles, Permission Sets and Permission Set Groups

Learn how profiles and permission sets grant object, field and system permissions, why a minimum-access profile plus permission sets is best practice, and how groups simplify it.

Profiles and permission sets are the tools that grant object permissions, field permissions, system permissions and access to apps, tabs and other features. They decide what a user can do; sharing (next lesson) decides which records they can do it to. Understanding when to use each is one of the most tested and most practical admin topics.

Profiles

Every user has exactly one profile. It is mandatory. A profile contains:

  • Object settings: Read, Create, Edit, Delete, View All, Modify All per object.
  • Field permissions: Read and Edit per field.
  • App and tab visibility: which apps appear and which tabs are Default On, Default Off or Hidden.
  • System permissions: for example Export Reports, Manage Users, Modify All Data, API Enabled, Run Flows.
  • Page layout assignments and record type access.
  • Login hours and login IP ranges.
  • Apex class, Visualforce page and custom permission access.
  • Password policies and session settings (some orgs).

Standard profiles include System Administrator, Standard User, Read Only, Marketing User, Contract Manager and Solution Manager. Standard profiles have limited editing; admins make custom profiles by cloning one. The only profile you must never remove access from is the System Administrator you are using.

The profile problem

If every variation of a job needs a different profile ("Sales Rep", "Sales Rep with Export", "Sales Rep with Contracts"), the number of profiles explodes and nobody knows what differs. Salesforce's answer is permission sets.

Permission sets

A permission set is a bundle of permissions that you assign on top of a profile. A user can have many permission sets. Permission sets can only add access; they cannot take it away (except through muting, in groups). They include object and field permissions, system permissions, app and tab visibility, Apex class access, custom permissions, and more.

Creating one: Setup > Permission Sets > New, choose the license ("None" works for most users with matching license), then configure. Then Manage Assignments > Add Assignment to give it to users.

Typical examples: "Export Reports", "Manage Contracts", "Access Invoice Object", "Run Flows", "View Sensitive Fields".

Profiles versus permission sets

Profile Permission set
How many per user Exactly one Zero, one or many
Can remove access Via permissions not granted No, only adds (muting in groups can reduce)
Controls page layout assignment, login hours/IP Yes No
Controls record type default Yes Record type availability only
Best use Baseline access and settings Job-specific add-ons

Recommended approach: give most users a minimum-access profile (a cloned profile such as "Minimum Access - Salesforce") and grant everything else through permission sets. Salesforce has been moving toward this model and has announced retiring permission management on profiles over time, so new designs should rely on permission sets and permission set groups. Always check the current release notes.

Python Stand-in: effective permissions = profile + permission sets

Press Run (or Ctrl + Enter) to see the result here.

Program input ยท what you'd type while the program runs

Type the answers before you press Run, one per line. Each time the program reads a line (with input()), it gets the next line from this box.

Permission set groups

A permission set group bundles several permission sets into a role-shaped package, for example "Sales Rep" = Sales_Access + Export_Reports + Run_Flows. Assign the group once instead of three sets. Two special features:

  • Muting permission sets: inside a group, a muting set can remove selected permissions that the group's sets would grant, without editing the original sets.
  • Status: a group must be Updated (recalculated) after changes; the page shows Updating then Updated.

Use groups for jobs, sets for building blocks, and the profile for the minimum.

flowchart TD
    P["Minimum access profile"] --> U["User"]
    G["Permission set group: Sales Rep"] --> U
    G --> S1["Set: Sales access"]
    G --> S2["Set: Export reports"]
    G --> S3["Set: Run flows"]

One profile for the baseline, one group for the job, built from reusable permission sets.

Custom permissions

A custom permission is a named switch you create (Setup > Custom Permissions) such as Approve_Discounts. You add it to a permission set and then check it in a validation rule ($Permission.Approve_Discounts), a flow decision ($Permission) or Lightning page visibility. This is the clean way to say "only certain people can do this" without hardcoding profile names.

Object permissions in detail

  • Read: view records (subject to sharing).
  • Create: add records.
  • Edit: change records.
  • Delete: delete records.
  • View All Records / Modify All Records: bypass sharing for that object.
  • Plus the system permission View All Data / Modify All Data for every object.

Note that a user can only be given Edit if they also have Read, and Delete requires Edit. Some objects have extra permissions, for example Convert Leads and Transfer Record on Lead.

Managing assignments

  • Setup > Permission Sets > Manage Assignments lists who has a set.
  • On a User record, the Permission Set Assignments related list shows what they have, including those from groups.
  • Permission Set Licenses may be needed for premium features.
  • Expiration: you can assign a permission set with an expiration date, useful for temporary access.
Python Stand-in: audit who has an export permission

Press Run (or Ctrl + Enter) to see the result here.

Program input ยท what you'd type while the program runs

Type the answers before you press Run, one per line. Each time the program reads a line (with input()), it gets the next line from this box.

Best practices

  • Prefer permission sets and groups; keep profiles minimal.
  • Name by purpose: PS_Invoices_Edit, not PS_Ben.
  • Grant to people through groups; document what each includes.
  • Review assignments regularly and remove old ones.
  • Test in a sandbox with a real test user.
  • Never share the System Administrator profile casually; consider a dedicated admin with minimal daily-use profile.

Check your understanding

Quick check ยท 4 questions

of 4 answered You scored / 4 ยท perfect!

  1. 1. How many profiles can a user have?

    Every user has exactly one profile, but may have many permission sets.
  2. 2. What can a permission set do that a profile cannot?

    Permission sets stack on top of a profile and only add permissions; they are the flexible layer.
  3. 3. What is a permission set group for?

    Groups bundle sets so you assign them together, and muting sets can reduce permissions inside the group.
  4. 4. How do you let only some users approve discounts in a validation rule without hardcoding a profile name?

    Create a custom permission, include it in a permission set and test it with $Permission.Name.

Summary

  • A user has one profile and many permission sets; effective permissions are the union.
  • Use a minimum-access profile plus permission sets, and permission set groups for jobs.
  • Custom permissions give clean switches for formulas, flows and pages.
  • Profiles and permission sets control what users can do; sharing controls which records.

Next: Org-Wide Defaults, Roles and Sharing Rules