--- schema_version: "1" id: f7f671d656c8316c6594819d6d4a39722b4c85be3d8bf1abe0589854d1f1a1cd title: Configuring Screen Elements collection: admin version: current locale: en-us portal_url: https://docs.salesforce.com/admin/current/en-us/platform/264-0-0/automate_flow_build_screen_flows_configuring_screens.md canonical_url: https://help.salesforce.com/s/articleView?id=platform.automate_flow_build_screen_flows_configuring_screens.htm&release=264.0.0&type=5 source_site: help.salesforce.com content_type: documentation content_hash: 2969e045b9434774faba4469707fe0529cbe3a8a0960a7a36940c460b31de871 description: Configure the overall screen properties to control what text users see and how users interact with the screen by configuring the header, footer, navigation buttons, and help text. products: - Flow Builder - Salesforce Platform release: "264" --- # Configuring Screen Elements Configure the overall screen properties to control what text users see and how users interact with the screen by configuring the header, footer, navigation buttons, and help text. ### Required Editions
View supported editions.
To access screen properties, click the screen's header in the screen preview. ## Naming and Describing Your Screen Element Give your screen element a name that describes what its purpose is. For example, Collect Contact Details or Show Confirmation Message. It's also important to add a description for your elements, including screen elements. If someone else opens your flow, or if you open it after a long time, it can provide helpful details to help you make a change or troubleshoot an error. ## Setting the Stage You can set the stage of the current screen element to be used in a progress indicator. A progress indicator gives users a visual cue about where they are in the flow. Learn about stages and progress indicators in [Showing Users Their Progress in a Screen Flow](https://help.salesforce.com/s/articleView?id=platform.flow_build_stages.htm&release=264.0.0&type=5 "Keep your users informed about which stage they’re in and how far they’ve progressed in a screen flow. Create stages to designate steps in the flow, and use a progress indicator to show all the stages and highlight the stage that the user is in.") ## Configuring the Header The header shows the flow's label and help text. In the screen properties, you can: - **Show or Hide the Header**: Control whether to show the header. The header shows the label of your flow, which can help users understand the purpose of the information they’re inputting or seeing. To name your flow in a way that you don't want users to see, hide the header. - **Add Help Text**: If you choose to show help text, a rich text editor opens where you can write helpful instructions or information for your users. This text appears in an info bubble (question mark icon) in the screen's header. Users can click the icon to read your help text. ![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 Header options are supported only in Lightning runtime. Add help text when users need extra context or instructions for completing the screen. For example, if a screen asks for specific information that isn't immediately clear, help text can explain what's needed and why. ## Configuring the Footer The footer contains navigation buttons that users click to move through your flow. Decide which buttons appear and what text is shown on your buttons, and also set a pause confirmation message, by configuring these options: Next or Finish Button If there are more screens in the flow, lets users proceed to the next screen. If it's the last screen in the flow, allows users to complete the flow. Previous Button Lets users go back to the previous screen and review or change their answers. This button is available when there's a screen before the current one. ![Tip](https://sf-zdocs-cdn-prod.zoominsoftware.com/tdta-platform-platform_automation-264-0-0-production-enus/60568438-ec7e-4665-acd1-7c80dcbe60d5/images/icon_tip.png) Tip If your flow has data elements (like Update Records) or actions (like Send Email) before the screen, consider disabling the Previous button to prevent users from accidentally running those actions multiple times. Pause Button Lets users save their progress and resume the flow later. This button is available only when **Let users pause flows** is enabled in your org's Process Automation settings. If you enable the Pause button: - Write a **Pause Confirmation Message** to tell users where and how they can resume the flow later. Be specific about where they can find their paused flows. - Customize the flow's [interview label](https://help.salesforce.com/s/articleView?id=platform.flow_ref_properties.htm&release=264.0.0&type=5 "A flow version’s properties consist of its label, description, interview label, and type. These properties drive the field values that appear on the flow’s detail page.") so users can easily identify their paused flows. - Make sure your org's Process Automation settings have **Let users pause flows** enabled. Pause Confirmation Message Shown to users when they pause a flow. You can use the standard message or add a custom message. The standard message is `This flow interview is now paused.` ## Configure Screen Actions Screen actions let you add powerful functionality to your screen by calling an autolaunched flow. With this feature, you can get or process data within a screen element without leaving the screen. For example, you can use a screen action to: - Look up related records as users make selections. - Check data against external systems. - Calculate values in real-time based on user input. For detailed information about screen actions, see [Get or Process Data Within a Screen Element with Screen Actions](https://help.salesforce.com/s/articleView?id=platform.flow_ref_elements_screen_flow_screen_actions.htm&release=264.0.0&type=5 "Screen actions make your screen elements dynamic by using an autolaunched flow to retrieve or process data. Screen actions reduce the need for you to add elements between screens and reduce the need for users to switch between screens to observe data updates. Because users click though fewer screens, they can finish a screen flow faster. Also, users benefit from screens that react to their interactions, increasing their engagement.").