---
schema_version: "1"
id: 42b09d0993a492432d2b9d431407abc717107e94a18b3691b61e745575cc3edb
title: Set Flow Run Context
collection: admin
version: current
locale: en-us
portal_url: https://docs.salesforce.com/admin/current/en-us/platform/264-0-0/flow_distribute_system_mode.md
canonical_url: https://help.salesforce.com/s/articleView?id=platform.flow_distribute_system_mode.htm&release=264.0.0&type=5
source_site: help.salesforce.com
content_type: documentation
content_hash: b5e73b71271e16453902dc0b55e81abaceb6612bdb8847d5a4aef47871be63f3
description: Override the default run context of a flow to control what data it can access. Run a flow in system context with or without sharing, or enforce user-level access regardless of the caller.
products:
  - Flow Builder
  - Salesforce Platform
release: "264"
---
# Set Flow Run Context

Override the default run context of a flow to control what data it can access. Run a flow in system context with or without sharing, or enforce user-level access regardless of the caller.

### 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;"><a href="https://help.salesforce.com/s/articleView?id=platform.flow_ref_supported_editions.htm&amp;release=264.0.0&amp;type=5" title="Learn about the editions and user interfaces that support Flow Builder. Some Flow Builder features integrate with other Salesforce products that require additional licenses.">View supported editions.</a></td></tr></tbody></table>

<table class="slds-table slds-table_bordered slds-max-medium-table_stacked slds-m-bottom_small permission">
        <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:left;vertical-align:top;" id="d104619e59">User Permissions Needed</th>
          </tr>
        </thead>
        <tbody>
          <tr class="">
            <td data-label="User Permissions Needed" class="slds-cell-wrap" style="vertical-align:top;" headers="d104619e59 ">To open, edit, create, activate or
              deactivate a flow using all flow types, elements, and features available in Flow
              Builder, including Einstein and Agentforce for Flow:</td>

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

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

- Open the flow in Flow Builder.
- Click ![View properties](https://sf-zdocs-cdn-prod.zoominsoftware.com/tdta-platform-platform_automation-264-0-0-production-enus/60568438-ec7e-4665-acd1-7c80dcbe60d5/platform_automation/images/flow/flow_properties.png).
- Click **Show Advanced**.
- In the How to Run the Flow dropdown, select a context.
    
    ![Note](https://sf-zdocs-cdn-prod.zoominsoftware.com/tdta-platform-platform_automation-264-0-0-production-enus/60568438-ec7e-4665-acd1-7c80dcbe60d5/images/icon_note.png)
    
    Note If the dropdown isn’t available, you can’t change the flow run context for the type of flow.
    
    - User or System Context—The context is determined by how the flow is launched.
    - User Context–Enforces User Permissions—The flow always runs with the running user’s access level, even if its caller runs in system context. This option is available for screen flows and autolaunched flows on API version 68.0 and later.
    - System Context with Sharing—The flow respects org-wide default settings, role hierarchies, sharing rules, manual sharing, teams, and territories. But it doesn’t respect object permissions, field-level access, or other permissions of the running user.
    - System Context without Sharing—The flow can access all data.

#### See Also

- [Flow Run Context](https://help.salesforce.com/s/articleView?id=platform.flow_distribute_context.htm&release=264.0.0&type=5 "Flows run in user context or system context. For a flow running in user context, the running user’s profile and permission sets determine the object permissions and field-level access of the flow. For a flow that runs in system context, whether it runs with or without sharing determines its data access. Understanding context helps you control what your flows can read and update on behalf of your users.")