You are here:
Winter '27 (API Version 68.0)
These updates affect only flows that are configured to run on API version 68.0 and later.
You are here:
These updates affect only flows that are configured to run on API version 68.0 and later.
| View supported editions. |
A new run context option in Flow Builder guarantees that your flow always runs with the running user's access level, regardless of what runs it. The User Context–Enforces User Permissions option is available for screen flows and autolaunched flows.
Previously, flows configured to run in user context inherited elevated system-level permissions from their caller, whether another flow, Apex, or another automation. When a caller running in system context runs a flow configured for user context, the flow configured for user context inherits the caller's elevated permissions and also runs in system context.
With the User Context–Enforces User Permissions option, a flow configured with this option always runs with user-level access, giving you predictable security boundaries and full control over your flow's access level.

We use three kinds of cookies on our websites: required, functional, and advertising. You can choose whether functional and advertising cookies apply. Click on the different cookie categories to find out more about each category and to change the default settings.
Privacy Statement
Required cookies are necessary for basic website functionality. Some examples include: session cookies needed to transmit the website, authentication cookies, and security cookies.
Functional cookies enhance functions, performance, and services on the website. Some examples include: cookies used to analyze site traffic, cookies used for market research, and cookies used to display advertising that is not directed to a particular individual.
Advertising cookies track activity across websites in order to understand a viewer’s interests, and direct them specific marketing. Some examples include: cookies used for remarketing, or interest-based advertising.