App
An App in Salesforce is a configurable bundle of tabs, navigation, branding, and Lightning components that gives a specific user role its working surface.
Definition
An App in Salesforce is a configurable bundle of tabs, navigation, branding, and Lightning components that gives a specific user role its working surface. Sales reps land in the Sales app with Accounts, Contacts, Opportunities, and Leads in the top navigation. Service agents land in the Service Console app with Cases and Knowledge in front of them. The same org may have dozens of Apps, each scoped to one team or workflow. Lightning Apps are configured in Setup, App Manager, and assigned to profiles or permission sets, so the right user sees the right surface on login.
The word App carries several related meanings inside Salesforce, distinct from but adjacent to Lightning Apps. Connected Apps are OAuth client registrations for external integrations. AppExchange Apps are managed packages distributed by third-party partners. Mobile Apps are the Salesforce mobile clients (Salesforce Mobile App, Field Service App, partner-built mobile apps). Each surface uses the word App differently. The Lightning App is the most common day-to-day meaning, since every Salesforce user spends their session inside one App at a time.
The kinds of App in Salesforce and how Lightning Apps shape user experience
Lightning Apps and the App Manager
Lightning Apps live in Setup, App Manager. Each App configures a navigation bar (the tabs and items at the top), a utility bar (the action shelf at the bottom), branding (logo, primary colour), and user assignment (which profiles and permission sets can launch it). The App Launcher (the nine-dot icon at the top left) lists every App the running user can access; switching Apps changes the navigation and utility surfaces in one click.
Standard Apps and Console Apps
Lightning Apps come in two navigation styles. Standard Apps use a single-tab navigation pattern; opening a record replaces the current view. Console Apps support multi-tab workspaces, where each opened record becomes its own primary tab and related records open as sub-tabs. Service Console and Sales Console are the canonical Console Apps. Console apps drive service teams' high-density workflows; standard apps fit most other roles.
Utility Bar and the action shelf
Every Lightning App can include a Utility Bar at the bottom of the window. The bar holds always-accessible utility items: Omni-Channel for service agents, Open CTI for sales callers, History for record navigation, Macros for canned actions. The Utility Bar is per-App, so service agents see different utilities than sales reps even when both are in the same browser session.
App assignment via profile and permission set
Apps are assigned through profile or permission set. Each profile has an App Settings section listing every Lightning App, with Visible and Default toggles. Visible means the user can see the App in App Launcher; Default decides which App opens on login. Most production orgs use permission sets to grant App visibility so the assignment scales without profile sprawl.
Connected Apps for OAuth
Connected Apps are a separate concept under the same word. They register an external system (a mobile app, a data integration, a marketing tool) so users can authenticate with Salesforce credentials via OAuth. Each Connected App has a Client ID, Client Secret, OAuth scopes, and IP restrictions. The surface is Setup, App Manager, Connected Apps. Connected Apps and Lightning Apps share a tab in App Manager but solve different problems.
AppExchange managed packages
The word App also refers to AppExchange managed packages: third-party extensions distributed through the AppExchange marketplace. An installed AppExchange App lives in the org as a managed namespace with its own objects, fields, classes, and pages. AppExchange Apps may include Lightning Apps inside the package; that overlap is where the terminology gets confusing for new admins.
Mobile Apps
The Salesforce Mobile App is the mobile client every Salesforce user can install. It surfaces the same data and a subset of the desktop Lightning Apps. Custom mobile apps built on the Mobile SDK or as Lightning Web Runtime apps also count as Salesforce apps. The mobile and desktop surfaces share data and metadata but render UI differently per device.
Designing an effective Lightning App
Three design moves matter most. Curate the navigation tightly; ten well-chosen tabs beat thirty kitchen-sink ones. Use the Utility Bar for actions users perform constantly, not occasionally. Set the Default App per role so login lands users in the right surface without an extra click. Most Salesforce productivity wins come from these three decisions; everything else is incremental tuning.
How to create a Lightning App
Building a Lightning App takes a 10-minute wizard. The longer work is curating the navigation and utility surfaces for the role that will use it.
- Open App Manager
Setup, App Manager. Click New Lightning App.
- Name and brand the App
Provide a Name and Developer Name. Upload a logo and pick a primary colour to brand the navigation bar so users can identify the App at a glance.
- Pick Standard or Console navigation
Standard for most apps; Console for service workflows that need multi-tab workspaces.
- Add tabs and utility items
Drag tabs into the navigation bar in the order the user will use them. Add utility items like Omni-Channel, History, or Macros to the Utility Bar.
- Assign to profiles or permission sets
On the final wizard step, choose which profiles or permission sets can see the App. Set the Default App for the right roles. Save.
Human-readable label shown in the App Launcher.
API-safe identifier used in metadata and permission set assignment.
Standard or Console; cannot be changed after the App is created.
Tabs and items that appear in the navigation bar.
Profiles or permission sets that grant access to the App.
- Navigation style (Standard vs Console) cannot be changed after creation. Pick the right one up front.
- Profile-only assignment scales poorly. Use permission sets to grant App visibility instead.
- Utility Bar items are configured per App, not per profile. Two Apps that share users may need duplicate Utility configurations.
- Default App is per profile. Setting it on the App alone does not make it the default until profile defaults are also configured.
Trust & references
Cross-checked against the following references.
- Create a Lightning AppSalesforce Help
- Connected Apps OverviewSalesforce Help
Straight from the source - Salesforce's reference material on App.
- App ManagerSalesforce 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 does a Salesforce App bundle together?
Q2. How do users switch between apps?
Q3. Does an App change a user's underlying permissions?
Discussion
Loading discussion…