+ Start a Discussion
Peter ForthPeter Forth 

Do I need Environment Hub enabled to publish to App Exchange?

According to the ISVForce quickstart guide ( https://na1.salesforce.com/help/pdfs/en/salesforce_packaging_guide.pdf
) the first steps to packaging and publishing an app require the use of Environment Hub within your partner account in order to create a dev org, test org and business org.

Our partner account doesn't seem to have Environment Hub enabled.  When we asked to enable it, SalesForce said:

"Environment hub should be enabled in the org where the majority of your users have access, in many cases SFDC recommends the Partner Business Org or your CRM environment. We do not recommend enabling this feature in a test/demo org or a customer trial org.
You can also have this feature enabled in a DE org if you would like to provide your developers with the ability to spin up Test / Developer Edition orgs without access to your main business org. However we cannot enable this in an org that contains a managed package as it may cause issues when pushing an upgrade to your customer or creating new package versions."

I'm confused as to why they say that the hub is attached to a "DE org"... in the pdf it seems more like it attaches to a partner account as a requirement to let them manage multiple orgs.  They also say not to use it for a test/demo org... but the pdf describes using it to create your dev and test orgs.  Are there different object types that they are using the word "org" to reference?

Finally it says that they can't enable the hub on an org that contains a managed package...  the entire reason that I want the hub is that I need to create a managed package and that is what the pdf is telling me to do.

In short the response that we got from Salesforce seems to directly contradict their documentation and I am unsure as to how to proceed to create our managed package for AppExchange distribution.
NagaNaga (Salesforce Developers) 
Hi Peter,

Environment Hub lets partners view, connect, create, and log in to multiple Salesforce organizations from one location. This can be especially convenient if you use a large number of organizations for business, development, and testing.

Generally, you should choose one organization as the Environment Hub (or hub organization), and can then connect all your other organizations (or member organizations) to the hub (note: it is possible to have more than one hub, see the FAQ for details). You can establish single sign-on between the hub and member organizations, enabling users to seamlessly switch between them without having to provide login credentials.  Use the following resources to understand how to set up Environment Hub for your company.

Read this News item on on key questions to keep in mind when spinning up orgs from the Environment Hub. 

Important Note: App Vendors (ISV) should never enable Environment Hub in the DE org that contains a managed package — this could cause issues when you try to upload a new package version or push an upgrade to your customers.


Best Regards
Naga Kiran
Hello Peter,

1. You don't need environment hub for creating managed package and publish it on AppExchange. It will be all happening from your Dev org. directly.
2. You will need environment hub if you need to create trial orgs. from your partner account
3. Environment Hub is just one place to manage all trial orgs created from your partner login.

Hope this helps!