Console Settings
Console Settings is the org-wide Setup area that controls global behavior of the Lightning Service Console and related console-style apps: keyboard shortcuts, tab behavior (reopen tabs on restart, tab limit, sub-tab behavior), push notification preferences, console-wide custom branding, and the enable/disable toggle for specific console features like Macros, Quick Text, and the Recent Items component.
Definition
Console Settings is the org-wide Setup area that controls global behavior of the Lightning Service Console and related console-style apps: keyboard shortcuts, tab behavior (reopen tabs on restart, tab limit, sub-tab behavior), push notification preferences, console-wide custom branding, and the enable/disable toggle for specific console features like Macros, Quick Text, and the Recent Items component. Console Settings sits at the org level; per-app Console Layout configuration sits at the app level. The two work together to produce the agent console experience.
Console Settings exists to centralize org-wide console behavior so admins do not configure the same option on every console app. Enabling Reopen Tabs on Restart, setting the maximum primary tab count, configuring keyboard shortcuts apply org-wide. Per-app variations (which utility bar items appear in this console) live in the Console Layout. Most admins touch Console Settings once at console rollout and revisit only when adding console features that surface here.
Why Console Settings is the org-wide console toggle hub
Where Console Settings lives and what it controls
Setup, Feature Settings, Service, Console Settings or Setup, Lightning Service Console depending on the org edition. The settings cluster: tab behavior (reopen tabs after refresh, default tab pinning, sub-tab nesting depth, tab limit), keyboard shortcuts (Salesforce-defined plus custom assignments), push notifications (case updates, work item assignment), Macros enable/disable, Quick Text enable/disable, console color theme. Each setting applies org-wide; users see the configured behavior in every console app the admin assigns them.
Reopen Tabs on Restart and the agent-session continuity
Reopen Tabs on Restart restores the agent's previously open tabs when they reload the console or sign in fresh. The feature is convenient (agents resume mid-conversation) but also produces stale tabs (cases that were closed yesterday reopen today). Most teams enable Reopen Tabs for high-volume service teams and disable for teams that prefer fresh sessions. The toggle is org-wide; users cannot override personally. Test with the agent team before flipping the toggle in production.
Keyboard shortcuts and the power-user experience
Console Settings ships with default keyboard shortcuts: Ctrl+Shift+N opens a new primary tab, Esc closes the current tab, Ctrl+Shift+L pulls focus to the navigation bar. Admins can edit defaults or add custom shortcuts that fire utility bar actions or open specific record types. Power-user agents who learn the shortcuts work significantly faster; agents who never learn them rely on clicks. The shortcuts surface on the console as a question-mark help icon; encourage agents to open it during onboarding.
Push notifications and the agent attention model
Console Settings configures which events trigger browser push notifications in the console: new case assignment, case ownership change, mention in a Chatter post, Omni-Channel work item arrival, Knowledge article update on subscribed topics. The notifications appear as desktop notifications outside the browser window so agents see them even when the console is in a background tab. The right notification mix depends on workflow; over-notifying produces alarm fatigue, under-notifying produces missed assignments.
Macros, Quick Text, and the productivity toggles
Some console productivity features are toggle-enabled in Console Settings. Macros (the scripted-clicks feature) is enabled here for the org. Quick Text (the canned-response feature) is enabled here. Disabling either at the org level removes the feature from every console app, regardless of per-app Console Layout configuration. The toggles are coarse; finer-grained gating happens through permission sets.
Custom branding and the visual customization
Console Settings includes branding options: custom logo in the console header, custom color theme, custom navigation labels. Most large orgs do not need this; the standard Salesforce branding works. Service Cloud OEM resellers and partner-facing portals sometimes need custom branding to match their visual identity. The customization is limited compared to standalone web apps; Console Settings handles the easy cases and falls short of full white-labeling.
Maintenance, audit, and the relationship to Console Layout
Console Settings is org-wide; Console Layout is per-app. Changes here affect every console app simultaneously. Quarterly audit: confirm Reopen Tabs setting matches current team practice, confirm push notifications match current alert workflow, confirm enabled features (Macros, Quick Text) are still in use. The audit cadence pairs naturally with the Account Settings, Activity Settings, Calendar Settings quarterly review; bundle them together for one ops review session.
How to tune Console Settings for agent productivity
The pattern: configure org-wide defaults that match the common agent workflow, layer per-app Console Layout variations on top, audit quarterly. The cost is low; the agent-productivity gain compounds across thousands of console sessions.
- Open Console Settings in sandbox
Setup, Feature Settings, Service, Console Settings. Document current state. Sandbox lets you test changes against the agent team before production.
- Decide on Reopen Tabs on Restart
Enable for high-volume service teams that benefit from session continuity. Disable for teams that prefer fresh sessions. Test with agents before flipping.
- Configure push notifications for critical events
New case assignment, work item arrival, escalations. Avoid over-notifying; alarm fatigue undermines the value.
- Confirm Macros and Quick Text enablement matches workflow
Both ship enabled by default. Disabling cleans up agents who do not use them; leaving on is harmless if no one uses them.
- Promote keyboard shortcuts in agent onboarding
The shortcuts dramatically improve power-user speed but require learning. Include in onboarding training; agents who learn them in week one use them for years.
- Push from sandbox to production through normal pipeline
Change sets, source-tracked sandboxes, DevOps Center. Treat Console Settings as production config.
- Schedule the quarterly Console Settings audit
Bundle with Account, Activity, Calendar settings audits for a single ops review session per quarter.
Session continuity vs fresh session preference. Org-wide toggle.
Maximum primary tabs an agent can have open. Default is generous; tighten for performance-sensitive orgs.
Which events trigger desktop notifications in the console.
Productivity feature toggles. Default on; disable if unused.
Default plus custom shortcut assignments. Power-user productivity feature.
- Console Settings is org-wide. Per-app variation lives in Console Layout, not here.
- Reopen Tabs on Restart can surface stale closed cases. Test with the agent team before enabling in production.
- Push notifications can produce alarm fatigue if over-configured. Subscribe agents to only the critical events.
- Disabling Macros or Quick Text removes the feature from every console app, regardless of per-app Console Layout.
- Custom branding is limited compared to standalone web apps. Console is not a full white-label surface.
Trust & references
Cross-checked against the following references.
- Console referenceSalesforce
- Service Cloud overviewSalesforce
Straight from the source - Salesforce's reference material on Console Settings.
- Lightning Console AppsSalesforce Help
- Set Up Lightning Console AppsSalesforce Help
- Console Keyboard ShortcutsSalesforce 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. Can a Salesforce admin configure Console Settings without writing code?
Q2. What is the primary benefit of Console Settings for Salesforce administrators?
Q3. In which area of Salesforce would you typically find Console Settings?
Discussion
Loading discussion…