Setting up the LMA is a one-time configuration in your License Management Org. You install the app, connect it to the Salesforce Partner Console, and associate your managed package so future installs generate Lead and License records automatically. Do this once per partner program, before you start distributing the package widely.
- Request and install the LMA
From the Salesforce Partner Console, request the License Management App, then install the managed package into the org you want to use as your LMO, usually your business org. Confirm the Package, Package Version, and License objects appear after install.
- Connect your LMO to the Partner Console
In the Partner Console, connect the org where you installed the LMA as your License Management Org. This link is what tells Salesforce where to write License and Lead records when customers install your package.
- Associate your managed package
Associate the specific managed package with your connected LMO. Until a package is associated, installs of it will not generate License records, so verify the association shows your package by name.
- Set default licensing terms
Set the default Seats, license type, and trial length that new installs should receive. These defaults drive the License record created on each future install, so choose values that match your standard offer.
- Verify with a test install
Install the package into a separate test org and confirm a Lead and a License record appear in the LMO with the expected Seats, Status, and Expiration. Fix the defaults if the test record looks wrong before you go live.
The org where the LMA is installed and where License and Lead records are written. Pick it deliberately, since the choice is effectively permanent.
The seat count new License records receive on install. Can be a fixed number up to 99,000,000 or a Site License covering all users in the subscriber org.
Whether new installs start as a trial or a paid license, and for trials, how many days (up to 90) before access ends.
The managed package linked to the LMO. Only installs of an associated package generate License records.
- The LMO choice is effectively permanent; moving the LMA to a different org after the fact is painful, so pick the right org up front.
- Changing default licensing only affects future installs. Existing License records keep their original terms until you edit them.
- Setting Status to Suspended or backdating Expiration immediately blocks the customer from using your package, so double-check before saving on a paying account.
- A package that is not associated with the LMO will not generate License records, even though the LMA is installed.