Skip to content
Salesforce Dictionary - Free Salesforce GlossarySalesforce Dictionary
Full License Management Organization (LMO) entry
How-to guide

Setting up your License Management Org

Most partners get an LMO automatically: finish standard signup, and your Partner Business Org arrives with the License Management App installed. The steps below cover confirming the LMA, getting it into a non-PBO org if you need to, and pointing a package at the LMO so installs report back.

By Dipojjal Chakrabarti · Founder & Editor, Salesforce DictionaryLast updated Jun 16, 2026

Most partners get an LMO automatically: finish standard signup, and your Partner Business Org arrives with the License Management App installed. The steps below cover confirming the LMA, getting it into a non-PBO org if you need to, and pointing a package at the LMO so installs report back.

  1. Confirm the LMA in your PBO

    Open the App Launcher in your Partner Business Org and search for License Management. If the app appears, your PBO is already your LMO and you can start managing licenses. Standard signup installs it for you.

  2. Request the LMA for a non-PBO org

    If you want the LMA in a different org, log in to the Salesforce Partner Community, open AppExchange Support, and log a case with Salesforce Partner Program Support. A signed partner agreement is required before you can request it.

  3. Associate the package with the LMO

    In your publishing flow, set the License Manager for the managed package. This links every future install of that package to your LMO so a License record is created on each install.

  4. Verify and automate

    Install your package into a test subscriber org and confirm a Lead and License record appear in the LMO. Then add triggers, reports, or Feature Management parameters to act on the data.

License Manager (package setting)remember

The setting that ties a managed package to its LMO. Set it during publishing so installs route License records to the correct org.

Partner Business Org (PBO)remember

The production org from standard signup that ships with the LMA preinstalled. For most partners the PBO and the LMO are the same org.

License statusremember

Trial (up to 90 days), Active, Suspended, or Uninstalled. Set it on each License record to govern a customer org's access to your package.

Feature parametersremember

Boolean, Integer, or Date values managed via the Feature Management App to toggle features in subscriber orgs from the LMO.

Gotchas
  • Never use a Developer Edition or trial org as your LMO. When it expires, the LMA and your entire license history become unreachable.
  • To assign a license to a customer, that Account must exist in the same org as the LMA. This is why Salesforce recommends keeping the LMA in your PBO.
  • Uninstalled is terminal. Once a customer uninstalls and the license flips to Uninstalled, you cannot edit that license record anymore.
  • Feature parameters accept only Boolean, Integer, and Date. They travel between orgs, so Salesforce blocks free text to keep personal data out.

See the full License Management Organization (LMO) entry

License Management Organization (LMO) includes the definition, worked example, deep dive, related terms, and a quiz.