Mini Page Layouts only apply in Salesforce Classic. If your org runs Lightning Experience, skip this and configure a Compact Layout instead. These steps show how an admin trims a mini layout from the original page layout editor in Classic.
- Open the object's page layout
In Setup, go to the object's Page Layouts list. Click Edit next to the page layout whose mini view you want to adjust. The mini layout is bound to this specific page layout.
- Click the Mini Page Layout link
In the page layout header, click Mini Page Layout. This opens an editor showing the fields and related lists the parent layout already exposes. You are filtering that set, not adding new fields.
- Select fields and related lists
Use Add and Remove to choose which fields appear in hover detail and the console mini view. Reorder with the up and down arrows. You can include up to five related lists. Keep the list short to avoid scrolling.
- Save and verify
Click Save. Hover over a record of this layout's record type in a list view to confirm the popup shows the fields you picked. Always Displayed fields from the parent layout appear automatically.
The subset of the parent layout's fields shown in the mini view. Field access and read-only status are inherited and cannot be changed here.
Up to five related lists from the parent layout. They display in the console mini view even when they contain no records.
Fields marked Always Displayed on the full page layout are forced into the mini layout and cannot be removed.
- Mini Page Layouts do nothing in Lightning Experience. Configuring one in a Lightning org is wasted effort; use the Compact Layout.
- You cannot add a field that is not already on the parent page layout. The mini layout is strictly a subset.
- You cannot assign a mini layout independently. It follows whichever profile and record type assignment the parent page layout has.
- A long mini layout forces users to scroll inside the hover popup, which undercuts the quick-glance purpose.