Learn how to create a custom permission, clone an existing Record-Triggered Flow, and use the custom permission to bypass that flow for specific users or profiles in Salesforce.
This article explains how to bypass a Record-Triggered Flow for a specific user or profile using a custom permission. This is useful when a system administrator or another user needs an exception to a flow's normal automation. Using Record-Triggered Flow, you'll need to complete four steps:
Custom permissions let you grant users access to custom apps and let you check which users can access certain functionality. You can define access checks that are assigned to users via permission sets or profiles, the same way you assign other user permissions and access settings. You can even use a custom permission to bypass a validation rule or, in this case, a flow, for certain users or profiles.
Now modify the record-triggered flow to fit your business requirement. You'll add a condition to check whether the user has access to the Skip Salesforce Flow custom permission.
Once everything looks correct, click the Activate button.
Written by: Rakesh Gupta, Salesforce MVP. Rakesh is a Senior Solution Architect, Salesforce MVP, and author, passionate about solution design and process automation.
Submissions reflect only the opinions of the user who made the submission available, not the opinions of Salesforce, regardless of whether the user is affiliated with Salesforce, and may contain third-party materials. Salesforce neither controls nor endorses, and is not responsible for, any third-party materials, including their accuracy, validity, timeliness, completeness, reliability, integrity, quality, legality, usefulness, or safety. Community submissions are for general knowledge only and should not be relied upon as answers to specific questions — always contact Salesforce Support for answers to your specific questions. For more community discussion, visit the Trailblazer Community feed.
000393835

We use three kinds of cookies on our websites: required, functional, and advertising. You can choose whether functional and advertising cookies apply. Click on the different cookie categories to find out more about each category and to change the default settings.
Privacy Statement
Required cookies are necessary for basic website functionality. Some examples include: session cookies needed to transmit the website, authentication cookies, and security cookies.
Functional cookies enhance functions, performance, and services on the website. Some examples include: cookies used to analyze site traffic, cookies used for market research, and cookies used to display advertising that is not directed to a particular individual.
Advertising cookies track activity across websites in order to understand a viewer’s interests, and direct them specific marketing. Some examples include: cookies used for remarketing, or interest-based advertising.