---
schema_version: "1"
id: 3e28b23d8d7a82b6594fb864c9abedb8126485d9dff73423b846310aaa805b2c
title: Build Rich Screens with Custom Screen Components
collection: admin
version: current
locale: en-us
portal_url: https://docs.salesforce.com/admin/current/en-us/platform/264-0-0/flow_build_extend_lc_screen.md
canonical_url: https://help.salesforce.com/s/articleView?id=platform.flow_build_extend_lc_screen.htm&release=264.0.0&type=5
source_site: help.salesforce.com
content_type: documentation
content_hash: 78f7dd93b4068f11c2661b067fd0906a7a8aec9293f2913e676bdff719c435c5
description: Use screen components to unlock the look, feel, and functionality of your flow screens.
products:
  - Flow Builder
  - Salesforce Platform
release: "264"
---
# Build Rich Screens with Custom Screen Components

Use screen components to unlock the look, feel, and functionality of your flow screens.

### 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>

You can install screen components from AppExchange or have a developer build Lightning components for you. With custom screen components, you can do these actions and more:

- Customize the navigation in your flow
- Display data in a table
- Use a branded header instead of the default flow header

![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 Before you add custom screen components to a flow screen, make sure that:

- The flow’s type is [Screen Flow](https://help.salesforce.com/s/articleView?id=platform.flow_concepts_type.htm&release=264.0.0&type=5 "A flow's type determines which elements and resources you can add and how you can distribute the flow. For example, you embed a screen flow on a page to gather information from visitors; or you distribute an autolaunched flow by using a custom button that users click to run the flow in the background. Similarly, you can add a Custom Error element only in a record-triggered flow, whereas you can add a Choice resource type only in a screen flow.").
- Users can run the flow only in [Lightning runtime](https://help.salesforce.com/s/articleView?id=platform.flow_distribute_runtime.htm&release=264.0.0&type=5 "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."). For example, don’t distribute the flow using a Visualforce component.

When you have the appropriate screen component in your org, add it to your flow screen.

1. In Flow Builder, open an existing screen, or add a Screen element to the canvas.
2. From the list of screen components, drag the appropriate component onto the screen canvas.
    
    If a screen component is built from a Lightning component, it has a lightning bolt icon next to its name. If the custom screen component includes an API name and label, the label is shown on the screen canvas.
3. Use values from the flow to set the screen component’s attributes.
4. To use values from the screen component as resources later in the flow, start typing the API name of the screen component.
    
    We automatically store all the attribute values in a variable with the same name as the screen component’s API name.
    
    To store the action’s output values manually, select **Manually assign variables (advanced)**.

![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 By default, screen components that run on Lightning runtime version 58 and prior have no memory. If a user enters a value, and then does one of the following, the value is lost.

- Navigates to another screen and returns to the component’s screen.
- Pauses the flow then resumes it.
- Navigates to the next screen and triggers an input validation error.

Setting the attribute enables a flow to remember the value. The flow stores the value automatically. If you store values manually, store the attribute’s output value in a variable.

#### See Also

- [Available Screen Components](https://help.salesforce.com/s/articleView?id=platform.flow_ref_elements_screencmp.htm&release=264.0.0&type=5 "Salesforce provides several standard screen components that extend the types of input fields available in screens.")
- [_Lightning Web Components Dev Guide_: Configure a Component for Flow Screens](https://developer.salesforce.com/docs/component-library/documentation/en/lwc/lwc.use_config_for_flow_screens)
- [_Lightning Aura Components Developer Guide_: Customize Flow Screens Using Aura Components](https://developer.salesforce.com/docs/atlas.en-us.lightning.meta/lightning/components_config_for_flow_screens_intro.htm)
- [Extend Flows with Lightning Components](https://help.salesforce.com/s/articleView?id=platform.flow_build_extend_lc.htm&release=264.0.0&type=5 "To build a richer flow screen, add Aura components or Lightning web components to your flow. To perform an action without going through the server, add Aura components to your flow.")