Primary Tab
In the Salesforce Classic console, the main browser-like tab that represents a primary record (like a case or account), which can have multiple subtabs showing related records, allowing agents to work across related data.
Definition
In the Salesforce Classic console, the main browser-like tab that represents a primary record (like a case or account), which can have multiple subtabs showing related records, allowing agents to work across related data.
In plain English
“A Primary Tab in the Salesforce Classic console is the main browser-like tab that represents a primary record like a case or account. It can have multiple subtabs showing related records, letting agents work across related data without losing their place.”
Worked example
Marisol, a service rep at Knotwood Furniture, runs the legacy Classic Service Console for the support team. When she opens a Case from her queue, it loads in a new Primary Tab - the main browser-tab-like row at the top of her console. Underneath that Primary Tab she opens three Subtabs: the Customer's Account, their last three Orders, and the related Knowledge article. She can have eight Cases open at once across eight Primary Tabs; each Primary Tab carries its own Subtabs, scoped to that case's investigation. Switching Primary Tabs preserves all the Subtab state - a context she doesn't have to rebuild. The Primary Tab is the workspace boundary; the Subtab is where the related drilling lives.
Why Primary Tab matters
In the Salesforce Classic console, a Primary Tab is the main browser-like tab that represents a primary record (like a case or account), which can have multiple subtabs showing related records, allowing agents to work across related data. This tab-based workspace was a key feature of the Classic console for high-volume agent work, supporting context-preserving navigation across many records.
Primary tabs and subtabs are Classic-era concepts. Lightning Service Console handles similar needs through a different workspace model that includes split view, sub-tabs, and other patterns. Understanding primary tabs matters mostly for working with Classic console references and for migration planning. New console implementations should use Lightning Service Console patterns rather than Classic primary/sub-tab structures.
How organizations use Primary Tab
Helps clients still on Classic understand primary tabs and plan migration to Lightning Service Console.
Treats primary tab references as a Classic-era signal that the org should migrate to Lightning.
Migrated from Classic primary/sub-tab structure to Lightning Service Console workspaces.
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 Primary Tab in Classic console?
Q2. What's the modern equivalent?
Q3. Should you use primary tabs today?
Discussion
Loading discussion…