First-Generation Managed Packaging Developer Guide

Clouds with binary code floating aboveCloud with binary code floating above

No Results

Search Tips:

  • Please consider misspellings
  • Try different search keywords
First-Generation Managed Packages
Why Switch to Second-Generation Managed Packaging?
Register a Namespace for a First-Generation Managed Package
Create a First-Generation Managed Package Using a UI
Create a First-Generation Managed Package using Salesforce DX
Components Available in First-Generation Managed Packages
Behavior of Specific Metadata in First-Generation Managed Packages
Package and Test Your First-Generation Managed Package
Update Your First-Generation Managed Package
Publish Upgrades to First-Generation Managed Packages
Manage Licenses for Managed Packages
Get Started with the License Management App
Install the License Management App
Associate a Package with the License Management App
Configure Permissions for the License Management App
Lead and License Records in the License Management App
Modify a License Record
Refresh Licenses for a Managed Package
Extending the License Management App
Move the License Management App to Another Salesforce Org
Troubleshoot the License Management App
Best Practices for the License Management App
Troubleshoot Subscriber Issues
Manage Features in First-Generation Managed Packages
AppExchange App Analytics for First-Generation Managed Packages
Developing and Distributing Unmanaged Packages
PDF

Associate a Package with the License Management App

To receive lead and license records for your package, you connect your License Management Org (LMO), your package, and the Salesforce Partner Console. Your LMO is the Salesforce org where the License Management App (LMA) is installed.

User Permissions Needed
To manage licenses in the Partner Community: Manage Listings

A single LMO can manage multiple 1GP and 2GP packages, but a package can be associated with only one LMO.

  1. Connect your packaging org (for 1GP) or your Dev Hub org (for 2GP) to the Partner Console.
    1. Log in to the Partner Community, and select the Publishing tab.
    2. Click Technologies | Orgs.
    3. Click Connect Technology, and then click Org.
    4. Click Connect Org.
    5. Log in to the org. Provide a username and a password with a security token appended. For example, if the password is ABC and the token is 123, enter ABC123. Don’t remember your token? Reset your security token.

      For 1GP packages, enter the login credentials for the packaging org. Repeat this step for all your 1GP packages.

      For 2GP packages, enter the login credentials for the Dev Hub org. When you connect the Dev Hub org, all the 2GP packages owned by the Dev Hub org are linked to the Partner Console.

  2. Select the Solutions tab.
  3. Locate the package you want to register with the LMO. To register each package you own, repeat this step.
    1. Click the down arrow to expand the list of versions for your package.
    2. Click Register Package for the package version you want to register.
      Package versions created after linking to your LMO inherit the association.
    3. To register the package, log in to your LMO.
  4. Set the default behavior you want for your package license, and then click Save.

After the package is registered, a license is created when customers install it. You can view which packages are registered in the LMA.

Beta package versions don’t display in the LMA. Only managed-released package versions (1GP) and promoted package versions (2GP) are visible in the LMA. Unlocked packages aren’t supported.

Note