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
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

Refresh Licenses for a Managed Package

To sync all license records for a package across all subscriber installations, you refresh the license. Refreshing the license can also resolve discrepancies between the number of licenses in a subscriber’s org and the number displayed in the License Management App (LMA). Refreshing is required when you move the LMA to a different org.

For each package, you can refresh licenses only one time per week.

Note

  1. From the LMA, select the Packages tab.
  2. Open the package record.
  3. Click Refresh Licenses. In Lightning Experience, Refresh Licenses is located in the dropdown menu.