8.1 Lightning Record, Home & App Pages

Lightning Record, Home & App Pages

The Lightning App Builder is Salesforce's flagship declarative point-and-click tool for designing bespoke graphical user interfaces for desktop and the Salesforce Mobile app. Operating entirely within Setup, it enables administrators and platform app builders to construct modern, responsive user experiences without writing custom HTML, CSS, or JavaScript. By assembling standard, custom, and third-party AppExchange components onto structured page templates, app builders can tailor every screen to the specific operational workflows of distinct user personas.

On the Platform App Builder certification exam, page customization questions focus heavily on understanding the functional boundaries between page types, selecting the appropriate structural templates, and mastering the multi-tier activation precedence model that controls which page a user sees.

---

The Three Core Lightning Page Types

Lightning App Builder provides three primary page types, each engineered for a distinct operational context:

+--------------------------------------------------------------------------+
|                       LIGHTNING APP BUILDER PAGES                        |
+---------------------+-------------------------------+--------------------+
|      APP PAGE       |           HOME PAGE           |    RECORD PAGE     |
| (No Record Context) |      (No Record Context)      |  (Record Context)  |
| Top-level utility,  |  App landing page; rollups,   | Contextual sObject |
| dashboards, hubs    |  assistant, feeds, shortcuts  | details & related  |
+---------------------+-------------------------------+--------------------+

1. App Page

An App Page is a top-level, standalone page designed for high-level aggregated data, analytical dashboards, toolkits, and utility hubs.

• Context: App Pages have no record context—there is no underlying recordId or single sObject binding.
• Navigation: Once activated, an App Page can be added directly to the navigation bar of one or more Lightning Apps as a navigation tab. It can also be added to the Salesforce Mobile navigation menu.
• Typical Use Cases: Executive KPI cockpits, regional sales leaderboards, custom resource directories, and daily operational task centers.

2. Home Page

A Home Page serves as the primary landing page presented to users when they launch a specific Lightning App or click the "Home" tab in the navigation bar.

• Context: Like App Pages, Home Pages have no record context.
• Purpose: Home Pages provide users with immediate situational awareness of their workday, aggregating quarterly performance charts, upcoming calendar events, open tasks, Chatter feeds, and the Einstein Assistant.
• Persona Tailoring: Because different departments require vastly different daily starting points, Home Pages can be customized per business unit. A sales representative requires a performance chart showing closed revenue against quota alongside active lead queues, whereas a customer support agent requires real-time case queues, Omni-Channel widgets, and critical incident alerts.

3. Record Page

A Record Page is a contextual view customized for viewing, editing, and managing individual records of a specific standard or custom sObject (e.g., Account, Opportunity, Case, or custom Work_Order__c).

• Context: A Record Page is strictly bound to an individual record. When rendered, the Lightning runtime provides record context to components that implement the supported record-aware interfaces/properties. Flow inputs and custom component properties may require explicit configuration.
• Purpose: Displays the object's compact layout fields (Highlights Panel), record details, related lists, activity timelines, paths, and contextual collaboration feeds.

---

Page Templates & Structural Canvas Layouts

When creating any Lightning Page, the app builder must first select a Page Template. Templates divide the page canvas into predefined drop zones known as regions into which components are placed.

Standard Template Structures

Salesforce provides multiple responsive standard templates out of the box:

• Header and Two Columns (2:1 Ratio): The default layout for most record pages. Features a full-width header across the top (typically housing the Highlights Panel and Path), a wide left/main column (housing tabs for Record Detail, Chatter, and key Related Lists), and a narrower right sidebar (housing secondary related lists, report charts, or quick actions).
• Header and Two Equal Columns (50/50 Ratio): Equal-width dual columns beneath a full-width header.
• Header and Right / Left Sidebar: Specialized configurations optimizing screen real estate for specific monitor aspect ratios.
• Three Columns: Ideal for high-density app pages or wide desktop displays requiring simultaneous visibility across multiple data streams.
• Single Column: A simple vertical stack of full-width components, commonly selected for mobile-focused designs or streamlined executive dashboards.

Pinned Header and Pinned Region Templates

In standard scrolling templates, when a user scrolls down a long page layout, the entire viewport scrolls together, moving the top components out of view. In high-velocity service and sales environments, this causes significant operational friction: representatives lose sight of critical record status, SLAs, and primary action buttons while reviewing lengthy case history or order line items.

To solve this, Salesforce provides Pinned Templates (e.g., Pinned Header, Pinned Header and Left Sidebar):

