Lightning Out 2.0 App Manager
Lightning Out 2.0 App Manager is the Setup interface where admins configure Lightning Out applications, the framework that lets Lightning Components run inside non-Salesforce hosts: external websit…
Definition
Lightning Out 2.0 App Manager is the Setup interface where admins configure Lightning Out applications, the framework that lets Lightning Components run inside non-Salesforce hosts: external websites, Visualforce pages, custom mobile apps, and Heroku apps. Lightning Out delivers a self-contained bundle that includes the requested Lightning Components, the underlying dependencies, and the JavaScript needed to render them, all served from the Salesforce-supplied lightning.force.com endpoint. The 2.0 version represents the modernized framework that supports Lightning Web Components alongside the original Aura Components.
The App Manager in Setup, under App Manager, lets admins create the Lightning Application records that define which components are exposed via Lightning Out. Each Lightning Application bundles a set of components into a deployable unit; external pages reference the application URL to embed the Salesforce experience. Common use cases include embedding a Salesforce-driven order-status component into a public website, surfacing a Salesforce dashboard inside a Visualforce email digest, or running Salesforce-aware Lightning Components inside a Heroku-hosted application.
How Lightning Out 2.0 lets Salesforce components run outside Salesforce
The Lightning Out concept
Lightning Out is the framework that lets Lightning Components run in any web context that can include JavaScript. The external host (Visualforce page, custom site, Heroku app) embeds a script tag pointing to the Lightning Out endpoint, plus a $Lightning.use() call that loads the components. The Salesforce server delivers the bundle; the components render in the host''s DOM with access to Salesforce data via standard APIs.
Lightning Application records as the unit
The unit of deployment is a Lightning Application: an Aura application or LWC application that declares which components are exposed. The App Manager in Setup lets admins create new applications, configure their dependencies, and surface the embed URL to external developers. Each app is referenced by its API name from the external host code.
Authentication for Lightning Out
Components running via Lightning Out still need to authenticate against Salesforce to access data. Two common patterns: implicit authentication via the host''s existing Salesforce session (Visualforce, Lightning Experience), or explicit OAuth flows for external hosts. The latter requires Connected App configuration.
Lightning Web Components support
Lightning Out 2.0 supports LWC alongside Aura Components. Modern deployments use LWC for new components; the App Manager lets admins surface both. The framework handles the difference under the covers, but external integrators should default to LWC for new builds.
Common use cases
Three patterns dominate. Embedding a Salesforce-aware quote-status component on a public marketing site. Surfacing a Lightning record summary inside a Visualforce email digest. Running Lightning Components inside a Heroku app that already has its own UI but wants to add Salesforce-aware screens.
Salesforce Sites and Experience Cloud comparison
Lightning Out and Experience Cloud both let Lightning Components run outside the standard Salesforce UI. The difference: Experience Cloud is a full-blown community platform with its own authentication, navigation, and styling; Lightning Out is a lightweight embed framework for dropping individual components into existing external pages. Pick Lightning Out for small embeds; pick Experience Cloud for full sites.
Deprecation considerations
Lightning Out is not deprecated, but Salesforce''s strategic direction has moved many use cases toward Experience Cloud or toward Heroku Connect for richer integrations. Lightning Out continues to ship and is supported, but new design conversations should evaluate Experience Cloud as an alternative.
Create a Lightning Out application in the App Manager
Setting up a Lightning Out app is a Setup-side task; the external integration code is the harder part.
- Open App Manager
Setup, App Manager. The list shows existing Lightning and Connected Apps.
- Create a new Lightning Application
Click New Lightning App. Pick the standard Lightning App template. Name and configure the App.
- Add the target Lightning Components
Drop the LWCs or Aura Components that should be exposed via Lightning Out into the App''s configuration.
- Configure access permissions
Set which profiles or permission sets can use the components. Default to least-privilege.
- Build the external integration
On the external host, add the Lightning Out script tag and $Lightning.use() initialization. Pass the app API name and the target DOM element.
- Test the embed end-to-end
Verify the component renders, authenticates, and pulls data correctly from the external context.
The App Manager record that defines the bundle.
The LWCs or Aura Components included.
The script tag and JavaScript initialization on the external page.
Implicit (Visualforce) or explicit OAuth (external).
- Lightning Out components have to coexist with the host page CSS. Style conflicts are common; SLDS classes can be overridden by host styles.
- External hosts need to handle the Lightning Out load time. Components add 100-500ms to first paint on the external page; budget accordingly.
- Authentication can be tricky for fully external hosts. Plan the OAuth flow alongside the component design.
- Lightning Out is supported but not the strategic direction for many use cases. Evaluate Experience Cloud before committing.
Trust & references
Cross-checked against the following references.
- Lightning Out Developer GuideSalesforce Developers
- 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 is a Governor Limit in the context of Lightning Out 2.0 App Manager?
Q2. What skill set is typically needed to work with Lightning Out 2.0 App Manager?
Q3. Where would a developer typically work with Lightning Out 2.0 App Manager?
Discussion
Loading discussion…