Enable Dev Hub and Second-Generation Managed Packaging

After you enable the Dev Hub setting on a Salesforce org, that Dev Hub becomes the owner of every managed 2GP package you create. All Salesforce ISV and OEM partners should designate their Partner Business Org (PBO) as their Dev Hub org.

To enable Dev Hub:

1. Log in to your Partner Business Org.
2. From Setup, enter Dev Hub in the Quick Find box and select Dev Hub. If you don't see Dev Hub in the Setup menu, make sure that your org is one of the supported editions.
3. Select Enable Dev Hub. After you enable Dev Hub, you can’t disable it.
4. Select Enable Unlocked Packages and Second-Generation Managed Packages. After you enable this setting, you can’t disable it.

If you choose to use a trial or Developer Edition org as your Dev Hub, consider these factors.

• You’re limited to creating up to six scratch orgs and package versions per day, with a maximum of three active scratch orgs.
• Trial orgs expire on their expiration date.
• Developer Edition orgs can expire due to inactivity.
• If a package is associated with a non-production Dev Hub org, and that org expires or becomes inactive, the installed package can't be updated, and new attempts to install the package may fail.
• If you plan to create package versions or run continuous integration jobs, it’s better to use your PBO as your Dev Hub because of higher scratch org and package version limits. Package versions are associated with your Dev Hub org. When a trial or Developer Edition org expires, you lose access to the package versions.

The Dev Hub org instance determines where scratch orgs are created.

• Scratch orgs created from a Dev Hub org in Government Cloud are created on a Government Cloud instance.
• Scratch orgs created from a Dev Hub org in Public Cloud are created on a Public Cloud instance.