License Management Application (LMA)
The License Management Application (LMA) is the Salesforce-supplied managed package that AppExchange partners install in their License Management Organization to track every customer install of their managed packages.
Definition
The License Management Application (LMA) is the Salesforce-supplied managed package that AppExchange partners install in their License Management Organization to track every customer install of their managed packages. The LMA exposes standard objects (License, Package, Package Version, Subscriber) that record each customer''s subscription details, license count, expiration date, and contact information. When a customer installs the partner''s managed package from the AppExchange, Salesforce automatically creates a License record in the partner''s LMA-enabled org and populates it with the install details.
The LMA is the foundation of the AppExchange partner business model. It lets ISVs (Independent Software Vendors) provision licenses, expire licenses on contract end, identify the subscriber org for support engagement, monitor adoption, and run partner-side reporting on the install base. Without the LMA, a partner would have no programmatic visibility into their AppExchange customers. The application is free to install for any Salesforce Partner Community member with a managed-package offering; the related License Management Organization (LMO) is the org where the LMA lives.
How the LMA tracks every subscriber org and license
Standard objects in the LMA
The LMA introduces License, Package, Package Version, and Subscriber as standard objects in the partner''s LMO. License is the per-install record: who installed what package, when, with how many seats, expiring when. Package is the partner''s managed package definition. Package Version tracks each release of the package. Subscriber is the customer org with contact details.
Auto-provisioning on install
When a customer installs the partner''s package from the AppExchange, Salesforce creates a License record in the partner''s LMO automatically. The record includes the subscriber org ID, the package version, the seat count (default 1; Active or Free trial seats vary), the install date, and the expiration date. The partner receives the new License via standard Salesforce automation in their LMO.
License lifecycle management
Partners manage licenses through the lifecycle: trial, active subscription, renewal, expiration, suspension. Editing the License record changes the customer''s access to the package. Setting Status to Suspended blocks the customer from using the package; setting Expiration Date to a past date does the same. The License record is the partner''s single control point.
Seat-based provisioning
Some managed packages license per-seat, with the partner enabling specific Salesforce Users in the customer''s org. The License record tracks the seat count; the customer org has its own per-user permission set assignment that respects the count. Going over the seat count produces an error in the customer org until either more seats are purchased or unused users are disabled.
Subscriber Support Console
The LMA includes a Subscriber Support Console that lets partner support engineers log in to subscriber orgs (with the subscriber''s permission) to investigate issues. The Login Access feature, granted by the subscriber via Setup, allows partner support to assume the subscriber user''s identity for diagnostic purposes. The combination is essential for any non-trivial AppExchange package support program.
Reporting on the install base
Partners build reports and dashboards on License, Subscriber, and related custom objects. Common metrics: total seats sold, total active subscribers, renewal rate, churn by customer segment, average seats per customer, install velocity. These dashboards drive the AppExchange business; without them, the partner has no programmatic insight into their own business.
Integration with billing systems
Most partners integrate their LMA with their billing system (Stripe, NetSuite, custom) so a License modification (new install, renewal, expiration) syncs to the billing record. The integration runs via Apex on the License object or via a third-party iPaaS. Partners with significant AppExchange revenue treat this integration as critical infrastructure.
Install and configure the LMA in your LMO
Every AppExchange partner needs the LMA. Installation is a one-time setup; ongoing operation is the daily work of managing the install base.
- Pick the License Management Organization
Designate which Salesforce org will be the LMO. Most partners use their primary internal Salesforce org; some create a dedicated partner org for separation.
- Install the LMA
Salesforce Partner Community provides the LMA install link. Install into the LMO. The package adds License, Package, and Subscriber objects.
- Link your managed package to the LMA
From the Salesforce Partner Console, link each AppExchange managed package to the LMA so Salesforce creates License records on customer installs.
- Configure license provisioning rules
Decide default seat counts, expiration policies, trial durations. The LMA supports flexible defaults that automate the most common scenarios.
- Build the install-base dashboard
Surface key metrics: active subscribers, total seats, renewal pipeline, churn. Pin the dashboard to the executive team''s home view.
- Integrate with billing
Wire License changes to the partner''s billing system. The integration drives accurate invoicing and revenue recognition.
- The LMO designation is permanent. Picking the wrong org as LMO is hard to undo; pick carefully at partner-program registration time.
- License records are created automatically; deleting them removes the customer''s access to the package. Treat License deletion as a serious action.
- Subscriber Support Console access requires customer consent. Partners cannot log into subscriber orgs without the customer granting Login Access.
- The LMA is a managed package itself. Updates ship periodically; partners should stay current to access new license-management features.
Trust & references
Cross-checked against the following references.
- License Management ApplicationSalesforce Help
- Salesforce Partner CommunitySalesforce
Straight from the source - Salesforce's reference material on License Management Application (LMA).
- LMA Developer GuideSalesforce Developers
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 the License Management Application?
Q2. Where is the LMA installed?
Q3. Why is the LMA essential for ISVs?
Discussion
Loading discussion…