Allow a privacy policy to bypass automations, such as triggers and validation rules. If
certain targeted records are subject to value restrictions or used to trigger flows, errors can
occur during policy execution. Bypassing automations reduces these job errors and avoids further
changes caused by record-triggered flows.
Required Editions
| Available in: Developer, Enterprise, Performance, and
Unlimited Editions with the Privacy Center license.
|
There are two ways to bypass automations when you run privacy policies. You can bypass a
specific trigger or validation rule by modifying it to include a bypass condition, and then
assigning a custom permission set to your policy. This approach gives you more control and
reduces the risk of unintended effects in your org.
Alternatively, you can select a bypass setting at the object or policy level. This option
bypasses all triggers and validations for the selected objects on a policy, or for the entire
policy. To avoid skipping critical record actions or allowing unwanted field values, make sure
that you understand the full scope of your policy and the affected automations before using
this approach.
