Layout Design Guidelines provide standards for naming and configuring Staff View layouts such as compact layouts, list views, page layouts, and search layouts. Layouts should contain the most important fields for the record. Since some layouts cannot always display all the fields included in the layout, it is important that administrators use a standard approach for selecting the sequence of fields.
The most important fields for an object are placed in each of its layouts in a particular sequence, based on the rank specified below. The rank promotes field types that provide the most clarity and efficiency, and groups similar field types together. The first rank is the highest priority field and should be added first.
Once you determine a specific sequence of fields for an object, consistently apply that same sequence to the object's compact layouts, search layouts, and list views, as much as possible, but not at the expense of clarity or efficiency for staff.
Applying a sequence of fields is simple for most layouts because they only allow you to specify a single, linear list of fields. However, page layouts uniquely allow you to group fields into sections and organize them across two columns, so this field sequence ranking is more loosely applied to page layouts. Read more about Page Layout Design Guidelines.
Keep in mind that every object is unique. You can skip a rank if it does not apply to your object or if strict adherence to these standards negatively affects the layout's clarity, efficiency, or consistency.
An alternate or shortened name that is typically always populated and helps identify records. For example, the Entity
The principal lookup field(s) that helps identify records. Lookup fields render as links so users can easily navigate to related records.
When sequencing multiple lookup fields, prioritize the lookup field that:
For example, a lookup field to Account is generally the first lookup field listed because:
For junction objects—that is, objects that link together two parent objects—the first lookup field is the first object listed in the junction object's name. For example, for Membership Type Product Link, rank
Less important lookup fields are included in the "Miscellaneous" rank.
The principal contact info for the record, listed in the following sequence:
Less important contact fields are included in the "Miscellaneous" rank.
The principal status field for the record. Some objects have both a
The status does not need to be included for an object in which nearly all records have the same status. For example, the Account
The principal date field for the object that indicates when the record occurs or begins.
If an object has an additional date field that indicates when the record ends, it can be included. For example, Committee Membership
The principal financial field(s) for the record. They are listed in the following sequence:
The principal field(s) used for Community Hub configuration, listed in the following sequence:
If Bill Me is used by the client, it can be added to layouts, as needed.
Other helpful fields for the record can be included here, at the end of the sequence, such as less important lookup fields and additional contact info. The Highlights Panel component on Lightning record pages displays email and phone fields in a dropdown list below higher-ranked fields of the same data type.
Show Me an Image...
Miscellaneous fields that exist on multiple objects—such as
Compact Layout Standards
Compact Layout Design Guidelines provide standards for when to create new compact layouts, how to name them, and how to organize fields.
List View Standards
List View Design Guidelines provide standards for when to create new list views, how to name them, and how to organize fields.
Page Layout Standards
Page Layout Design Guidelines provide standards for when to create new page layouts and how to name them. They also provide guidelines for organizing buttons, actions, sections, fields, custom links, and related lists.
Search Layout Standards
Search Layout Design Guidelines provide standards for organizing fields in search layouts. Unlike other layouts, search layouts cannot be created nor renamed.