First-Generation Managed Packaging Developer Guide

First-Generation Managed Packages
Why Switch to Second-Generation Managed Packaging?
Move to 2GP: Migrate Your Managed Packages with Ease
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
Lead and License Records in the License Management App
Modify a License Record
Refresh Licenses for a Managed Package
Extending the License Management App
Package and Package Version Object Fields
License Object Fields
Adding Custom Automation to License Management App Objects
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

Newer Version Available

This content describes an older version of this product. View Latest

License Object Fields

Use the License custom object to set limits on how many users in the subscriber’s org can use your app and for how long.

The License Management App (LMA) creates a license record every time your package is installed in an org. For example, if a subscriber installs two of your 1GP packages and three of your 2GP packages, you have five license records for that subscriber in your LMA. If you deliver a 2GP app that is composed of multiple packages, a unique license record is created for each package in the app. You can allocate up to 99,000,000 seats per subscriber license.

To view details about a license record, select the Licenses tab in the LMA, and then select and open the license record.

License records are automatically created and contain critical information for tracking licenses. Do not directly edit the license record. Instead, use the Modify License tool to change the expiration date, license status, and the number of licensed seats.

License Custom Object Fields Description
Account A lookup field to the account record for a converted lead.
Contact A lookup field to the contact record for a converted lead.
Created By License records are always created by the LMA.
Expiration Date Displays the expiration date or Does not expire (default).
Install Date The date the subscriber installed this package version.
Instance The Salesforce instance where the subscriber’s org resides.
Lead The lead record that the LMA created when the package was installed. A lead represents the user who owns the license.

If you convert the lead into an opportunity, the lead name is retained but the lead record no longer exists.
License Name An auto-generated number that represents an instance of a license. License names are in the format of L-00001, and each new license is incremented by one.
Licensed Seats Displays the number of licenses or Site License (default). When a package is installed in a sandbox org, Site License is the default. If a free trial package is installed in a sandbox org, the Site License is applied.
License Status The type of license: Active, Suspended, Trial, or Uninstalled.
License Type This is a legacy field and can be ignored.
Org Edition The edition of the subscriber’s org.
Org Expiration Date Applies only if the subscriber installs your package in a trial org. Indicates the date when the trial org expires. It isn’t related to the package license expiration.
Org Status The status of the subscriber’s org: Active, Free, or Trial.
Owner The LMA owns all license records. Don’t edit this field.
Package Version A lookup field that links to the package version associated with this license.
Package Version Number The version number in major.minor.patch format. For example, 3.1.0.
Sandbox Indicates whether the license is for a package installed in a sandbox org.
Subscriber Org ID The 15-character ID representing the subscriber’s org.
Used Licenses Displays the number of users who have a license to the package.

This field is blank if:

  • A customer uninstalled the package.
  • Licensed Seats is set to Site License.