Skip to content
Tutorials Center
My learning

Topics

Lesson 33 of 36 ยท Apps and Deployment

Lightning Apps, App Builder and Page Layouts

Build the Salesforce user experience: Lightning apps and navigation, Lightning App Builder pages, dynamic forms and actions, component visibility, activation and compact layouts, with JavaScript stand-ins.

Everything users see in Salesforce is configured: which apps they can open, which tabs are in the navigation bar, what a record page shows and in which order, and which buttons appear. A well-designed experience means reps find what they need in two clicks; a poor one buries the important fields beneath a long list and trains people to ignore the CRM. This lesson covers Lightning apps, Lightning App Builder pages, dynamic forms, dynamic actions, visibility rules and page activation.

The screens are described in words. The code is a labelled JavaScript stand-in for the rules that decide what a user sees; it is not Salesforce.

Lightning apps

A Lightning app is a group of navigation items for a job role or a function: Sales, Service, Marketing, Recruiting. Create one in Setup, then App Manager, then New Lightning App, and set:

  • App details and branding: name, description, icon, color.
  • App options: Standard navigation (tabs open in tabs of the workspace) or Console navigation (workspace tabs and subtabs, for service agents handling many records), and whether users can personalize the navigation items.
  • Utility items: persistent tools along the bottom of the screen, such as Notes, Recent Items, History, Phone, or a flow.
  • Navigation items: the list of tabs (objects, Lightning pages, custom tabs, web tabs, reports and dashboards).
  • User profiles: which profiles (or permission sets, via assignments) can see the app.

Users switch apps from the App Launcher (the nine-dot icon), and you can set a default app per profile. Keep the number of apps small, and the navigation to a handful of items per role.

Tabs

Objects get a tab by enabling Tab Visibility (default on, available or hidden through permission sets and profiles). Custom object tabs are created in Setup, then Tabs. A Lightning page tab displays a custom page built in the App Builder. Tabs can open web content, Visualforce pages and Lightning components.

Lightning App Builder

The Lightning App Builder (Setup, then Lightning App Builder, or Edit Page from a record) is a drag-and-drop editor for three kinds of Lightning pages:

  • App pages: a page that is not tied to one object, shown as a tab in an app (a team landing page).
  • Home pages: the page users see when opening an app.
  • Record pages: the page for a record of one object, such as an Account.

You choose a template (the layout of regions, for example Header and Right Sidebar, Three Regions) and then drag in components: Highlights Panel, Record Detail, Related Lists, Related List - Single, Activities, Path, Chatter, Report Chart, List View, Rich Text, Flow, Tabs, Accordion and custom components. The right panel shows the component's properties.

Dynamic Forms

For record pages, Dynamic Forms break the single Record Detail component into individual field components you can arrange in sections and tabs, and attach visibility rules to a field or section. Instead of one huge page layout with 80 fields, users see only the fields relevant to their record. Use Upgrade Now in the App Builder to convert a page layout to Dynamic Forms, and note that this feature is available for custom objects and a growing list of standard objects.

Dynamic Actions

Dynamic Actions show or hide buttons in the highlights panel and actions based on rules, for example, show "Escalate" only when Priority = High, and "Close as Won" only to the Sales Manager profile.

Component visibility

Any component can have visibility filters: show it only when a field has a value, when the user has a permission (a custom permission or user attribute such as profile or role), when the device is a phone or desktop, or when a page value (e.g. a record type) matches. Filters can combine with AND or OR (up to 50 conditions). Hide empty or irrelevant sections to reduce clutter, but never use visibility as security: hidden components are not secure, use field-level security and sharing for that.

Activation

A saved Lightning record page does nothing until you activate it. Click Activation and pick:

  • Org Default: all users and apps.
  • App Default: one app.
  • App, Record Type and Profile: the most specific assignment, for example Sales app, record type Enterprise, profile Sales Manager.
  • Form factor (desktop or phone).

Salesforce picks the most specific assignment that matches the user's context. Keep a short list of activations and document them, or users will complain that "my colleague sees a different page" and nobody can explain why.

Even with Lightning pages, page layouts still matter: they control which fields are required or read-only, the related lists and buttons shown in the record detail (unless Dynamic Forms replaces them), and the actions in the Salesforce mobile app's action bar. Compact layouts define the key fields in the highlight panel and in the mobile app (the first five fields appear, with the first as the title). Record types let different business processes use different picklist values and layouts (see the chapter on objects and fields).

Other experience tools: Path (a stage guide with key fields and guidance per stage), list views (with filters, pinned lists and inline editing), global actions and object-specific quick actions (create a Task, log a call, call a flow), Kanban views for opportunities and cases, Chatter feed settings, and Lightning Console configuration.

flowchart TD
  A["Lightning app (navigation, utilities)"] --> H["Home page (Lightning page)"]
  A --> T["Tab: Account"]
  T --> RP["Record page (Lightning page)"]
  RP --> HP["Highlights panel (compact layout, actions)"]
  RP --> DF["Dynamic Forms (sections with visibility rules)"]
  RP --> RL["Related lists, Path, Flow component"]
  RP --> ACT["Activation: org, app, record type, profile"]

How an app, a tab and a record page fit together.

Stand-in: which page does this user get?

This stand-in is not Salesforce. It resolves the most specific page activation for a user's context.

JS Stand-in: page activation resolution

Press Run (or Ctrl + Enter) to see the console output here.

No output.

Stand-in: visibility filters

JS Stand-in: component visibility rules

Press Run (or Ctrl + Enter) to see the console output here.

No output.

Design guidance

  1. Start from the task: what does the user do on this page in their first minute? Put it at the top.
  2. Fewer fields: show what is needed; use Dynamic Forms and tabs for the rest.
  3. One page per role only when the roles really differ; otherwise use visibility rules.
  4. Test as the user (Setup, then Login As or the View As in the App Builder).
  5. Remember mobile: the phone layout is separate.
  6. Name pages clearly and document activations; changes move to production with change sets (Change sets and deployment).

Check your understanding

Quick check ยท 4 questions

of 4 answered You scored / 4 ยท perfect!

  1. 1. Which page type is tied to one record of an object?

    A record page shows one record of a specific object.
  2. 2. What do Dynamic Forms allow?

    Dynamic Forms replace the single Record Detail component with individually placed fields and sections.
  3. 3. A Lightning record page was saved but users do not see it. Why?

    A page must be activated for the org, app, or record type and profile.
  4. 4. Is hiding a component with a visibility filter a security measure?

    Visibility only changes the page; the data can still be reached by other means.

Summary

  • Lightning apps group navigation items for a role; App Manager configures navigation, utilities and who sees the app.
  • Lightning App Builder creates app, home and record pages from templates and components; Dynamic Forms and Dynamic Actions show only what is relevant.
  • Visibility filters tidy the page but are not security.
  • Activate pages by org, app, record type and profile; the most specific match wins.

Next: Project: lead to opportunity automation