Flow Runtime Context And Sharing

Flow Runtime Context And Sharing

Activate when designing, reviewing, or auditing a Flow whose run mode determines whether it sees records the running user can't, edits fields the running user can't, or trusts merge fields that resolve from the running user's context. This is the canonical Security skill for Flow — every record-triggered, screen, scheduled, or auto-launched flow that touches sensitive data must justify its run mode against this skill before activation.

Before Starting

Gather this context before working on anything in this domain:

• Flow type and trigger. Record-triggered (before-save / after-save), screen, scheduled, auto-launched, platform-event-triggered, or orchestration. Each has a different default run mode and different override semantics.
• Who is the running user? The interactive user clicking through a screen flow, the user whose DML fired a record-triggered flow, the Automated Process user for scheduled flows, the Apex caller's running user for invocable contexts, or a guest user for Experience Cloud entry points.
• What records does the flow read? Are they within the running user's sharing visibility? Could a low-privileged user trigger this flow and indirectly read records they cannot otherwise see?
• What records does the flow write? Will writes hit objects whose OWD is Private and where sharing rules matter (HR_Case__c, Compensation__c, Patient__c, Opportunity in a sales-team-only org)?
• Sensitivity classification. HR, Comp, Health (HIPAA), Financial (SOX), Personal (GDPR/CCPA), or public-business data. The recommended default flips for each tier.
• API version pinning. Flows pin runtime behavior to their API version. A flow saved at API 51.0 (Spring '21) or earlier may default differently than one saved at API 52.0+.
• Existing runInMode setting. Is it explicitly set in the Flow XML, or is it relying on the default? Implicit defaults are the #1 source of audit findings here.

The most common wrong assumption: "the flow runs as the user who triggered it, so sharing is enforced." It does not. Since Spring '21, record-triggered flows default to System Context Without Sharing, which bypasses sharing rules even when the triggering user couldn't see the record themselves.

Limits and platform constraints:

• Before-save record-triggered flows always run in System Context regardless of the configured run mode (they execute inside the same transaction as the triggering DML, before sharing is evaluated).
• Screen Flows always default to User Context — but a subflow called from a Screen Flow inherits its own setting, not the parent's.
• The runInMode per-element override is supported on Get Records and other DML elements but not on Action elements (Send Email, Apex actions); those run under their own rules.

Core Concepts

There are three central concepts a practitioner must understand: the three run modes themselves, the per-element override, and the Spring '21 default change that silently rewrote the security model for record-triggered flows.

Concept 1 — The Three Run Modes

Salesforce Flow runs at one of three security boundaries, set on the flow's overall properties:

Key points:

• "Without Sharing" + "With Sharing" are both System Context — meaning FLS and CRUD are always bypassed in either mode. The only difference is whether record-level sharing rules apply.
• Only User Context enforces FLS and CRUD. This matters for screen flows that surface fields a low-profile user shouldn't see.
• Validation rules fire in all three modes — but a validation rule that references $User.Profile.Name will resolve against the actual running user, which can yield surprising results in System Context flows.

Defaults by flow type:

• Record-triggered (after-save, since Spring '21): System Context Without Sharing.
• Record-triggered (before-save): Always System Context (the setting is ignored).
• Screen Flow: User Context.
• Auto-launched (scheduled, platform-event, invoked from Apex): System Context Without Sharing (since Spring '21).
• Orchestration (Flow Orchestrator stages): Each stage can be configured; default tracks the underlying flow type.

The principle of least privilege says: start at User Context and escalate only with justification. The Salesforce default does the opposite — it starts at without-sharing and forces you to opt in to safety. This is why every record-triggered flow needs an explicit run-mode review.

Concept 2 — Per-Element Override (runInMode)

The Flow XML supports a runInMode attribute on individual Get Records, Create Records, Update Records, and Delete Records elements. Valid values:

• DefaultMode — inherit the flow's overall run mode.
• SystemModeWithSharing — escalate this element to System Context With Sharing.
• SystemModeWithoutSharing — escalate this element to System Context Without Sharing.

There is no per-element "User Context" override — you can only escalate from User Context, not de-escalate from System Context. This asymmetry is intentional: it lets a User-Context Screen Flow read a single lookup the user can't see (e.g., the assigned Queue's owner) without escalating the entire flow.

Use the per-element override sparingly and document each one. An audit script should flag every element with runInMode != DefaultMode for human review.

In Flow Builder, the setting appears on Get Records as Filter Records → How to Find Records and on DML elements as Run in System Context (without sharing) / Run in System Context (with sharing) toggles. The XML representation is what audit scripts and CI lint should target.

Concept 3 — The Spring '21 Default Change

Before Spring '21 (API 51.0):

• Record-triggered flows defaulted to User Context (sharing-enforced).
• Auto-launched flows defaulted to System Context Without Sharing.

In Spring '21 (API 52.0):

• Record-triggered flows changed default to System Context Without Sharing.
• The change applies only to flows created or saved at API 52.0 or higher.

Implications for audit:

• A flow with apiVersion < 52.0 and no explicit runInMode runs in User Context — it may unexpectedly fail to read records the triggering user can't see.
• A flow with apiVersion >= 52.0 and no explicit runInMode runs in System Context Without Sharing — it may unexpectedly bypass sharing.
• "Saving" a legacy flow in Flow Builder bumps its API version and silently changes its security model. This has caused production data leaks. Always check apiVersion and runInMode together before re-saving.

Concept 4 — $User, $Profile, $Permission Merge Fields

These global merge fields always resolve against the running user, but the definition of "running user" depends on the flow context:

A common bug: a scheduled flow checks $Permission.Edit_Sensitive_Data to decide a branch — but Automated Process user has no permission set assignments, so the check always returns false. The flow silently takes the wrong branch.

Do not use $Permission checks as a substitute for an explicit run-mode decision. Run mode controls what the flow can do at the platform level; $Permission is just a feature toggle that the flow logic happens to read.

Common Patterns

Pattern 1 — User Context UI + System Context Subflow

When to use: A Screen Flow needs to update a record the user can't see (e.g., assigning a Case to a queue the user is not a member of, or updating a parent Account's last-touched date when the user has read-only on the parent).

How it works:

[Screen Flow — User Context]                  [Auto-launched Subflow — System Context Without Sharing]
   ┌────────────────────┐                          ┌────────────────────────────┐
   │ Capture user input │ ── invoke subflow ──>    │ Update parent Account      │
   │ (in user's context)│                          │ Insert audit log record    │
   └────────────────────┘                          │ Return success/failure flag│
              │                                    └────────────────────────────┘
              ▼
   ┌────────────────────┐
   │ Show confirmation  │
   │ to user            │
   └────────────────────┘

The Screen Flow stays in User Context — the user only sees fields they're entitled to. The subflow is configured as System Context Without Sharing and does the privileged write. Pass only the minimum fields needed (record Id + the new value) — never let the subflow re-read user-visible data and round-trip it back to the UI.

Why not the alternative: Setting the entire Screen Flow to System Context Without Sharing exposes every Get Records and Display Field to bypass FLS — meaning a screen that should show only the user's allowed fields suddenly shows everything. The bug surfaces months later when an auditor asks why an intern saw the CEO's compensation.

Pattern 2 — Without Sharing for Bulk Reparenting

When to use: A scheduled or batch-replacement flow needs to reassign ownership of Cases from a departing rep to a queue, even when the running Automated Process user has no specific share grants.

How it works:

• Flow type: Scheduled (auto-launched).
• Overall run mode: System Context Without Sharing (default for auto-launched, but make it explicit in the XML).
• Document in the flow description: "Runs as Automated Process user with full data access — required for cross-team reparenting. Audit log written to Reparenting_Log__c per record."
• Add an Audit Log subflow that records who triggered the reparenting batch and which records were affected.

Why not the alternative: Trying to enforce sharing on a bulk reparenting flow forces the Automated Process user to be granted explicit shares to every record — operationally infeasible. The right answer is to escalate run mode AND add compensating audit controls.

Pattern 3 — FLS-Bypass Audit

When to use: Periodic security review of all active flows; triage list for agents/flow-analyzer/AGENT.md audit-mode runs.

How it works:

# Pull active Flow metadata from the org
sf project retrieve start --metadata Flow

# Inventory run-mode settings
grep -l "<runInMode>SystemModeWithoutSharing</runInMode>" force-app/main/default/flows/

# Inventory flows that depend on the Spring '21 default
for f in force-app/main/default/flows/*.flow-meta.xml; do
  api=$(grep -oP '(?<=<apiVersion>)[^<]+' "$f")
  mode=$(grep -oP '(?<=<runInMode>)[^<]+' "$f")
  if [[ -z "$mode" && $(echo "$api >= 52.0" | bc) -eq 1 ]]; then
    echo "IMPLICIT WITHOUT-SHARING: $f (api=$api)"
  fi
done

Every flow returned should be classified:

• Justified without-sharing (bulk reparenting, system maintenance, audit-log writes) — annotate the flow description and move on.
• Unjustified without-sharing (sales rep inquiry screen, customer self-service Experience Cloud flow) — file P0 ticket to convert to User Context or User Context + targeted subflow.

Why not the alternative: Trusting flow authors to remember the security implications of the default does not scale. A repeatable audit script is the only defensible posture under SOX / HIPAA / FedRAMP.

Decision Guidance

Recommended Workflow

1. Identify the flow's trigger and default mode. Record-triggered after-save? Screen? Scheduled? Look up the default from the table in Concept 1. Note the API version — anything below 52.0 has different defaults.
2. Classify data sensitivity. What objects does the flow read and write? Are any classified HR, Comp, Health, Financial, or Personal? Sensitive data raises the bar — User Context is the default unless escalation is justified in writing.
3. Map the running user. Who is the running user under each invocation path? For scheduled and PE-triggered flows, this is Automated Process — flag any $User/$Permission references that won't resolve correctly.
4. Choose the overall run mode. Use the Decision Guidance table. Default to User Context for screen flows; default to System Context With Sharing for record-triggered flows that don't need to bypass sharing; only choose Without Sharing with a justification block in the flow description.
5. Identify per-element overrides. If the flow is User Context but needs to read one specific record the user can't see, add runInMode=SystemModeWithSharing (or Without Sharing if necessary) on that single Get Records and document why.
6. Add an audit-log step for any without-sharing path. Every System Context Without Sharing write should record source flow + record Id + running user to an audit table. This is the compensating control auditors require.
7. Test with a low-privileged persona. Run the flow as a user with the minimum profile — confirm User Context paths fail closed (record not found / insufficient access) and System Context paths succeed for the documented reason.
8. Pin the API version. Set <apiVersion> explicitly in the flow XML so a later "Save" in Flow Builder does not silently flip the default.

Review Checklist

Run through these before marking work in this area complete:

• Flow XML has explicit <runInMode> set (no reliance on implicit defaults).
• Flow XML has explicit <apiVersion> pinned to a known value.
• If runInMode = SystemModeWithoutSharing, flow description contains a justification block citing the data-access requirement.
• Any per-element runInMode override is documented inline (Flow description or element label).
• No $Permission or $User.UserRoleId checks in flows whose running user is Automated Process (scheduled, PE-triggered).
• Screen Flows on Experience Cloud are User Context unless approved by security review.
• System Context Without Sharing flows write to an audit log per record affected.
• Test plan includes a low-privileged-user persona run to confirm User Context paths fail closed.
• Subflows have their own runInMode set explicitly (not assumed to inherit from parent).
• No Action element relies on bypass-the-sharing-rule semantics — Send Email Alert and similar honor their own enforcement.

Salesforce-Specific Gotchas

Non-obvious platform behaviors that cause real production problems:

1. Before-save record-triggered flows ignore the run mode setting. They always run in System Context as part of the triggering DML transaction. Configuring User Context on a before-save flow is silently ignored — leading to a false sense of security in code review.
2. $User returns the triggering user, not the flow author or the Automated Process user, for after-save record-triggered flows. A flow that emails $User.Email to confirm a record change will email the user who saved the record — not the system or the original record owner. This often surfaces during cross-tenant data migrations where the running user is a sysadmin doing bulk loads.
3. System Context Without Sharing inherits to subflows unless the subflow explicitly overrides. Calling a subflow from a without-sharing parent does not "reset" the security boundary. To escalate-then-de-escalate, the subflow must set its own runInMode to SystemModeWithSharing or be a Screen subflow (which always asserts User Context for its screens — but its DML elements still inherit).
4. FLS still enforces in some Action elements regardless of run mode. Send Email Alert respects FLS on the merge fields it pulls into the email body. Post to Chatter respects FLS. Apex actions enforce per the Apex class's own with sharing declaration. Setting the flow to System Context Without Sharing does NOT bypass these.
5. Saving a legacy flow in Flow Builder bumps apiVersion and silently changes default run mode. A flow created at API 50.0 (User Context default) opened and saved in current Flow Builder gets bumped to the latest API version (System Context Without Sharing default) if runInMode was never explicitly set. The flow now bypasses sharing — and no diff in source control will warn you, because no element changed.
6. The Profile of the user activating the flow can affect what gets deployed. Activating a flow whose embedded Apex action class is private or whose referenced object is hidden by FLS for the activator can silently strip metadata in some legacy edge cases. Always activate flows as a sysadmin with full data + metadata access.
7. Orchestration stage assigned to a queue resolves $User to the claimant, but only after claim. Before the work item is claimed, $User references in the assigned stage are unresolved — formula evaluation defers. Test with both pre-claim and post-claim states.
8. Platform-event-triggered flows run as Automated Process for standard PEs, but as the PE-defined "Run As" user for high-volume PEs. The $User resolution differs. Check the PE's "Subscriber Run As User" setting before assuming Automated Process.

Output Artifacts

Related Skills

• apex/apex-managed-sharing — when run-mode escalation isn't enough and the right answer is to grant explicit programmatic shares.
• security/record-access-troubleshooting — when a User Context flow can't see a record the user expects; debug at the sharing-rule level before changing run mode.
• security/dynamic-sharing-recalculation — when bulk run-mode changes affect downstream sharing calculations.
• flow/flow-error-monitoring — wire fault paths from System Context Without Sharing flows to a monitored audit log.
• flow/auto-launched-flow-patterns — subflow design where run-mode boundaries matter.
• flow/record-triggered-flow-patterns — broader patterns for record-triggered flows; this skill is the security overlay.
• apex/apex-system-runas — when designing tests for flows with explicit run-mode escalation.

Official Sources Used

• Salesforce Help — Configure Flow Run Behavior: https://help.salesforce.com/s/articleView?id=platform.flow_distribute_run_user.htm
• Salesforce Help — Run-Mode Considerations for Flows: https://help.salesforce.com/s/articleView?id=platform.flow_considerations_run_user.htm
• Salesforce Help — How Does Flow Security Work?: https://help.salesforce.com/s/articleView?id=sf.flow_distribute_security.htm
• Salesforce Spring '21 Release Notes — Default Run Mode for Record-Triggered Flows changed to System Context Without Sharing.
• Salesforce Developer — Apex Sharing Keywords (with sharing / without sharing / inherited sharing): https://developer.salesforce.com/docs/atlas.en-us.apexcode.meta/apexcode/apex_classes_keywords_sharing.htm
• Salesforce Developer — Flow Metadata API (runInMode element): https://developer.salesforce.com/docs/atlas.en-us.api_meta.meta/api_meta/meta_visual_workflow.htm
• Salesforce Architects — Well-Architected Security Pillar: https://architect.salesforce.com/well-architected/trusted/secure