Tips for Building Optimized Record Pages

Use best practices when creating record pages in the Lightning App Builder to increase staff efficiency throughout their interaction with your records.

Getting Started

As you begin configuring your org with custom objects, record types, or just want a custom view of standard object information, you will need to create record pages to empower staff to interact with your data in a meaningful way. To get started creating a record page, you will use the Lightning App Builder (external). You have the freedom to do many things within the Lightning App Builder, but there are some best practices and considerations we recommend as you build.


Salesforce provides many different page template options you can use when creating a new record page.

There are two templates we recommend to optimize your record interaction depending on how the record is used:

  • Header & Right SidebarWe recommend you use the default Header & Right Sidebar page template in cases where staff will view, interact, and collaborate on different pieces of information simultaneously, like in the case the record is related to many other records. With this template, staff can view the most important information in the main column and additional information simultaneously in a smaller sidebar on the right.
  • Header & One Column—We recommend you use the Header & One Column page template in cases where staff will not need to view different pieces of information simultaneously or if the information in the main column needs more space, like on a configuration record. With this template, staff can view the all information in the main column.


We recommend you use a consistent naming scheme for your record pages to help you distinguish the purpose of each.

Because Lightning App Builder is also used to create home pages and app pages, it is important to include "Record Page" in the name. Also, it is important to include the object name because all pages built in Lightning App Builder are collectively visible within certain areas in Salesforce. The Lightning App Builder allows you to create various list views to help manage your lightning app records. So based on your naming you could create a few list views to help group your association's specific record pages.

Single Record Page

If you create only one record page for an object, we recommend the following naming format for the record page label:

[association acronym] [object name] Record Page

The API name follows the same standard except the underscores and dashes are removed:

[association acronym][object name]RecordPage

Example: For the committee membership object, the record page label would be ISEN Committee Membership Record Page and the API name would be ISENCommitteeMembershipRecordPage.

Multiple Record Pages

If you create multiple record pages for an object—for example, a record page for each record type—we recommend the following naming format for the record page label:

[association acronym] [object name] Record Page - [record type name]

The API name follows the same standard except the underscores and dashes are removed:

[association acronym][object name]RecordPage[record type name]

Example: For the product object membership record type, the record page label would be ISEN Product Record Page - Membership and the API name would be ISENProductRecordPageMembership.


In the header, we recommend you include the Highlight Panel Lightning component, which contains the most vital data for your team defined in the compact layout for the record.

Below the Highlight Panel, we recommend you include the Related List Quick Links Lightning component. With the Related List Quick Links component, staff can view multiple related lists in quick succession just by hovering over a link. And, they can complete actions right from within the hover pane. Learn more (external).


We recommend you use the Tabs component within each column on the page. Using tabs in each column is done throughout Salesforce and Nimble AMS, and provides context for the information in each tab, and streamlines staff interaction. When naming each tab, we recommend you use names recommended by Salesforce, or used throughout Nimble AMS whenever possible. We also recommend you use individual Related Lists components within each tab instead of one Related List component, which can become cumbersome.

In the case of a Header & Right Sidebar page template, we recommend you add applicable tabs in the specified order:

Main Column Tabs

The main column is where staff view and interact with record information.

  1. Related—This includes Related List components for:
    1. Notes, if available
    2. Files
    3. Any related lists not included in the Primary, Secondary, or Tertiary Groups
  2. Details—This includes the Record Detail component, which is the demographic block of fields, sections, and custom links defined in a page layout.
  3. "Secondary Group" (optional)—This includes the second most important group of Related Lists components for the object.
  4. "Tertiary Group" (optional)—This includes the third most important group of Related Lists components for the object.

Right Sidebar Tabs

The right sidebar is where staff collaborate on the record.

  1. "Primary Group"—This includes the most important group of Related Lists components for the object which staff can immediately view.
  2. Activity—This includes the Activities component.
  3. Chatter—This includes the Chatter component.

In the case of a Header & One Column page template, we recommend you include applicable tabs in the main column.

  Show Me an Image...

Nimble AMS, Staff View, Setup, Record Page Tabs

Using Primary, Secondary, and Tertiary Group Tabs

The "Primary Group", "Secondary Group", and "Tertiary Group" tabs are optional depending on your needs, and contain groups of related lists. These tabs are contextually named and you can use them to thematically collect related lists into distinct tabs, rather than having a single, scroll-intensive Related tab. Again, we recommend you use tab names suggested by Salesforce whenever possible and create a custom tab name only when none of the provided tab names applies. This ensures a consistent staff experience.

The group tabs are typically one or more of the following, in the specified order:

  1. Build—Related Lists components used for configuration and setup of functionality.
    • Example: On an event record, the Build tab displays various related records to set up the event, such as products, event session groups, and event questions.
  2. Order—Related Lists components corresponding to the Nimble AMS order process and workflow. This includes any order and cart objects as well as other supporting objects such as transactions.
    • Example: On a donation record, the Order tab displays related order information, such as the order item lines.
  3. Engagement—Related Lists components involving account historical/participation records, such as committee membership, registrations, and memberships.
    • Example: On a membership type record, the Engagement tab displays related membership records.

These groups are only added as needed; specifically:

  • For the Header and One Column page template, there is no sidebar, therefore there is no "Primary Group" tab.
  • Only some objects have a "Secondary Group" tab and of those, only a subset have a "Tertiary Group" tab.

Nested Tabs

In cases where you create a record page for an object with a vast amount of related records or configuration information, you can nest a Tabs component within a Tabs component to create sub-tabs. As an example, see the tabs and sub tabs on the entity object record page.

On This Page

In This Section