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.

Know Your Orgs for Second-Generation Managed Packages

Some of the orgs that you use with second-generation managed packaging (managed 2GP) have a unique purpose.

Choose Your Dev Hub Org

Use the Dev Hub org for these purposes.

As owner of all second-generation managed packages
To link your namespaces
To authorize and run your sf package Salesforce CLI commands

We recommend that your Partner Business Org is also your Dev Hub org. For important considerations about your Dev Hub org, see Enable Dev Hub and Second-Generation Managed Packaging.

The Dev Hub org against which you run the sf package create command becomes the owner of the package.

If the Dev Hub org expires or is deleted, packages owned by that Dev Hub:

Can’t be transferred to a different Dev Hub
Stop working and new package versions can’t be created

Note

Namespace Org

The primary purpose of the namespace org is to acquire a namespace for your managed 2GP package.

After you create a namespace org and specify the namespace in it, open the Dev Hub org and link the namespace org to the Dev Hub org.

Other Orgs

When you work with managed 2GP packages, you also use these orgs:

Scratch orgs to develop and test your packages.
A target or installation org in which you install the package.

Second-Generation Managed Packaging Developer Guide

Know Your Orgs for Second-Generation Managed Packages

Choose Your Dev Hub Org

Namespace Org

Other Orgs

See Also