You are here:
Process Automation Settings
Salesforce provides various settings for platform automation to help customize and streamline business processes.
Required Editions
| View supported editions. |
| User Permissions Needed | |
|---|---|
| To edit process automation settings: | Customize Application |
Access the settings dialog from Setup by entering Process Automation Settings in the Quick Find box, then selecting Process Automation Settings.
Process Automation provides these settings:
| Setting Label | Type | Description |
|---|---|---|
| Default Workflow User | Text | The name of the default workflow user, which is required for scheduled paths in record-triggered flows and time-dependent actions in workflow rules. If the user who triggered the automation is no longer active, the specified default workflow user is associated with the actions that the automation runs. The default workflow user always runs schedule-triggered flows. |
| Automated Process User Email Address | Text | The No-Reply email address for the Salesforce admin profile that's used to send emails from automated processes. All Salesforce Flow automations use the email address to send emails for actions and errors. Orchestrations also use the email address to send orchestration work item notifications. Flow Approval Processes and Classic Approval Processes also use the email address to send approval work item notifications. By default, no email address is set for the Automated Process User. See: Send Email Action |
| Email Approval Sender | Picklist | For Classic Approval Processes, the organization-wide email address to use as the sender for approval emails. By default, the email approval sender is the approval submitter. See Set Up an Org-Wide Email Address for Flow Approval Processes |
| Enable Email approval response | Checkbox | For Flow Approval Processes and Classic Approval Processes, indicates whether approvers and their delegates can reply to email approval work item notifications to complete approval work items. Approvers reply with APPROVE or REJECT on the first line and add comments on the second line. For flow approval processes, this setting has no effect if the Send Approval Work Item Assignment Emails to Approvers in Approval Settings is set to Don't Send. This setting has no effect for a specific flow approval process if the Don’t Send approver notifications setting is selected. For orchestrations, this setting has no effect if the Stop Sending Orchestration Work Item Email Notifications setting is selected. When you select this setting, you agree to allow Salesforce to process replies and update approval requests and objects on behalf of your users and credentialed site visitors. See Control Email Completion of Flow Approval Processes Approval Work Items |
| Let users pause flows | Checkbox | When selected, users can pause screen flows to wait for more information. A pause button appears on each screen except those screens where you hide it in the screen footer. |
| Let users resume shared flow interviews | Checkbox | When selected, users with direct edit access or edit access via the role hierarchy can resume shared flow interviews. When deselected, only the interview owner or a flow admin with the Manage Flow permission and view access can resume them. |
| Enable Lightning runtime for flows | Checkbox | When selected, flows launched from a URL or from Setup use the Lightning runtime experience instead of the classic runtime experience. Only Lightning runtime supports two-column flow screens, custom screen components, and local actions. |
| Require the Manage Flow permission to view all Automation Home charts | Checkbox | This setting has no affect because the page it controlled access to no longer exists. |
| In Lightning Experience, use the enhanced Flows page and separate Paused and Scheduled Automations page | Checkbox | When selected, the Flows node in Setup separates Flow Definitions from Paused and Failed Flow Interviews. When selected, Paused and Failed Flow Interviews appear in their own Setup node. When deselected, both appear together in the Flows node. This setting affects only Lightning Experience and has no effect in Salesforce Classic. |
| Filter inaccessible fields from flow requests | Checkbox | When selected, flows filter out fields that the running user can’t edit from Create Records and Update Records requests. Also, inaccessible fields are skipped and the operation partially succeeds without notification. When deselected, the operation fails if the running user lacks edit access to any field, triggering the associated fault path or sending an error email. This setting affects flows in API version 51.0 or earlier. See Control What Happens When a Flow Tries to Set Values for Read-Only Fields |
| Enable record locking and unlocking in Apex | Checkbox | When selected, Apex code can set and remove approval process locks for both Classic Approval Processes and Flow Approval Processes. When deselected, Apex can't modify lock or unlock status for approval process records. |
| Let admins debug flows as other users | Checkbox | When selected, users with the Manage Flow and View All Data permissions can select the running user when debugging a flow. This setting is available only in sandbox environments. When debugging as another user:
See Test or Troubleshoot Flows With the Flow Builder Debugger |
| Send Process or Flow Error Email to | Picklist | The recipient for error emails when a process or flow interview fails. These emails include details about what ran, what failed, and the data involved, including user-entered data.
|
| Enable Reactive Components for Specific Flow Versions | Checkbox | When selected, screen flow components running API Version 57 and 58 can react to each other in real time. When selected, supported components on the same screen can update their values or visibility based on changes in other components. Not all screen flow components support reactivity. This setting has no effect on flows running in API version 59 or later, where supported components are always reactive. |
| Send an email each time automation updates the same record | Checkbox | When selected, sends an email notification when a process, workflow rule, or Apex trigger creates or updates the same record that triggered the automation. When deselected, Salesforce doesn’t send an email notification for automated updates to the triggering record. |
| Stop Sending Orchestration Work Item Email Notifications | Checkbox | When selected, stops the sending of email notifications to an assigned user, group, or queue when an orchestration work item or an approval work item is created or reassigned. Use this preference to call flows from your orchestration that send a different notification type. With this setting selected, the Enable Email approval response setting has no effect for flow approval processes or orchestrations. See Disable All Email Notifications for Work Item Assignments |
| Send orchestration work item queue emails only to queue members | Checkbox | When selected, sends orchestration work item queue emails to only queue members. If deselected, also sends queue emails to users in higher roles within the role hierarchy. For flow approval processes, this setting has no effect if the Send Approval Work Item Assignment Emails to Approvers in Approval Settings is set to Don't Send. This setting has no effect for a specific flow approval process if the Don’t send approver notifications setting is selected. For orchestrations, this setting has no effect if the Stop Sending Orchestration Work Item Email Notifications setting is selected. See Control Orchestration Work Item Email Notifications for Queue Members |
| Inherit orchestration run sharing rules to control orchestration run log record access | Checkbox | When selected, orchestration run log record access is inherited from the sharing rules of related orchestration run records. When deselected, users need Manage Flow or View All Data permission to access orchestration run log records. |
| Deploy processes and flows as active | Checkbox | By default, active processes and flows deployed via change sets or Metadata API are deployed as inactive and require an admin to activate them. When selected, active processes and flows are deployed as active, as long as some percentage of active processes and autolaunched flows have test coverage. This setting only appears in Production orgs. |
| Enable the Automation App | Checkbox | When selected, users with the necessary permissions can search for, filter, sort, and manage flows in the Automation app. See Automation App |
