Cert++
Close

Visibility on Lightning record pages

Key Takeaway

A visibility rule hides a component, field, or tab until its filter criteria are met. Rules on individual fields need a Dynamic Forms-enabled Lightning record page, and hiding a field is not security.

Visibility rules let an admin control when a component, field, or tab appears on a Lightning page. The admin adds filter conditions in the Lightning App Builder, and the page then shows or hides each item based on those conditions.

How visibility rules work

You set a visibility rule in the Lightning App Builder. You select a component, then add filter conditions and filter logic to its properties.

With no filter, a component displays as usual. After you define one or more filters and set the filter logic, the component stays hidden until the filter criteria are met.

For example, you can set a rich text component on an opportunity page to show only when the opportunity amount is US$1 million or more. On an opportunity with a smaller amount, the component stays hidden.

Visibility properties are available in these places:

  • Components on Lightning record pages, app pages, and Home pages
  • Individual tabs in the Tabs component
  • Fields on a Dynamic Forms-enabled Lightning record page

Visibility rules work the same way for standard components, custom components, and AppExchange components. Custom components need no extra work, because the Lightning App Builder handles it. In the Lightning App Builder, an icon marks each item that has at least one filter.

Platform Administrator Study Guide

Checklist progress

0/324Learned

Given a scenario, determine how to create and assign page layouts, visibility on Lightning page layouts, record types, and business processes for custom and standard objects (quick actions and global actions)

0/14

Prepare for the Exam

Play Today's Certle

Study Community

Ask questions and get the latest info from other Platform Administrator studiers.