Compact Layouts and Path

1. Why This Topic Matters

Compact Layouts and Path sit inside the Advanced Objects and Applications domain of the Salesforce Advanced Administrator exam. They are two of the most visible user-experience tools an administrator controls in Lightning Experience and the Salesforce mobile app. Exam writers love them because they test whether you understand the difference between similar-sounding features: page layouts versus compact layouts, compact layouts versus Path key fields, Path versus Kanban, and assignment by record type versus assignment by profile. If you confuse these, you will lose easy points. If you master them, you can answer scenario questions in seconds.

In the real world, these features directly influence user adoption. Compact layouts decide what a rep sees in the first second of opening a record on a phone; Path decides whether a rep knows what to do next at each stage of a sale or case. The exam reflects this by asking how an administrator would surface key information or guide users through a process with declarative tools only.

2. Compact Layouts: What They Are

A compact layout is a lightweight, ordered list of fields that controls what appears in the condensed views of a record. It does not control the full detail page (that is the page layout and the Lightning record page). Compact layouts drive:

- The Highlights Panel at the top of a record page in Lightning Experience
- The record header area in the Salesforce mobile app
- Record previews / hover cards when you pause over a lookup or a link
- Expanded lookup cards and Chatter feed item record snippets
- Record headers in some related list and console contexts

Key facts you must know:

- You can add up to 10 fields to a compact layout.
- The first field in the list becomes the record header (the big title at the top).
- In Lightning Experience the Highlights Panel shows the first 7 fields; in the mobile app the record header shows the first 4 fields. Order therefore matters: put the most important fields first.
- Every object (standard and custom) has a System Default compact layout that cannot be edited, but you can create a new one or clone and then set yours as the primary compact layout.
- Only one compact layout can be primary per object, but you can override it by record type using Compact Layout Assignment.
- Compact layouts are NOT assigned by profile. This is the single most tested distinction. Page layouts are assigned by profile and record type; compact layouts are assigned per object and optionally per record type only.
- Field-level security still applies. If a user lacks read access to a field on the compact layout, it simply does not appear for that user.
- Some field types cannot be placed on a compact layout, notably long text area, rich text area, and multi-select picklist. Formula, lookup, picklist, number, date, and text fields are all fine.
- Compact layouts exist for both standard and custom objects and are edited from Object Manager > (Object) > Compact Layouts.

3. Compact Layouts: How They Work

Setup flow: Object Manager > select object > Compact Layouts > New. Give it a label and API name, add and order fields, Save. Then click Compact Layout Assignment > Edit Assignment, choose the Primary Compact Layout, and if the object has record types, use the Record Type Overrides tab to assign a different compact layout to specific record types.

When a user opens a record, Salesforce determines the record type, finds the assigned compact layout (or falls back to the primary), filters the fields through field-level security, and renders the first 7 (desktop) or first 4 (mobile) visible fields in the highlights area. On a Lightning record page the Highlights Panel component reads this layout automatically; you do not pick fields in Lightning App Builder for the standard Highlights Panel. Newer orgs may also see a Dynamic Highlights Panel component that lets you choose fields directly in App Builder (up to 12 fields) without a compact layout; if a question explicitly describes picking highlight fields inside Lightning App Builder, that is the dynamic version, but the classic exam answer for record highlights, mobile header, and hover cards is the compact layout.

Typical scenario: Sales reps on mobile want to see Account Name, Phone, Industry, and Owner immediately when they open an account, and Support reps want Account Name, SLA Level, Support Tier, and Phone. Answer: create two compact layouts and assign them to the Sales and Support record types. If there are no record types, you would need to create them (or accept a single primary layout). You would not try to assign compact layouts by profile because that option does not exist.

4. Path: What It Is

Path is a visual, step-by-step guidance component that appears across the top of a record in Lightning Experience and the mobile app. It is built on a picklist field (for example Opportunity Stage, Lead Status, Case Status, or any custom picklist). Each picklist value becomes a step (chevron). For each step, the administrator can define:

- Up to 5 Key Fields that display beneath the path for that step, editable inline if the user has edit access and the field is editable
- Guidance for Success: rich text (up to 1,000 characters) with tips, links, policy reminders, or checklists

Path is available on Accounts (including Person Accounts), Campaigns, Cases, Contacts, Contracts, Leads, Opportunities, Orders, Quotes, Work Orders, Work Order Line Items, Service Appointments, and custom objects. It is a Lightning Experience and mobile feature only; it does not render in Salesforce Classic (the Classic predecessor was called Sales Path, limited to Leads and Opportunities).

Additional Path features:

- Celebrations: toss confetti when a record reaches selected picklist values (for example Closed Won). You choose which steps trigger it and how often (always, sometimes, rarely).
- Remember User Path Preferences: lets Path remember whether each user left the details section expanded or collapsed.
- Mark Stage as Complete / Mark as Current Stage buttons advance the picklist directly from the path.
- On Opportunities, all Closed stages (Closed Won and Closed Lost) are grouped into a single Closed step; the user selects the specific closed stage when completing it. On Leads, the Converted status appears as the final step and is handled by lead conversion.
- Validation rules, field-level security, and record locking still apply. If a validation rule blocks a stage change, the user sees the error in the path. If the user cannot edit the picklist, the path is read-only.
- Multi-select picklists cannot be used as the Path field.

5. Path: How It Works

