Salesforce Dictionary - Free Salesforce GlossarySalesforce Dictionary
Full Process Automation Settings entry
How-to guide

How to configure Process Automation Settings

Configure the org-wide automation options once, deliberately, ideally during initial org setup. You need the Customize Application permission. The page applies to Flow and to the retired Workflow Rules and Process Builder, so changes here affect every automation in the org.

By Dipojjal Chakrabarti · Founder & Editor, Salesforce DictionaryLast updated Jun 16, 2026

Configure the org-wide automation options once, deliberately, ideally during initial org setup. You need the Customize Application permission. The page applies to Flow and to the retired Workflow Rules and Process Builder, so changes here affect every automation in the org.

  1. Open the settings page

    From Setup, type Process Automation Settings into the Quick Find box and select it. The full page of org-wide options opens.

  2. Set the Default Workflow User

    Use the lookup to pick a permanently active service account. This is required if you use time-dependent workflow actions, and it backstops attribution when triggering users go inactive.

  3. Route error emails

    Set Send Process or Flow Error Email To. Choose Apex Exception Email Recipients for a monitored team list, instead of the lone user who last edited the automation.

  4. Decide on pausing

    Enable Let Users Pause Flows if any screen flow uses a Pause element. Leave it off otherwise. Then save the page.

Default Workflow Userremember

Lookup naming the fallback identity shown when a triggering user is inactive; required for time-dependent actions and used for pending-action alerts.

Send Process or Flow Error Email Toremember

Picks the error-email audience: User Who Last Modified the Process or Flow (default), or Apex Exception Email Recipients (a curated list).

Let Users Pause Flowsremember

Org-wide checkbox that enables the Pause element in screen flows so a running interview can stop and resume later.

Gotchas
  • Pointing the Default Workflow User at a real employee breaks audit trails and pending actions the moment that person is deactivated.
  • Leaving error emails on the last-modified user means failures can route to someone on leave or no longer at the company.
  • A Pause element does nothing if Let Users Pause Flows is unchecked, which sends builders chasing a non-existent flow bug.

See the full Process Automation Settings entry

Process Automation Settings includes the definition, worked example, deep dive, related terms, and a quiz.