Consider a technology company that uses Salesforce to manage its sales pipeline.<\/p>\n\n\n\n
To maintain the integrity of completed deals, the Salesforce Administrator has implemented a Validation Rule that prevents users from editing a Closed Won Opportunity.<\/p>\n\n\n\n
Business Rule<\/strong><\/p>\n\n\n\n Once an Opportunity reaches Closed Won, users should not be able to modify important business fields such as:<\/p>\n\n\n\n This rule works perfectly for sales users.<\/p>\n\n\n\n However, the company introduces a Record-Triggered Flow that automatically updates renewal information after the Opportunity is won.<\/p>\n\n\n\n The Flow needs to:<\/p>\n\n\n\n When tested, the Flow fails because the Validation Rule blocks the update.<\/p>\n\n\n\n The business now faces three options:<\/p>\n\n\n\n The third option provides the best balance between automation and governance.<\/p>\n\n\n\n Instead of disabling the Validation Rule, we’ll allow only trusted automation users to bypass it using Custom Permissions.<\/p>\n\n\n\n Step 1: Create a Custom Permission<\/strong><\/p>\n\n\n\n Navigate to:<\/p>\n\n\n\n Setup \u2192 Custom Permissions<\/strong><\/p>\n\n\n\n Create a new Custom Permission.<\/p>\n\n\n\n Example:<\/strong><\/p>\n\n\n\n Bypass_Opportunity_Validation<\/p>\n\n\n\n Step 2: Create a Permission Set<\/strong><\/p>\n\n\n\n Navigate to:<\/p>\n\n\n\n Setup \u2192 Permission Sets<\/strong><\/p>\n\n\n\n Create a new Permission Set.<\/p>\n\n\n\n Example<\/strong>:\u00a0 <\/p>\n\n\n\n Automation User Permissions Important:<\/strong> Do not assign this Permission Set to regular business users.<\/p>\n\n\n\n <\/strong>Step 3: Modify the Validation Rule<\/strong><\/p>\n\n\n\n Suppose your existing Validation Rule prevents users from editing Closed Won Opportunities.<\/p>\n\n\n\n Before<\/strong><\/p>\n\n\n\n This rule blocks everyone.<\/p>\n\n\n\n After<\/strong><\/p>\n\n\n\n Update the Validation Rule to check for the Custom Permission.<\/p>\n\n\n\n Now the Validation Rule behaves intelligently.<\/p>\n\n\n\n Step 4: Configure Your Flow<\/strong><\/p>\n\n\n\n Create a Record-Triggered Flow that performs the required updates.<\/p>\n\n\n\n Since the Flow runs using a user with the Custom Permission, it can successfully update the record without being blocked by the Validation Rule.<\/p>\n\n\n\n Using Custom Permissions to bypass Validation Rules offers several advantages:<\/p>\n\n\n\n Validation Rules and automation should complement each other\u2014not compete.<\/p>\n\n\n\n While Validation Rules protect the quality and consistency of Salesforce data, automated business processes often need the flexibility to update records that users cannot modify.<\/p>\n\n\n\n Using Custom Permissions provides a secure, declarative, and scalable way to selectively bypass Validation Rules without compromising security or maintainability. By granting bypass access only to trusted automation and integration users, organizations can maintain strong data governance while ensuring that Flows and integrations continue to operate reliably and efficiently.<\/p>\n\n\n\n By following the above blog instructions, you will be able to learn \u201cHow to Bypass Validation Rules in Salesforce Flow Using Custom Permissions<\/strong>\u201c. If you still have queries or any related problems, don\u2019t hesitate to contact us at salesforce@greytrix.com<\/a>. More details about our integration product are available on our website<\/a> and Salesforce AppExchange<\/a>. About Us<\/b><\/br>\n Greytrix<\/a> \u2013 a globally recognized and one of the oldest Sage Development Partner and a Salesforce Product development partner offers a wide variety of integration products and services to the end users as well as to the Partners and Sage PSG across the globe. We offer Consultation, Configuration, Training and support services in out-of-the-box functionality as well as customizations to incorporate custom business rules and functionalities that require apex code incorporation into the Salesforce platform. Validation Rules are one of Salesforce’s most powerful declarative features for maintaining data quality. They ensure that users enter complete and accurate information by preventing records from being saved when business rules are violated. However, not every update originates from a user. Modern Salesforce implementations rely heavily on Record-Triggered Flows, Scheduled Flows, Platform Events, and\u2026 Read More »<\/a><\/span><\/p>\n","protected":false},"author":2,"featured_media":0,"comment_status":"closed","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[2],"tags":[1866,3501,62,2342,3502,3494,3498,3504,3508,2646,1381,3497,3506,3496,1402,3493,1711,3490,367,2467,3418,1709,3511,3516,2457,3507,3228,2048,3500,3517,2507,3083,392,1712,2469,3513,2570,397,3514,3505,882,3518,3510,3515,1984,2329,3512,3503,2108,3495,2111,2918,3491,3489,2136,2138,2645,1241,3509,3499,3492],"class_list":["post-13046","post","type-post","status-publish","format-standard","hentry","category-gumu-salesforce","tag-automation","tag-bypass-validation-rules","tag-crm","tag-crm-automation","tag-custom-permissions","tag-custompermissions","tag-declarativedevelopment","tag-flow-automation","tag-flow-best-practices","tag-flowautomation","tag-flowbuilder","tag-lowcode","tag-no-apex","tag-nocode","tag-permission-sets","tag-permissionsets-2","tag-record-triggered-flow","tag-recordtriggeredflow","tag-salesforce","tag-salesforce-admin","tag-salesforce-architecture","tag-salesforce-automation","tag-salesforce-automation-tips","tag-salesforce-automation-user","tag-salesforce-best-practices","tag-salesforce-business-automation","tag-salesforce-configuration","tag-salesforce-crm","tag-salesforce-custom-permissions","tag-salesforce-data-validation","tag-salesforce-declarative-automation","tag-salesforce-developer","tag-salesforce-development","tag-salesforce-flow","tag-salesforce-flow-builder","tag-salesforce-flow-tutorial","tag-salesforce-governance","tag-salesforce-integration","tag-salesforce-integration-user","tag-salesforce-low-code","tag-salesforce-permission-sets","tag-salesforce-productivity","tag-salesforce-record-update","tag-salesforce-record-triggered-automation","tag-salesforce-security","tag-salesforce-security-best-practices","tag-salesforce-tutorial","tag-salesforce-validation-rules","tag-salesforceadmin","tag-salesforcearchitecture","tag-salesforceautomation","tag-salesforcebestpractices","tag-salesforcedeveloper","tag-salesforceflow","tag-salesforceintegration","tag-salesforcesecurity","tag-salesforcetips","tag-screenflow","tag-validation-rule-bypass","tag-validation-rules","tag-validationrules"],"_links":{"self":[{"href":"https:\/\/www.greytrix.com\/blogs\/salesforce\/wp-json\/wp\/v2\/posts\/13046","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/www.greytrix.com\/blogs\/salesforce\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/www.greytrix.com\/blogs\/salesforce\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/www.greytrix.com\/blogs\/salesforce\/wp-json\/wp\/v2\/users\/2"}],"replies":[{"embeddable":true,"href":"https:\/\/www.greytrix.com\/blogs\/salesforce\/wp-json\/wp\/v2\/comments?post=13046"}],"version-history":[{"count":9,"href":"https:\/\/www.greytrix.com\/blogs\/salesforce\/wp-json\/wp\/v2\/posts\/13046\/revisions"}],"predecessor-version":[{"id":13061,"href":"https:\/\/www.greytrix.com\/blogs\/salesforce\/wp-json\/wp\/v2\/posts\/13046\/revisions\/13061"}],"wp:attachment":[{"href":"https:\/\/www.greytrix.com\/blogs\/salesforce\/wp-json\/wp\/v2\/media?parent=13046"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.greytrix.com\/blogs\/salesforce\/wp-json\/wp\/v2\/categories?post=13046"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.greytrix.com\/blogs\/salesforce\/wp-json\/wp\/v2\/tags?post=13046"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}\n
\n
\n
Solution Overview<\/mark><\/strong><\/h2>\n\n\n\n
![\"Create](\"https:\/\/www.greytrix.com\/blogs\/salesforce\/wp-content\/uploads\/2026\/07\/imageblog.1.png\")
<\/a><\/center>
Add the newly created Custom Permission to the Permission Set.
Assign this Permission Set only to trusted users such as:<\/p>\n\n\n\n\n
<\/a><\/figure><\/center>\n\n\n\nAND(
ISPICKVAL(StageName,\"Closed Won\"),
ISCHANGED(Amount)
)<\/code><\/pre>\n\n\n\nAND(
ISPICKVAL(StageName,\"Closed Won\"),
ISCHANGED(Amount),
NOT($Permission.Bypass_Opportunity_Validation)
)<\/code><\/pre>\n\n\n\n\n
<\/a><\/center><\/a><\/center><\/a><\/center><\/a><\/center>Benefits of This Approach<\/strong><\/mark><\/h2>\n\n\n\n
\n
Conclusion<\/strong><\/mark><\/h2>\n\n\n\n
We hope you may find this blog resourceful and helpful. However, if you still have concerns and need more help, please contact us at salesforce@greytrix.com<\/a>.<\/p>\n\n\n\n
Greytrix has some unique solutions for Cloud CRM such as Salesforce Sage integration<\/a> for Sage X3<\/a>, Sage 100<\/a> and Sage 300 (Sage Accpac)<\/a>. We also offer best-in-class Cloud CRM Salesforce customization and development services<\/a> along with services such as Salesforce Data Migration<\/a>, Integrated App development<\/a>, Custom App development and Technical Support business partners and end users. Salesforce Cloud CRM integration offered by Greytrix works with Lightning web components and supports standard opportunity workflow. Greytrix GUMU™ integration for Sage ERP \u2013 Salesforce is a 5-star rated app listed on Salesforce AppExchange<\/a>.
The GUMU™ Cloud framework by Greytrix forms the backbone of cloud integrations that are managed in real-time for processing and execution of application programs at the click of a button.
For more information on our Salesforce products and services, contact us at salesforce@greytrix.com<\/a>. We will be glad to assist you.<\/p>\n","protected":false},"excerpt":{"rendered":"