Salesforce Console
A Salesforce Console is a type of app built for fast-paced, high-volume work, where users move between many records at once instead of opening them one at a time.
Definition
A Salesforce Console is a type of app built for fast-paced, high-volume work, where users move between many records at once instead of opening them one at a time. It uses a tab-based workspace, an optional split view list panel, a footer utility bar, and keyboard shortcuts so agents and reps keep their context while they jump across related data.
In Lightning Experience, a console is just a Lightning app whose navigation type is set to Console. Salesforce ships two ready-made console apps, the Service Console for support teams and the Sales Console for sellers, and you can also build your own. Console apps are common in contact centers and call centers, where speed across cases, contacts, and accounts matters more than slow exploration.
How the Salesforce Console actually works
Console navigation versus standard navigation
The biggest difference between a console app and a normal Salesforce app is how records open. With standard navigation you see one record at a time, and clicking a related record replaces what you were looking at. Console navigation keeps several records open together on one screen, so a support agent can read a case, check the contact, and glance at the account without losing any of them. You pick the navigation style in the App Manager when you build the app, and switching a navigation type from Standard to Console (or back) changes the entire feel of the app for every assigned user. This is why console apps suit contact centers and high-volume call centers, where people work off lists and bounce between many records per hour. The trade is screen density for speed. A console packs more onto the page, which is great for trained agents and busy for casual users. For that reason most orgs reserve console apps for the teams that live in them all day, and keep lighter standard apps for everyone who only touches records occasionally.
Workspace tabs and subtabs
A console organizes open records into tabs. The top-level records are workspace tabs, and each workspace tab can hold its own set of subtabs for related records you open from it. Open a case as a workspace tab, click into its contact, and that contact opens as a subtab nested under the case rather than wiping the case off the screen. This nesting is what lets an agent fully load the context for one customer interaction, then close the whole group when the call ends. Each tab has a tab menu where users can refresh, pin, customize, or close it, and pinning keeps a frequently used record handy across sessions. Tabs remember their state, so returning to a workspace tab brings back the subtabs that were open under it. The mental model is one workspace tab per thing you are handling, with subtabs as the supporting records for that thing. Teaching agents to think in workspace tabs and subtabs is usually the single biggest adoption win when an org rolls out a console for the first time.
The utility bar
The utility bar is a fixed footer that runs along the bottom of a console app and gives users quick access to productivity tools without leaving the page. Each item you add opens in a docked panel above the footer, so things like Notes, History, Recent Items, a softphone, or an Omni-Channel widget are always one click away. You configure the utility bar in the App Manager by editing the app and adding utility items, where each item is a Lightning component with its own label, icon, and properties. Some utilities run in the background instead of opening a panel. These background utility items let developers run logic, such as listening for events or driving custom keyboard shortcuts, while the app is open and without cluttering the interface. Because the utility bar persists no matter which record tab is in focus, it is the natural home for tools an agent needs constantly during a shift. A well-built utility bar removes a lot of clicking. Putting the phone, notes, and a knowledge lookup in the footer means the agent stops hunting for them on every single interaction.
Split view, lists, and screen real estate
Console apps include a split view, a panel on the left that shows a list alongside the open record. An agent can stay on a list of cases, click each one to load it on the right, and work straight down the queue without bouncing back to a separate list page. Split view is on by default in Lightning console apps, and users can collapse or expand it to trade list visibility for more room on the record. Records opened from the split view panel open as workspace tabs, which keeps the working pattern consistent. The "Display As" control lets users flip a list between the normal table view and split view, so the same list serves both browsing and heads-down processing. This list-driven flow is why console apps fit queue-based work so well. Support, inside sales, and similar teams often spend their day clearing a list, and split view turns that list into a fast pipeline. It does eat horizontal space, so it shines on wide monitors and feels tight on small laptop screens, which is worth keeping in mind when you decide who gets a console.
Customizing and extending a console
A console is highly configurable through clicks and through code. With clicks, admins control which objects appear, design the record pages in the Lightning App Builder, choose split view behavior, set up keyboard shortcuts, and assemble the utility bar. With code, developers reach the console through the Lightning Console JavaScript API, which gives Aura components and Lightning Web Components programmatic control over the workspace. The API can open a workspace tab or subtab, focus a specific tab, read details about the focused tab, set a tab label or icon, refresh a tab, and close a tab. There are also methods for driving the utility bar, such as opening or minimizing a utility. This matters when you want screen pops or automation, for example opening the right record as a new tab the moment a call arrives, or relabeling a tab so an agent can tell two open cases apart at a glance. The console API has supported many classic Console Integration Toolkit methods since API version 42.0, which eased migrations from older Classic consoles. Most teams start with point-and-click configuration and add JavaScript only where the workflow genuinely needs it.
Setup requirements and feature parity notes
To use a console app, a user needs the Lightning Console User permission, and their profile or permission set has to be assigned to that specific app. Console apps are available in Professional, Enterprise, Performance, Unlimited, and Developer editions, though some related features carry their own licensing. The fastest way to get started is to enable one of the standard apps, Service Console or Sales Console, rather than building from scratch, because they come pre-wired with sensible pages and utilities. One thing to plan for is that Lightning console apps do not yet have full parity with the older Salesforce Classic console. Several Classic-era capabilities are limited or handled differently in Lightning, including resizable split view width, certain keyboard shortcut overrides, interaction logs, push notifications, multi-monitor pop-out workspaces, and tab preview on hover. None of these block normal use, but they can surprise teams migrating from a long-tuned Classic console who expect every old behavior to carry over. Before a migration, it is worth listing the Classic features your agents rely on daily and checking each one against the current Lightning console feature set.
Build a Lightning console app in the App Manager
You create a console by building a Lightning app and setting its navigation type to Console, then adding the objects, pages, and utilities your team needs. Here is the click path in the App Manager. If you only need a starting point, enabling the standard Service Console or Sales Console app is faster than building one by hand.
- Open the App Manager
In Setup, go to Apps, then App Manager. Click New Lightning App to start a fresh app, or click the dropdown next to an existing Lightning app and choose Edit to convert or adjust it.
- Set navigation type to Console
On the App Options step, choose Console as the navigation style instead of Standard. This is what turns on workspace tabs, subtabs, and the split view behavior for the app.
- Add navigation items and configure split view
Add the objects and tabs users should see, then decide how lists behave, including whether split view is available so agents can work a list beside the open record.
- Build the utility bar
On the Utility Items step, add the Lightning components users need in the footer, such as Notes, History, a softphone, or Omni-Channel, and set each item label, icon, and properties.
- Assign the app and save
On the User Profiles step, add the profiles that should use the console, save the app, and confirm those users have the Lightning Console User permission.
Set to Console to enable the tabbed multi-record workspace; Standard shows one record at a time.
Lightning components shown in the fixed footer; some run as background utilities with no panel.
A left-side list panel paired with the open record, on by default and collapsible for more space.
Service Console and Sales Console are prebuilt; enable one for a fast, supported starting point.
- Users without the Lightning Console User permission cannot open the app even if the app is assigned to their profile.
- Console apps are dense and best for trained, high-volume teams; casual users are often better served by a standard navigation app.
- Lightning console apps lack full parity with Classic console apps, so confirm features like push notifications and pop-out workspaces before a migration.
- Split view needs horizontal room and feels cramped on small laptop screens, so weigh screen size when you decide who gets a console.
Trust & references
Cross-checked against the following references.
Straight from the source - Salesforce's reference material on Salesforce Console.
Hands-on resources to go deeper on Salesforce Console.
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 Salesforce Console?
Q2. How does it differ from standard navigation?
Q3. What features support efficiency?
Discussion
Loading discussion…