LMO setup happens once. Get it right at partner-program registration; fixing it later is painful.
- Pick the right org
Permanent, paid org with stable infrastructure. Most often the partner''s primary internal Salesforce org. Never a Developer Edition or trial.
- Register through Partner Console
Salesforce Partner Community, Partner Console, designate the org as the LMO during managed-package registration.
- Install the LMA
Once designated, install the License Management Application managed package into the LMO. License and Subscriber objects appear.
- Configure user permissions
Grant License and Subscriber access to partner ops, customer success, and support roles. Restrict broader access by default.
- Build dashboards and integrations
Surface install-base metrics. Integrate with billing for revenue recognition. Wire support workflows for subscriber engagement.
- Document the org as the LMO
Mark the org clearly so future admins do not accidentally retire it or treat it as a sandbox.
- LMO designation is effectively permanent. Pick a stable, paid, long-lived org; never a Developer Edition or trial.
- Switching LMOs later requires Partner Support intervention and produces a bifurcated install base during the transition.
- Default sharing on License records is permissive. Review and restrict for sensitive customer information.
- The LMO''s storage and API limits apply to License operations. High-volume partners may hit limits if the org also hosts heavy internal CRM data.