---
schema_version: "1"
id: bc8573a5f33e0efb6d9eb0f577f5131cf31505428e1a80dd78ad9a93bccce148
title: Identify Your Salesforce Org’s Default Workflow User
collection: admin
version: current
locale: en-us
portal_url: https://docs.salesforce.com/admin/current/en-us/platform/264-0-0/workflow_defaultuser.md
canonical_url: https://help.salesforce.com/s/articleView?id=platform.workflow_defaultuser.htm&release=264.0.0&type=5
source_site: help.salesforce.com
content_type: documentation
content_hash: aee1af39c276332e3138fc1c52d81d07e54a14470644320df57aa240bdafa52e
description: 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.
products:
  - Flow Builder
  - Salesforce Platform
release: "264"
---
# Identify Your Salesforce Org’s Default Workflow User

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.

### 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;">Available in: <strong>Enterprise</strong>, <strong>Performance</strong>, <strong>Unlimited</strong>, and <strong>Developer</strong> Editions</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="d169172e76">User Permissions
              Needed</th>
          </tr>
        </thead>
        <tbody>
          <tr class="">
            <td data-label="User Permissions Needed" class="slds-cell-wrap" style="vertical-align:top;" headers="d169172e76 ">To edit process automation settings:</td>

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

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

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

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

![Important](https://sf-zdocs-cdn-prod.zoominsoftware.com/tdta-platform-platform_automation-264-0-0-production-enus/60568438-ec7e-4665-acd1-7c80dcbe60d5/images/icon_important.png)

Important Support and updates for Workflow Rules have ended as of December 31, 2025. This means that support won't be provided for any workflow rules and bugs in the Workflow Rules product won't be fixed. See [Workflow Rules & Process Builder End of Support](https://help.salesforce.com/s/articleView?id=001096524&type=1&language=en_US).

After December 31, 2025, existing workflow rules continue to run, and you can activate, deactivate, and edit them; however we recommend using Flow Builder. To migrate existing workflow rules, plan your [switch to Flow Builder](https://help.salesforce.com/s/articleView?id=platform.flow_migrate_to_flow_learning_map.htm&release=264.0.0&type=5 "Flow Builder combines the capabilities of workflow rules and Process Builder in a single point-and-click tool, making it easier to create a triggered process. If you created triggered processes with workflow rules or Process Builder, use the Migrate to Flow tool to move them to Flow Builder. Start by migrating and testing in a sandbox environment before moving your new flows to production.") and use the [Migrate to Flow](https://help.salesforce.com/s/articleView?id=platform.flow_migrate_to_flow.htm&release=264.0.0&type=5 "Use the Migrate to Flow tool to convert your Process Builder processes and workflow rules into Flow Builder, including scheduled actions. The tool also supports partial migration of processes for most actions.") tool. For new automations, create flows in [Flow Builder](https://help.salesforce.com/s/articleView?id=platform.flow.htm&release=264.0.0&type=5 "Automation reduces repetitive work and helps your team complete tasks faster and more accurately. With Flow Builder, you can build simple or complex automations, forms, and guided experiences with no code. You can add forms to Salesforce pages and Experience sites, and launch flows using buttons, record triggers, or schedules.").

If your organization uses time-dependent actions in workflow rules, you must designate a default workflow user. When the user who triggered the rule isn’t active, Salesforce displays the username of the default workflow user in the Created By field for tasks, the Sending User field for email, and the Last Modified By field for field updates. Salesforce doesn’t display this username for outbound messages. If a problem occurs with a pending action, the default workflow user receives an email notification.

When workflow email alerts approach or exceed certain limits, Salesforce sends a warning email to the default workflow user or—if the default workflow user isn't set—to an active Salesforce admin.

1. From Setup, enter Process Automation Settings in the Quick Find box, then select **Process Automation Settings**.
2. For Default Workflow User, select a user.
3. Save your changes.

#### See Also

- [Daily Allocations for Email Alerts](https://help.salesforce.com/s/articleView?id=platform.workflow_limits_email.htm&release=264.0.0&type=5 "The daily allocation for emails sent through email alerts is 1,000 per standard user license per org—except for free Developer Edition and trial orgs, where the daily workflow email allocation is 15. The overall org allocation is 2,000,000. This allocation applies to emails sent through email alerts in workflow rules, approval processes, flows, processes, or REST API. Single emails sent to external email addresses are also limited, and how those limits are enforced depends on when your org was created.")