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.