Depending on how a flow is distributed, users see either the Classic runtime or
Lightning runtime UI when they run the flow. Like its name suggests, Lightning runtime looks and
feels like Lightning Experience.
Here’s the same flow rendered in Classic runtime (left) and Lightning runtime (right).
How to Switch to Lightning Runtime for All Flows
From Setup, enter
Process Automation Settings in the Quick Find box, then select Process Automation Settings.
Select Enable Lightning runtime for flows and save your changes.
Which Runtime Experience Do My Users See?
Flows that run from a Visualforce component always use Classic runtime. Flows that run from
a Lightning page, flow action, or custom Aura component always use Lightning runtime. All
other methods depend on whether Lightning runtime has been enabled in your org’s Process
Automation settings.
This table summarizes which runtime experience your users see based on how you distribute
the flow.
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
Always Active
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
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
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.
