Lightning Page Visibility Rule Considerations and Limitations

General

• Visibility filters support a single value at a time, not comma-separated values. To add more than one value, add a new filter.
• Lookup fields that you want to use as a filter for a visibility rule must always have a value.
• If a user doesn’t have access to a field used as part of a component visibility filter’s criteria, the criteria evaluate to false.
• For visibility rules on dynamic actions in the Highlights Panel or Dynamic Highlights Panel, if a user doesn’t have access to a field used as part of the action's visibility filter criteria, the criteria don't apply, and therefore evaluate to true.
• If all of the components inside an individual tab on a Lightning page are hidden due to visibility rules, then Salesforce hides that tab. For example, if all components inside the Related tab are hidden, then Salesforce hides the Related tab. Also, if all of the individual tabs inside a Tabs component are hidden due to visibility rules, then Salesforce hides the entire Tabs component.
• If the default tab becomes hidden after being selected because its components were hidden due to visibility rules, then the default tab isn't reselected if one of its components becomes visible again later.
• If you set visibility criteria based on a lookup field and that lookup field resolves to a null value at run time, then the page won't load properly.
• When creating a visibility rule, sometimes an error can occur when you enter text in the Field field and then backspace. If this happens, close the visibility rule window and try again.
• Visibility rules that reference a picklist field can sometimes not work as expected for users without access to that field. This can occur when the picklist field is from the same object or from a different object via lookups. The field or component governed by the visibility rule can be incorrectly shown or hidden even when the rule criteria are met.

Limitations

• A component can have up to 10 filters.
• Some person account fields, including Email and Mobile, can’t be used in filters.

Visibility Rules and Form Factors

The Salesforce mobile app on a tablet uses the phone form factor. Salesforce viewed in a browser on a tablet uses the desktop form factor. These form factors affect component visibility on record pages differently.

If the visibility filter is “Device not equal to desktop” or “Device equals phone,” the component appears on pages in the Salesforce mobile app on a phone and a tablet. It doesn’t appear on pages viewed in a browser on a tablet or on desktop.

If the visibility filter is “Device not equal to phone” or “Device equals desktop”:

• The component appears on pages in Lightning Experience on a desktop and on pages viewed in a browser on a tablet.
• In orgs without Dynamic Forms and Dynamic Highlights on Mobile enabled, the component also appears on pages viewed in the Salesforce mobile app on a tablet. It doesn’t appear in the Salesforce mobile app on a phone.
• In orgs with Dynamic Forms and Dynamic Highlights on Mobile enabled, the component doesn’t appear in the Salesforce mobile app on a phone or a tablet.

Visibility Rules and Dynamic Forms

• Field and Field Section components are supported on desktop only. Therefore, the visibility rules you set on them are respected only in the desktop view, not on mobile. However, Dynamic Forms on Mobile gives your mobile users the same experience that your desktop users have. To avoid this issue, from Salesforce Mobile App Setup, enable Dynamic Forms and Dynamic Highlights on Mobile.
• If a field is hidden on a page due to a visibility rule, and a user edits the value of the field, its new or changed value isn’t saved.
• Dependent picklist fields don’t respect visibility rules. Even if they have visibility rules assigned to them, dependent picklist fields still appear in the View All Dependencies list.
• Component visibility rules on field sections behave differently than they do on fields. Visibility rules on fields are assessed dynamically. Changes a user makes while editing a record can make fields appear and disappear as visibility rules are evaluated. Visibility rules on field sections aren’t dynamic and don’t react to what a user does while editing. Field section visibility rules are evaluated only after the record is saved.
• If you hide a field with a visibility rule, users don’t lose access to the field’s data. Values in hidden fields remain intact and are visible outside of the Dynamic Forms-based page in places like reports, dashboards, and list views. Hidden fields are for user convenience, not for field-level security.
• When a tab is hidden by a visibility rule, any field sections within that tab are hidden in the Create and Edit windows. If all field sections on a page are contained in the hidden tab, then the Create and Edit windows are blank.