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
Request Login Access from Subscribers
Log In to Subscriber Orgs
Debug Subscriber Orgs
Manage Features in First-Generation Managed Packages
AgentExchange App Analytics for First-Generation Managed Packages
Developing and Distributing Unmanaged Packages
PDF

Note: This release is in preview. Features described here don’t become generally available until the latest general availability date that Salesforce announces for this release. Before then, and where features are noted as beta, pilot, or developer preview, we can’t guarantee general availability within any particular time frame or at all. Make your purchase decisions only on the basis of generally available products and features.

Request Login Access from Subscribers

To log in to a subscriber org, first request login access from the subscriber.

Ask the subscriber to enable either Grant Account Login Access or Grant Login Access. If they don’t see your company listed, one of the following applies.

  • A system admin disabled the ability for non-admins to grant access.
  • The user doesn’t have a license for the package.
  • The package is licensed to the entire org. In this scenario, only an admin with the Manage Users permission can grant access.
  • The org setting Administrators Can Log in as Any User is enabled.

When the org setting Administrators Can Log in as Any User is disabled, login access is granted for a limited amount of time, and the subscriber can revoke access at any time.

Note

Any changes you make while logged in as a subscriber are logged in the subscriber org’s audit trail.