First-Generation Managed Packaging Developer Guide

First-Generation Managed Packages
Why Switch to Second-Generation Managed Packaging?
Environment Hub
Get Started with the Environment Hub
Manage Orgs in the Environment Hub
Single Sign-on in the Environment Hub
Environment Hub Best Practices
Environment Hub FAQ
Can I use the Environment Hub in Lightning Experience?
Where do I install the Environment Hub?
Can I install the Environment Hub in more than one org?
Can I enable the Environment Hub in a sandbox org?
What kinds of orgs can I create in the Environment Hub?
How is locale determined for the orgs I create in the Environment Hub?
Are the orgs that I create in the Environment Hub the same as the ones I created in the Partner Portal?
Can an org be a member of multiple Environment Hubs?
Can I disable the Environment Hub?
Considerations for the Environment Hub in Lightning Experience
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
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
Manage Features in First-Generation Managed Packages
AppExchange App Analytics for First-Generation Managed Packages
Developing and Distributing Unmanaged Packages
PDF

Newer Version Available

This content describes an older version of this product. View Latest

Can I enable the Environment Hub in a sandbox org?

No, you can’t enable the Environment Hub in a sandbox org. Enable the Environment Hub in a production org that all your users can access.