Mini View
The Mini View in Salesforce Classic was the right-side panel that surfaced record details when a user opened the Service Cloud Console.
Definition
The Mini View in Salesforce Classic was the right-side panel that surfaced record details when a user opened the Service Cloud Console. It showed selected fields from the primary record (the case being worked on), with related records (Contact, Account) listed below. Admins configured the Mini View via the Mini Page Layout for each object that participated in the Console. The feature predated Lightning Experience and was specific to Salesforce Classic''s Console product.
Lightning Experience replaced the Mini View concept with the Service Console''s right sidebar (utility bar plus highlights panel plus related records panel), all configured via Lightning App Builder, Compact Layouts, and standard related-list configuration. The Mini View term persists in older training material and inherited org documentation; modern Salesforce orgs do not configure Mini Views because the Lightning Service Console layout is fundamentally different. Treat the term as historical context for any Classic-to-Lightning migration.
The Mini View as a Classic Service Console concept
Classic Service Console layout
Salesforce Classic''s Service Console (the predecessor to the Lightning Service Console) had a multi-pane layout: tabs across the top, the primary record in the center, and a Mini View panel on the right. The Mini View showed selected fields from the primary record plus related records the agent might need quick access to during a call.
Mini Page Layout as the configuration
Admins configured the Mini View''s contents via the Mini Page Layout for each object in the Console. The Mini Page Layout selected a subset of the full Page Layout''s fields and ordered them for the side-panel display. Each object that appeared in the Console (Case, Account, Contact) had its own Mini Page Layout.
The Lightning Service Console replacement
Lightning Experience replaced the Mini View with a multi-component sidebar: the Highlights Panel at the top (driven by Compact Layout), related-record components in the body (configured via Lightning App Builder), and the Utility Bar at the bottom for cross-page tools. The unified Lightning architecture is more flexible than the Classic Mini View.
Component-based configuration
Where Classic had a single Mini View configured via Mini Page Layout, Lightning has multiple specialized components: Highlights Panel for key fields, Related Lists for related records, Path for case progression, Knowledge for help articles, custom Lightning Web Components for specialized work. Each component is configured separately; the combination produces the Console experience.
Migration from Classic to Lightning
Orgs migrating from Classic Service Console to Lightning Service Console redesign the right-side panel rather than porting the Mini View directly. The Lightning Component model is more powerful but also more configuration; plan a fresh design pass during migration.
Where Mini Views still exist
Customer orgs still on Salesforce Classic Service Console continue to use Mini Views. The configuration remains in Setup; the right-panel display still renders. Once the org migrates to Lightning Service Console, the Mini View configuration becomes dead metadata.
Cert exam relevance
Older Service Cloud Consultant exams covered Mini Views as part of Classic Console configuration. Current exams focus on Lightning Service Console and its component model; Mini Views appear only in legacy context questions. Knowing Mini View was the Classic equivalent is enough for modern exam mentions.
Migrate from Mini View to Lightning Service Console
The migration redesigns the right-side panel from scratch. Plan a Lightning Service Console rollout that takes advantage of the component model rather than porting the Classic configuration.
- Inventory current Mini View configuration
Setup, Object Manager, each object in the Console, Page Layouts, Mini Page Layout. Document the field sets per object.
- Design the Lightning Service Console
Plan the layout: Highlights Panel content, related-record components, custom Lightning Web Components for specialized agent needs.
- Configure Compact Layouts
Setup, Object Manager, each Console object, Compact Layouts. Pick the field set that drives the Highlights Panel and related Lightning surfaces.
- Build the Lightning Record Pages
Use Lightning App Builder to assemble the Console layout: drop components into the right regions, configure properties, save.
- Activate the Lightning Service Console
Make Lightning Experience the default UX. Train agents on the new layout; expect a brief productivity dip during the transition.
- Retire Mini Page Layouts
Once Lightning is active, Mini Page Layout edits do nothing. Stop maintaining them; remove from internal documentation.
- Mini Views are Classic-only. They do nothing in Lightning Service Console.
- The Lightning architecture is more flexible but also more configuration. Plan a fresh design rather than direct migration.
- Agent training matters. The Lightning layout differs enough from Classic that veteran agents need a few weeks to adjust.
- Documentation drift is severe. Treat any Salesforce article older than 2018 referencing Mini Views as historical context.
Trust & references
Cross-checked against the following references.
- Service Console OverviewSalesforce Help
- Lightning Service Console DesignSalesforce Help
Straight from the source - Salesforce's reference material on Mini View.
- Mini Page LayoutsSalesforce Help
About the Author
Dipojjal Chakrabarti is a B2C Solution Architect with 29 Salesforce certifications and over 13 years in the Salesforce ecosystem. He runs salesforcedictionary.com to help admins, developers, architects, and cert/interview candidates sharpen their fundamentals. More about Dipojjal.
Test your knowledge
Q1. What is a Mini View?
Q2. What controls mini views in Lightning?
Q3. Why does mini view design matter?
Discussion
Loading discussion…