You are here:
Two-Column Flow Considerations
If your org has Lightning runtime enabled, you can control whether a flow displays in one column or two columns. Before you use this feature, understand how the flow layout currently behaves.

Use more general search terms.
Select fewer filters to broaden your search.
You are here:
If your org has Lightning runtime enabled, you can control whether a flow displays in one column or two columns. Before you use this feature, understand how the flow layout currently behaves.
| View supported editions. |
These considerations don’t apply to the Section component in flow screens.
The layout setting is applied at the flow level. So you can’t control the layout at the screen or field level. If you set a flow to use two columns, every screen in that flow displays in two columns.
You can’t manually control which fields go in which columns. If the flow is set to display two columns, the fields alternate in each column. The odd fields (first, third, fifth, and so on) are placed in the left column. The even fields (second, fourth, sixth, and so on) are placed in the right column.
If your users navigate screens with the Tab key, they tab through all the fields in the left column and then all the fields in the right column. You can’t configure the fields to tab left-to-right.
The flow layout isn’t responsive to the user’s screen dimensions. It uses the same layout whether the user’s screen is 1 inch wide or 20 inches wide.
For flows that are distributed via Experience Builder, the Lightning App Builder, or the utility bar, each flow screen that contains a Section component ignores the Layout property.
For flows that are distributed via URL, each flow screen that contains a Section component
ignores the flowLayout URL parameter.

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.