What are Salesforce Custom Permissions?<\/h2>\n\n\n\n
A custom permission is a named permission that you create in Setup. On its own, it does nothing. It only becomes useful when something checks it, such as a validation rule, a flow, a formula or Apex code. You give the permission to users through permission sets or permission set groups.<\/p>\n\n\n\n
Think of a school staff room key. The key itself does not open anything until a lock checks for it. The principal decides which teachers get a key. Salesforce Custom Permissions are those keys, and your rules and flows are the locks.<\/p>\n\n\n\n
Why Salesforce Custom Permissions Matter<\/h2>\n\n\n\n
Many orgs check profile names inside rules, such as “Profile.Name = ‘Sales Manager'”. This breaks when someone renames a profile or creates a new one. Salesforce Custom Permissions fix that problem. Here is how they help Bright Path Tutors.<\/p>\n\n\n\n
- \n
- First, only finance users may change a course fee after the course starts.<\/li>\n\n
- Also, only senior trainers may mark a course as “Featured” on the website.<\/li>\n\n
- Next, a support lead can bypass a validation rule during data clean-up.<\/li>\n\n
- A new screen flow button should appear only for pilot users.<\/li>\n\n
- Finally, admins want one place to see who has each special ability.<\/li>\n<\/ul>\n\n\n\n
So custom permissions make access rules clear, flexible and easy to audit.<\/p>\n\n\n\n
How Salesforce Custom Permissions Work<\/h2>\n\n\n\n
Salesforce Custom Permissions follow a simple pattern. First, you create the custom permission in Setup. Next, you add it to a permission set. Then you assign that permission set to users. After that, a validation rule, flow or formula checks the permission with the $Permission global variable. Finally, Salesforce allows or blocks the action based on the result.<\/p>\n\n\n\n
![\"Salesforce](\"https:\/\/swapnilzambare.com\/blog\/wp-content\/uploads\/2026\/10\/salesforce-custom-permissions-guide-diagram-1-1024x640.png\")
How a custom permission controls a validation rule.<\/figcaption><\/figure>\n\n\n\n The $Permission Variable<\/h3>\n\n\n\n
Formulas, validation rules and flows read custom permissions with $Permission. For example, $Permission.Edit_Started_Course_Fee returns true when the user has that permission. It returns false when they do not.<\/p>\n\n\n\n
Permission Sets and Groups<\/h3>\n\n\n\n
You never assign a custom permission directly to a user. Instead, you add it to a permission set or a permission set group. This keeps all access in the same model you already use.<\/p>\n\n\n\n
Required Custom Permissions<\/h3>\n\n\n\n
A custom permission can require another custom permission. For example, “Approve Refunds” can require “View Refunds”. Salesforce then makes sure the second one is also enabled wherever you enable the first.<\/p>\n\n\n\n
Custom Permissions vs Profile Checks<\/h2>\n\n\n\n
The table below compares custom permissions with checking profile names in rules.<\/p>\n\n\n\n
Feature<\/th> Profile name check<\/th> Custom permission<\/th><\/tr><\/thead> Survives profile rename<\/td> No, the rule breaks<\/td> Yes<\/td><\/tr> Works for many profiles<\/td> Needs long OR lists<\/td> One check covers all<\/td><\/tr> Grant to one extra user<\/td> Change their profile<\/td> Assign a permission set<\/td><\/tr> Easy to audit<\/td> Hard, spread across rules<\/td> Yes, in permission sets<\/td><\/tr> Fits the permission set model<\/td> No<\/td> Yes<\/td><\/tr><\/tbody><\/table><\/figure>\n\n\n\n When to use which is simple. Avoid profile name checks in new work. Use a custom permission whenever a rule or feature should apply to a specific group of users.<\/p>\n\n\n\n
![\"Salesforce](\"https:\/\/swapnilzambare.com\/blog\/wp-content\/uploads\/2026\/10\/salesforce-custom-permissions-guide-diagram-2-1024x640.png\")
Profile name check vs custom permission.<\/figcaption><\/figure>\n\n\n\n How to Use Salesforce Custom Permissions Step by Step<\/h2>\n\n\n\n
Let’s use Salesforce Custom Permissions at Bright Path Tutors. Once a course has started, only finance users should be able to change its fee.<\/p>\n\n\n\n
Step 1: Create the Custom Permission<\/h3>\n\n\n\n
- \n
- Go to Setup and type “Custom Permissions” in Quick Find.<\/li>\n\n
- Click New.<\/li>\n\n
- Enter the values from the table below.<\/li>\n\n
- Then click Save.<\/li>\n<\/ol>\n\n\n\n
The table below shows the values for this permission.<\/p>\n\n\n\n
Field<\/th> Value<\/th><\/tr><\/thead> Label<\/td> Edit Started Course Fee<\/td><\/tr> Name<\/td> Edit_Started_Course_Fee<\/td><\/tr> Description<\/td> Lets finance change the fee after a course starts<\/td><\/tr><\/tbody><\/table><\/figure>\n\n\n\n Step 2: Add It to a Permission Set<\/h3>\n\n\n\n
- \n
- Open the “Finance Team” permission set.<\/li>\n\n
- Click Custom Permissions, then Edit.<\/li>\n\n
- Next, move Edit Started Course Fee to Enabled Custom Permissions.<\/li>\n\n
- Then click Save and assign the permission set to Meera Iyer in finance.<\/li>\n<\/ol>\n\n\n\n
Step 3: Check It in a Validation Rule<\/h3>\n\n\n\n
- \n
- Go to Object Manager > Course > Validation Rules > New.<\/li>\n\n
- Name the rule “Fee_Locked_After_Start”.<\/li>\n\n
- Paste the formula below and set an error message.<\/li>\n<\/ol>\n\n\n\n
AND(\n ISCHANGED(Fee__c),\n Start_Date__c <= TODAY(),\n NOT($Permission.Edit_Started_Course_Fee)\n)<\/code><\/pre>\n\n\n\nThis rule fires when someone changes the fee on a course that has started. However, it skips users who have the custom permission. Use the error message “Only finance can change the fee after a course starts.”<\/p>\n\n\n\n
Step 4: Check It in a Flow<\/h3>\n\n\n\n
You can also use Salesforce Custom Permissions in Flow. In a decision element, add a condition with the resource $Permission.Edit_Started_Course_Fee equals True. For screen flows, you can also use it in component visibility, so only permitted users see certain fields.<\/p>\n\n\n\n
Step 5: Test It<\/h3>\n\n\n\n
- \n
- First, log in as Asha Mehta, a sales rep, and try to change the fee on a started course.<\/li>\n\n
- Confirm the error message appears.<\/li>\n\n
- Next, log in as Meera and make the same change.<\/li>\n\n
- Then confirm the save works.<\/li>\n<\/ol>\n\n\n\n
Bypass Permissions for Data Loads<\/h2>\n\n\n\n
A common use of custom permissions is a bypass switch. For example, create “Bypass Course Validations” and check it in every Course validation rule. Then assign it only to the integration user or to an admin during a data migration.<\/p>\n\n\n\n
This keeps rules strict for everyone else. Also, remove the permission set after the load, so the bypass does not stay open by mistake.<\/p>\n\n\n\n
Finding Who Has a Custom Permission<\/h2>\n\n\n\n
Admins often need to answer “Who can do this?” Open the custom permission in Setup and check which permission sets include it. Then view the assignments of each permission set. Developers can also check permissions in Apex with the FeatureManagement.checkPermission method, which we will cover in the developer series.<\/p>\n\n\n\n
Common Mistakes with Salesforce Custom Permissions<\/h2>\n\n\n\n
- \n
- Creating the permission but never adding it to a permission set.<\/li>\n\n
- Checking profile names in new rules instead of using a custom permission.<\/li>\n\n
- Leaving bypass permissions assigned after a data load.<\/li>\n\n
- Using vague names, such as “Special Access”, that nobody understands later.<\/li>\n\n
- Forgetting to write a description that explains where the permission is used.<\/li>\n<\/ul>\n\n\n\n
Best Practices for Salesforce Custom Permissions<\/h2>\n\n\n\n
- \n
- Name each permission after the action it allows, such as “Edit Started Course Fee”.<\/li>\n\n
- Write in the description which rules and flows check it.<\/li>\n\n
- Assign through permission sets or groups, never through profiles.<\/li>\n\n
- Use one bypass permission per object for data loads.<\/li>\n\n
- Review assignments every quarter with your security team.<\/li>\n<\/ul>\n\n\n\n
Practice Task<\/h2>\n\n\n\n
Create a custom permission called “Mark Course Featured”. Then build a validation rule that blocks changes to an Is Featured checkbox unless the user has it. Hint: use ISCHANGED with the checkbox field and NOT with $Permission.<\/p>\n\n\n\n
Most Asked Interview Questions on Salesforce Custom Permissions<\/h2>\n\n\n\n
Questions on Salesforce Custom Permissions are common, because they show you know modern access design. Here are the ones asked most.<\/p>\n\n\n\n
Basic Questions on Salesforce Custom Permissions<\/h3>\n\n\n\n
Q1. What is a custom permission?<\/strong><\/p>\n\n\n\n
It is a permission you create in Setup to control access to a feature or rule. It works only when something checks it, such as a validation rule or flow.<\/p>\n\n\n\n
Q2. How do you assign a custom permission?<\/strong><\/p>\n\n\n\n
Add it to a permission set or permission set group, then assign that to users. You can also enable it in a profile, but permission sets are the better choice.<\/p>\n\n\n\n
Q3. How do you check a custom permission in a formula?<\/strong><\/p>\n\n\n\n
Use the $Permission global variable, such as $Permission.Edit_Started_Course_Fee. It returns true or false.<\/p>\n\n\n\n
Q4. What is a required custom permission?<\/strong><\/p>\n\n\n\n
It is a custom permission that another custom permission depends on. Salesforce enables the required one wherever you enable the main one.<\/p>\n\n\n\n
Practical Questions on Salesforce Custom Permissions<\/h3>\n\n\n\n
Q5. Why use a custom permission instead of a profile check?<\/strong><\/p>\n\n\n\n
Profile checks break when profiles change and need long lists. A custom permission is one clear check that works across any profile.<\/p>\n\n\n\n
Q6. How do you let an integration user skip validation rules?<\/strong><\/p>\n\n\n\n
Create a bypass custom permission, check it in each rule with NOT($Permission…), and assign it only to the integration user.<\/p>\n\n\n\n
Q7. Can you use custom permissions in Flow?<\/strong><\/p>\n\n\n\n
Yes. Use $Permission in decision conditions, formulas and screen component visibility.<\/p>\n\n\n\n
Q8. How do developers check custom permissions?<\/strong><\/p>\n\n\n\n
In Apex, they use FeatureManagement.checkPermission with the permission’s API name.<\/p>\n\n\n\n
Official Resources<\/h2>\n\n\n\n