Setup flow: Setup > Path Settings > Enable. Click New Path. Step 1: name the path, choose the object, choose the record type (or Master if none), and choose the picklist field. Step 2: for each picklist value, select up to 5 key fields and write Guidance for Success. Step 3: optionally enable celebrations, choose whether the path is Active, and save.

Key architectural rules:

- You can create one path per object per record type (for a given picklist). To give different teams different guidance, create separate record types and a separate path for each.
- The Path component must exist on the Lightning record page. Standard record pages include it automatically once Path is enabled, but on a custom Lightning record page you may need to drag the Path component into place in Lightning App Builder. If a question says the path was created and activated but users do not see it, check the Lightning record page and the record type assignment.
- Deactivating a path hides it without deleting it. Only an active path displays.
- Key fields on the path are configured in Path Setup, not on the compact layout and not on the page layout. This is a classic trick: changing the compact layout does not change Path key fields.
- Path is not Kanban. Kanban is a list-view visualization that groups records into columns by a picklist and allows drag-and-drop; Path is a per-record guidance bar. Both rely on a picklist, but they are configured and used differently. Kanban card fields come from the list view columns, not from Path or compact layouts.
- Path does not automate anything by itself. It guides the human. If a scenario needs automatic field updates when a stage changes, that is Flow, not Path.

6. Comparing the Three Layout-Style Tools

Page Layout: controls fields, sections, related lists, and buttons on the full record detail/edit view. Assigned by profile + record type.
Compact Layout: controls the highlights panel, mobile header, hover cards, and feed snippets. Up to 10 fields; first 7 on desktop, first 4 on mobile. Assigned by object + record type only (no profile).
Path: a picklist-driven guidance bar with up to 5 key fields and guidance text per step. One path per object per record type. Lightning and mobile only.

7. Exam Tips: Answering Questions on Compact Layouts and Path

Tip 1 - Match the keyword to the feature. Words like highlights panel, record header, mobile app top of record, hover, preview, Chatter feed snippet point to Compact Layout. Words like guidance, stage-by-stage, coaching, next steps, confetti, celebration, chevrons, Mark Stage as Complete point to Path. Words like columns, drag and drop, summarize amounts by stage point to Kanban. Words like related lists, sections, buttons, edit page point to Page Layout.

Tip 2 - Remember the numbers. Compact layout: 10 fields max, 7 shown on desktop highlights, 4 shown on mobile, first field is the header. Path: 5 key fields per step, 1,000 characters of guidance per step, one path per object per record type. Number-based distractors are common.

Tip 3 - Record type, not profile. Any answer that says to assign a compact layout to a profile is wrong. If different users need different highlights, the correct answer involves record types and Compact Layout Assignment overrides. The same logic applies to Path: different paths require different record types.

Tip 4 - Watch for the wrong tool for key fields. If users want different fields to appear under each stage in the path, the fix is in Path Setup, not the compact layout and not the page layout. Conversely, if a field is missing from the highlights panel, check the compact layout and field-level security, not Path.

Tip 5 - Troubleshooting questions. Path not visible? Check: Path is enabled in Path Settings, the path is Active, it is built for the user's record type, the Path component is on the Lightning record page, and the user is in Lightning (not Classic). Highlights panel blank or missing fields? Check field-level security for the user's profile/permission sets and confirm the correct compact layout is assigned for the record type.

Tip 6 - Path does not replace automation or validation. If the scenario requires enforcing that a field is populated before moving to a stage, Path alone will not do it; you need a validation rule (Path will display the error). If the scenario requires updating other fields automatically, you need Flow. Path is for guidance and visibility; eliminate answers that credit Path with enforcement or automation.

Tip 7 - Classic versus Lightning. Both Path and compact layouts (for highlights) are Lightning Experience and mobile features. If a question stresses that users still work in Salesforce Classic and want a guided stage bar, the honest answer is that Path is not available in Classic and the users should move to Lightning.

Tip 8 - Field type eligibility. If an answer proposes putting a long text area or rich text field on a compact layout, it is a distractor. If an answer proposes building a Path on a multi-select picklist, it is a distractor. Path can be built on a custom picklist on a custom object; do not assume it is limited to Opportunity Stage and Lead Status.

Tip 9 - Read for the audience. Mobile emphasis strongly favors compact layouts (the mobile record header is entirely driven by the compact layout). Onboarding, training, and consistency emphasis strongly favors Path (Guidance for Success is designed for exactly that).

Tip 10 - Eliminate, then choose the declarative, lowest-effort option. The Advanced Administrator exam consistently prefers configuration over code and the simplest feature that fully meets the requirement. If a compact layout change or a Path tweak solves the stated problem, do not pick a Lightning component, Visualforce, or Apex answer.

8. Quick Review Checklist

- Compact layout = highlights, mobile header, hover cards, feed snippets; 10 fields max; first 7 desktop, first 4 mobile; assigned per object and record type; System Default cannot be edited; FLS applies; no long text, rich text, or multi-select.
- Path = picklist-driven guidance; 5 key fields and 1,000-character guidance per step; celebrations; one path per object per record type; Lightning and mobile only; available on Lead, Opportunity, Case, Contact, Account, Campaign, Contract, Order, Quote, Work Order, Work Order Line Item, Service Appointment, and custom objects; must be enabled, active, and present on the record page.
- Page layout = profile plus record type; Kanban = list view columns; Flow and validation rules = automation and enforcement.

Master these distinctions and the Compact Layouts and Path questions on the exam become some of the most reliable points you can earn.