---
schema_version: "1"
id: d7bae018d536df2f2a8014aeacdca612d0031c55f0781bc6c13b7542e12e6a3c
title: Modify Process Automation Settings
collection: admin
version: current
locale: en-us
portal_url: https://docs.salesforce.com/admin/current/en-us/platform/264-0-0/wf_approval_settings.md
canonical_url: https://help.salesforce.com/s/articleView?id=platform.wf_approval_settings.htm&release=264.0.0&type=5
source_site: help.salesforce.com
content_type: documentation
content_hash: 87a8b707de4a098e811e38b45dcc70d858e14bcb83400481997f8568f9043b21
description: Enable or disable features related to flows, processes, workflow rules, and classic approval processes.
products:
  - Flow Builder
  - Salesforce Platform
release: "264"
---
# Modify Process Automation Settings

Enable or disable features related to flows, processes, workflow rules, and classic approval processes.

### Required Editions

<table class="slds-table slds-table_bordered slds-max-medium-table_stacked slds-m-bottom_small edition">
        <colgroup>
          <col>
        </colgroup>
        <tbody>
          <tr class="">
            <td class="slds-cell-wrap" style="vertical-align:top;">Available in: Lightning Experience and Salesforce Classic</td>

          </tr>
          <tr class="">
            <td class="slds-cell-wrap" style="vertical-align:top;">
              <p>Processes and flows are available in: <span><strong>Essentials</strong>,
                  <strong>Professional</strong>, <strong>Enterprise</strong>, <strong>Performance</strong>, <strong>Unlimited</strong>,
                  and <strong>Developer</strong> Editions</span></p>
              <p style="margin-bottom:0;">Approvals and Workflow are available in <span><strong>Enterprise</strong>,
                  <strong>Performance</strong>, <strong>Unlimited</strong>, and <strong>Developer</strong>
                  Editions</span></p>
            </td>

          </tr>
        </tbody>
      </table> <table class="slds-table slds-table_bordered slds-max-medium-table_stacked slds-m-bottom_small ">
        <colgroup>
          <col style="width:50%">
          <col style="width:50%">
        </colgroup>
        <thead class="slds-text-title_caps ">
          <tr class="">
            <th scope="colgroup" class="slds-cell-wrap" colspan="2" style="text-align:center;vertical-align:top;" id="d170521e94">User Permissions
              Needed</th>
          </tr>
        </thead>
        <tbody>
          <tr class="">
            <td data-label="User Permissions Needed" class="slds-cell-wrap" style="vertical-align:top;" headers="d170521e94 ">To edit process automation settings:</td>

            <td class="slds-cell-wrap" style="vertical-align:top;" headers="d170521e94 ">Customize Application</td>

          </tr>
          <tr class="">
            <td data-label="User Permissions Needed" class="slds-cell-wrap" style="vertical-align:top;" headers="d170521e94 ">To create, update, and delete flow list views:</td>

            <td class="slds-cell-wrap" style="vertical-align:top;" headers="d170521e94 ">Manage Flow</td>

          </tr>
        </tbody>
      </table>

- [Identify Your Salesforce Org’s Default Workflow User](https://help.salesforce.com/s/articleView?id=platform.workflow_defaultuser.htm&release=264.0.0&type=5 "Select a Default Workflow User that you want Salesforce to display with a workflow rule when the user that triggered the rule isn’t active.")
- [Override the Sender for Email Approval Notifications from Classic Approval Processes](https://help.salesforce.com/s/articleView?id=platform.approvals_email_sender.htm&release=264.0.0&type=5 "By default, the sender for email approval notifications is the user who submitted the record for approval using a classic approval process. You can override the sender with an organization-wide address, like approval@acmewireless.com.")
- [Let Users Respond to Approval Requests via Email](https://help.salesforce.com/s/articleView?id=platform.approvals_email.htm&release=264.0.0&type=5 "After you’ve reviewed the considerations and prepared the right template, flip the switch that lets users respond to approval requests directly from their email.")
- [Let Users Pause Flow Interviews](https://help.salesforce.com/s/articleView?id=platform.flow_pause.htm&release=264.0.0&type=5 "When users can’t finish a flow interview, give them the option to pause it for later by customizing your org’s process automation settings. For example, a customer service representative can pause an interview when the customer doesn’t have all the necessary information.")
- [Let Users Pause Flow Interviews](https://help.salesforce.com/s/articleView?id=platform.flow_pause.htm&release=264.0.0&type=5 "When users can’t finish a flow interview, give them the option to pause it for later by customizing your org’s process automation settings. For example, a customer service representative can pause an interview when the customer doesn’t have all the necessary information.")
- [Enable Lightning Runtime for Custom Buttons and Links](https://help.salesforce.com/s/articleView?id=platform.flow_distribute_internal_lexruntime.htm&release=264.0.0&type=5 "Are you distributing a flow via a URL? That includes things like direct URLs, custom buttons, and links in Setup. You can flip one switch to upgrade all those flows to Lightning runtime.")
- [Control What Happens When a Flow Tries to Set Values for Read-Only Fields](https://help.salesforce.com/s/articleView?id=platform.flow_considerations_readonlyfields_behavior.htm&release=264.0.0&type=5 "When a flow tries to perform an action, such as create or update records, it uses a flow request to set values for specific fields. But what happens if the running user doesn’t have edit access to all those fields? When you use a record variable or record collection variable in Create Records and Update Records elements, that’s up to you. To control the behavior, select or deselect the Filter inaccessible fields from flow requests preference.")
- [Select Flow and Process Error Email Recipients](https://help.salesforce.com/s/articleView?id=platform.flow_troubleshoot_error_email.htm&release=264.0.0&type=5 "When a process or flow interview fails, a detailed email is sent to the admin who last modified the process or flow. However, sometimes the admin isn’t the best person to act on the details of what ran and what went wrong. In that case, you can send error emails to the Apex exception email recipients.")
- [Deploy Processes and Flows as Active](https://help.salesforce.com/s/articleView?id=platform.flow_distribute_deploy_active.htm&release=264.0.0&type=5 "By default, processes and flows that are active in a sandbox or non-production org are deployed to a production org as inactive. After deployment, manually reactivate the new versions. In production orgs, you can enable the setting to deploy a new active version of a process or flow via change sets or Metadata API. If you use a continuous integration and continuous delivery model to deploy metadata changes, enable the option to deploy processes and flows as active.")