• The pinned region remains completely static at the top or side of the browser window.
• The secondary body regions scroll independently beneath or beside the pinned region.
• Placing the Highlights Panel and Path in a pinned header ensures that vital metrics, status indicators, and primary action buttons remain accessible at all times, regardless of how far down the user scrolls.

---

The Activation Architecture: Hierarchy & Precedence

Creating a Lightning Page does not make it visible to end users; it must be Activated. Activation determines the precise conditions under which the page is rendered.

+-----------------------------------------------------------------------------+
|                   RECORD PAGE ACTIVATION PRECEDENCE ENGINE                  |
+-----------------------------------------------------------------------------+
|                                                                             |
|   [User Opens Record]                                                       |
|           │                                                                 |
|           ▼                                                                 |
|   Does an App + Record Type + Profile assignment match?                     |
|        ├── YES ──► Render Granular Custom Record Page (Highest Precedence)  |
|        └── NO                                                               |
|             │                                                               |
|             ▼                                                               |
|   Does an App Default assignment match the current App?                     |
|        ├── YES ──► Render App Default Record Page (Medium Precedence)       |
|        └── NO                                                               |
|             │                                                               |
|             ▼                                                               |
|   Render Org Default Record Page (Lowest Precedence / Universal Fallback)   |
|                                                                             |
+-----------------------------------------------------------------------------+

Record Page Activation Tiers

Record Pages support a sophisticated three-tier activation hierarchy. When a user navigates to a record, Salesforce evaluates page assignments in order of increasing specificity:

1. Org Default (Level 1 - Lowest Precedence):
   • Serves as the universal fallback for the entire organization across all apps, record types, and profiles.
   • Can be assigned to specific device form factors: Desktop, Phone, or Desktop and Phone.
2. App Default (Level 2 - Moderate Precedence):
   • Overrides the Org Default whenever the record is viewed within a specific Lightning Application (e.g., the Service Console app versus the Sales app).
   • Applies to all users and all record types within that specific app, unless a more specific assignment exists.
3. App, Record Type, and Profile (Level 3 - Highest Precedence):
   • The most granular activation tier available on the platform.
   • Assigns a specialized page layout to specific combinations of a Lightning Application, one or more Record Types, and one or more User Profiles.
   • Example: Support Engineers viewing an "Escalated" Case Record Type within the Service Console app see Page A, while Sales Managers viewing a "Standard" Case Record Type within the Sales app see Page B.

Home Page Activation Tiers

Because Home Pages lack record context, their activation options are different from Record Pages:

• Org Default: Universal landing page for all users in the organization.
• App Default: Custom landing page for a specific Lightning App.
• App and Profile Assignment: Assigns distinct landing pages to specific profiles within specific apps (e.g., Sales App + Sales Representative sees a rep-focused home page, while Sales App + Sales Manager sees a management cockpit).

---

Device Form Factor Assignments (Desktop vs. Mobile)

In modern enterprise architectures, user requirements diverge dramatically between desktop workstations and mobile devices. A desktop user on a high-resolution 27-inch monitor benefits from multi-column layouts, embedded report charts, and comprehensive related lists. Conversely, a field technician accessing the same record on a 6-inch mobile smartphone requires a lightweight, single-column interface with large tap targets and minimal data scrolling.

When activating Record Pages (at both the Org Default and App/Profile tiers), app builders can explicitly target form factors:

• Desktop: The page only renders when accessed via a desktop web browser.
• Phone: The page only renders when accessed via the Salesforce Mobile app on a mobile handset.
• Desktop and Phone: A unified responsive page that renders across all client devices.

By leveraging discrete Desktop and Phone activations, organizations can deploy tailored mobile pages that omit heavy charts or expansive tables, significantly reducing mobile memory consumption and load times.

---

Comparison: Lightning Page Types

---

Exam Traps and Architectural Best Practices

• Trap: Forgetting the Form Factor Override. If an app builder creates a specialized Phone-only Record Page and activates it as App Default, desktop users accessing that same app will continue to see the Org Default desktop layout. Always verify form factor alignments across all activation tiers.
• Trap: Profile Conflicts in Activation. A user can only have one active profile. If a user belongs to the "Custom Support" profile, Salesforce looks specifically for assignments matching that profile. If none exist, it falls back to the App Default, and finally the Org Default. Permission set assignments do not participate in Lightning Page activation.
• Best Practice: Consolidating Pages via Component Visibility. Before creating five distinct Record Pages for different profiles and activating them via App/Record Type/Profile combinations, evaluate whether a single Record Page utilizing Component Visibility Filters can satisfy the requirement. Maintaining one page with dynamically displayed components is vastly superior to maintaining multiple near-identical pages.

Official Source Check

Checked October 19, 2026: Lightning page and mobile differences.