An organization configures three distinct custom Lightning Record Pages for the Account object within Lightning App Builder:
- Account_Page_Global is assigned as the Org Default across all desktop and mobile views.
- Account_Page_Sales is assigned as the App Default for the 'Sales Hub' Lightning App.
- Account_Page_Enterprise is assigned to the 'Sales Hub' Lightning App, paired specifically with the 'Enterprise' Record Type and the 'Custom: Sales Manager' Profile.
A sales representative who is assigned the 'Custom: Sales Representative' Profile opens an Account record with the 'Enterprise' Record Type while navigating inside the 'Sales Hub' Lightning App. Which Lightning Record Page will be displayed to the user?
- Account_Page_SalesAnswer
- BAccount_Page_Enterprise
- CAccount_Page_Global
- DThe standard Salesforce System Default layout
Answer
Account_Page_Sales will be displayed because the user's profile does not match the profile criteria of the triple-combination assignment, causing activation precedence to fall back to the App Default.
Salesforce evaluates Lightning Record Page activation assignments using a clear three-tiered hierarchy: 1) App, Record Type, and Profile combination, 2) App Default, and 3) Org Default. In this scenario, the combination assignment is specified for the 'Custom: Sales Manager' profile. Because the viewing user possesses the 'Custom: Sales Representative' profile, the combination assignment fails to match. Salesforce then evaluates the next priority tier, which is the App Default for the 'Sales Hub' app, correctly rendering Account_Page_Sales.
Step-by-Step Solution
Key Concept
Lightning Record Page Activation Precedence