Component visibility rules on Lightning pages
Key Takeaway
A component with visibility filters stays hidden until its filter logic is met. Device filters check the form factor, not the physical device, so a browser on a tablet counts as desktop.
Component visibility rules let an administrator show or hide parts of a Lightning page based on conditions, with no code. You add filters and filter logic to a component's properties in the Lightning App Builder. Rules can check record field values, the viewing user, the user's permissions, or the device.
How visibility rules work
A visibility rule is a set of filter conditions plus filter logic on a component's properties in the Lightning App Builder.
Visibility properties appear when you select a component on a record page, app page, or Home page. They also appear when you select a field on a Dynamic Forms-enabled record page. You can also show or hide an individual tab inside the Tabs component.
Rules work the same way for standard components and custom components. Custom components need no changes, because the Lightning App Builder handles visibility for them.
A component with no filter displays as usual. After you add one or more filters and set the filter logic, the component is hidden until the logic is met. In the Lightning App Builder, any item with at least one filter shows an eyeball icon.
When a user saves a record and the filter criteria become true, the page updates to show the component without a page refresh.
A support team adds a Rich Text component with an escalation reminder to the case record page. They add one filter: the case's Priority equals High. While Maria views a case with Priority set to Medium, the reminder is hidden. Maria changes Priority to High and saves the record. The page updates and the reminder appears, without a page refresh.