Second-Generation Managed Packaging Developer Guide

Second-Generation Managed Packages
What’s a Second-Generation Managed Package?
Set Up Your Development Environment
Before You Create Second-Generation Managed Packages
Scratch Orgs and Package Development
Workflow for Second-Generation Managed Packages
Components Available in Second-Generation Managed Packages
Editable Properties After Package Promotion or Installation
Behavior of Specific Metadata in Second-Generation Managed Packages
Develop Second-Generation Managed Packages
Install and Uninstall Second-Generation Managed Packages
Prepare to Distribute Your Second-Generation Managed Package
Push a Package Upgrade for Second-Generation Managed Packages
Advanced Features for Second-Generation Managed Packages
Best Practices for Second-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
Assign Permissions to the Subscriber Support Console
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 Second-Generation Managed Packages
Get Started with AgentExchange App Analytics
Gaps Between First-Generation and Second-Generation Managed Packaging
PDF

Configure Permissions for the License Management App

Determine who needs access to the License Management App (LMA), and set object permissions. Consider using a permission set to assign user permissions.

Ensure that you:

  • Install the LMA.
  • Connect your packaging org (for 1GP) or your Dev Hub org (for 2GP) to the AgentExchange Partner Console.
  • Associate your package with the LMA.
  1. Set object permissions for the license, package, and package version custom objects.
    Custom Object Object Permissions
    License To view license records, assign READ permissions. To modify license records, assign READ and EDIT permissions.
    Package To view package records, assign READ permissions. To modify package records, assign READ and EDIT permissions.
    Package Version To view package version records, assign READ permissions. We recommend leaving all package version records as read-only.
  2. Set field-level security in user profiles or permission sets.
    Custom Object Field-Level Permissions
    License Make all fields read-only.
    Package Make all fields read-only.
    Package Version Make all fields read-only.
  3. Add related lists to page layouts.
    To enable... Add the Licenses related list to the...
    License managers to view the licenses associated with a particular lead Lead page layout
    LMA users to view the licenses associated with a particular account Account page layout
    LMA users to view the licenses associated with a particular contact Contact page layout