Do I need to enable Dev Hub in my PROD Org? The Next CEO of Stack Overflow2019 Community Moderator ElectionCan Dev Hub be enabled if we are on Salesforce Classic?Which org do I set my Dev Hub up in?Enabled Dev Hub for company org (Performance Edition), but cannot create scratch orgsDoes enabling Dev Hub disable anything else? Can I turn off Dev Hub?Can a developer create scratch orgs without a login on the Dev Hub org?What are the options for cross-org use of a dev hub?Dev Hub in Partner orgNo Dev hub available in Enterprise Edition tooCreate scratch org with namespace?confused about the different org types involved in a salesforce development env
Why do professional authors make "consistency" mistakes? And how to avoid them?
Indicator light circuit
Help understanding this unsettling image of Titan, Epimetheus, and Saturn's rings?
Is there a way to save my career from absolute disaster?
What can we do to stop prior company from asking us questions?
Is it professional to write unrelated content in an almost-empty email?
Is there a difference between "Fahrstuhl" and "Aufzug"
Does it take more energy to get to Venus or to Mars?
What does "Its cash flow is deeply negative" mean?
Is it ever safe to open a suspicious html file (e.g. email attachment)?
Return the Closest Prime Number
If/When UK leaves the EU, can a future goverment conduct a referendum to join the EU?
Why do airplanes bank sharply to the right after air-to-air refueling?
Are there any limitations on attacking while grappling?
Why has the US not been more assertive in confronting Russia in recent years?
Unreliable Magic - Is it worth it?
Make solar eclipses exceedingly rare, but still have new moons
Example of a Mathematician/Physicist whose Other Publications during their PhD eclipsed their PhD Thesis
How to avoid supervisors with prejudiced views?
How to prevent changing the value of variable?
Why does the UK parliament need a vote on the political declaration?
Why didn't Khan get resurrected in the Genesis Explosion?
What connection does MS Office have to Netscape Navigator?
How to safely derail a train during transit?
Do I need to enable Dev Hub in my PROD Org?
The Next CEO of Stack Overflow2019 Community Moderator ElectionCan Dev Hub be enabled if we are on Salesforce Classic?Which org do I set my Dev Hub up in?Enabled Dev Hub for company org (Performance Edition), but cannot create scratch orgsDoes enabling Dev Hub disable anything else? Can I turn off Dev Hub?Can a developer create scratch orgs without a login on the Dev Hub org?What are the options for cross-org use of a dev hub?Dev Hub in Partner orgNo Dev hub available in Enterprise Edition tooCreate scratch org with namespace?confused about the different org types involved in a salesforce development env
I want to adopt Salesforce DX development. Do I have to enable Dev Hub in my Prod Org, or can I activate it in a new Developer Edition, do my development in scratch orgs and eventually deploy the packages to my DEV, QA, UAT and PROD orgs?
Background: I am a developer and currently we develop in our personal dev sandboxes and push our code through other sandboxes (DEV, QA, UAT) and then to Prod org. My company does not want to give developers Prod access at all, even limited access licenses, so I don't think we should enable Dev Hub in Prod.
So I need to know if having a Dev Hub org that is not my Prod org is ok.
salesforcedx dev-hub
asked 13 hours ago
JimJim
283
New contributor
Jim is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
add a comment |
I want to adopt Salesforce DX development. Do I have to enable Dev Hub in my Prod Org, or can I activate it in a new Developer Edition, do my development in scratch orgs and eventually deploy the packages to my DEV, QA, UAT and PROD orgs?
Background: I am a developer and currently we develop in our personal dev sandboxes and push our code through other sandboxes (DEV, QA, UAT) and then to Prod org. My company does not want to give developers Prod access at all, even limited access licenses, so I don't think we should enable Dev Hub in Prod.
So I need to know if having a Dev Hub org that is not my Prod org is ok.
salesforcedx dev-hub
asked 13 hours ago
JimJim
283
New contributor
Jim is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
add a comment |
I want to adopt Salesforce DX development. Do I have to enable Dev Hub in my Prod Org, or can I activate it in a new Developer Edition, do my development in scratch orgs and eventually deploy the packages to my DEV, QA, UAT and PROD orgs?
Background: I am a developer and currently we develop in our personal dev sandboxes and push our code through other sandboxes (DEV, QA, UAT) and then to Prod org. My company does not want to give developers Prod access at all, even limited access licenses, so I don't think we should enable Dev Hub in Prod.
So I need to know if having a Dev Hub org that is not my Prod org is ok.
salesforcedx dev-hub
asked 13 hours ago
JimJim
283
New contributor
Jim is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
I want to adopt Salesforce DX development. Do I have to enable Dev Hub in my Prod Org, or can I activate it in a new Developer Edition, do my development in scratch orgs and eventually deploy the packages to my DEV, QA, UAT and PROD orgs?
Background: I am a developer and currently we develop in our personal dev sandboxes and push our code through other sandboxes (DEV, QA, UAT) and then to Prod org. My company does not want to give developers Prod access at all, even limited access licenses, so I don't think we should enable Dev Hub in Prod.
So I need to know if having a Dev Hub org that is not my Prod org is ok.
salesforcedx dev-hub
salesforcedx dev-hub
asked 13 hours ago
JimJim
283
New contributor
Jim is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
asked 13 hours ago
JimJim
283
New contributor
Jim is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
asked 13 hours ago
JimJim
283
New contributor
Jim is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
asked 13 hours ago
JimJim
283
asked 13 hours ago
JimJim
283
283
New contributor
Jim is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
New contributor
Jim is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
Jim is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
add a comment |
add a comment |
2 Answers
2
active
oldest
votes
Dev Hub can be enabled in Developer Edition orgs, but the scratch org limits are significantly lower than in paid Salesforce production orgs. In a Developer Edition org, the limits are just 3 active and 6 daily scratch orgs, which might suffice for an individual developer who is not using continuous integration but can be stifling in a process that likes to use a lot of orgs. It's not feasible to share a Developer Edition Dev Hub across a team; each developer would need their own.
Production orgs, as described in the linked documentation, offer an order of magnitude more scratch orgs. To use Dev Hub in production, you can request special free, limited access licenses (I wasn't sure if that's what you were alluding to in your question) to enable developers to authenticate and create scratch orgs against Prod, without viewing CRM data.
Of course, some organizations may be unwilling for compliance or process reasons even to use those licenses, in which case you don't have much recourse other than a separate paid org or multiple Developer Editions.
answered 13 hours ago
David ReedDavid Reed
38.5k82356
1
Thank you, I was indeed referring to that limited access licenses. I think the limitations you mention are sufficient reason to try to change their mind on allowing us access to Prod. TPTB implied there was leeway in that regard.
– Jim
12 hours ago
add a comment |
So I need to know if having a Dev Hub org that is not my Prod org is ok.
Typically it should be OK. However you will end up having limited number of Scratch Orgs that you can create using a DE Org.
The Enable Dev Hub in Your Org documentation lists down all such considerations while using a trial or DE Org as Dev Hub. One of the key considerations out there is as below, so you should plan your implementation approach depending on the scenario.
If you plan to create package versions or run continuous integration jobs, it’s better to use a production or business org 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.
answered 13 hours ago
Jayant DasJayant Das
17.4k21330
1
Thank you, I think if I explain it this way I might be able to convince TPTB to allow us to have limited access licenses and enable the Dev Hub in Prod.
– Jim
12 hours ago
add a comment |
Your Answer
StackExchange.ready(function()
var channelOptions =
tags: "".split(" "),
id: "459"
;
initTagRenderer("".split(" "), "".split(" "), channelOptions);
StackExchange.using("externalEditor", function()
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled)
StackExchange.using("snippets", function()
createEditor();
);
else
createEditor();
);
function createEditor()
StackExchange.prepareEditor(
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: false,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: null,
bindNavPrevention: true,
postfix: "",
imageUploader:
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
,
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
);
);
Jim is a new contributor. Be nice, and check out our Code of Conduct.
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function ()
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fsalesforce.stackexchange.com%2fquestions%2f255867%2fdo-i-need-to-enable-dev-hub-in-my-prod-org%23new-answer', 'question_page');
);
Post as a guest
Required, but never shown
2 Answers
2
active
oldest
votes
2 Answers
2
active
oldest
votes
active
oldest
votes
active
oldest
votes
Dev Hub can be enabled in Developer Edition orgs, but the scratch org limits are significantly lower than in paid Salesforce production orgs. In a Developer Edition org, the limits are just 3 active and 6 daily scratch orgs, which might suffice for an individual developer who is not using continuous integration but can be stifling in a process that likes to use a lot of orgs. It's not feasible to share a Developer Edition Dev Hub across a team; each developer would need their own.
Production orgs, as described in the linked documentation, offer an order of magnitude more scratch orgs. To use Dev Hub in production, you can request special free, limited access licenses (I wasn't sure if that's what you were alluding to in your question) to enable developers to authenticate and create scratch orgs against Prod, without viewing CRM data.
Of course, some organizations may be unwilling for compliance or process reasons even to use those licenses, in which case you don't have much recourse other than a separate paid org or multiple Developer Editions.
answered 13 hours ago
David ReedDavid Reed
38.5k82356
1
Thank you, I was indeed referring to that limited access licenses. I think the limitations you mention are sufficient reason to try to change their mind on allowing us access to Prod. TPTB implied there was leeway in that regard.
– Jim
12 hours ago
add a comment |
Dev Hub can be enabled in Developer Edition orgs, but the scratch org limits are significantly lower than in paid Salesforce production orgs. In a Developer Edition org, the limits are just 3 active and 6 daily scratch orgs, which might suffice for an individual developer who is not using continuous integration but can be stifling in a process that likes to use a lot of orgs. It's not feasible to share a Developer Edition Dev Hub across a team; each developer would need their own.
Production orgs, as described in the linked documentation, offer an order of magnitude more scratch orgs. To use Dev Hub in production, you can request special free, limited access licenses (I wasn't sure if that's what you were alluding to in your question) to enable developers to authenticate and create scratch orgs against Prod, without viewing CRM data.
Of course, some organizations may be unwilling for compliance or process reasons even to use those licenses, in which case you don't have much recourse other than a separate paid org or multiple Developer Editions.
answered 13 hours ago
David ReedDavid Reed
38.5k82356
1
Thank you, I was indeed referring to that limited access licenses. I think the limitations you mention are sufficient reason to try to change their mind on allowing us access to Prod. TPTB implied there was leeway in that regard.
– Jim
12 hours ago
add a comment |
Dev Hub can be enabled in Developer Edition orgs, but the scratch org limits are significantly lower than in paid Salesforce production orgs. In a Developer Edition org, the limits are just 3 active and 6 daily scratch orgs, which might suffice for an individual developer who is not using continuous integration but can be stifling in a process that likes to use a lot of orgs. It's not feasible to share a Developer Edition Dev Hub across a team; each developer would need their own.
Production orgs, as described in the linked documentation, offer an order of magnitude more scratch orgs. To use Dev Hub in production, you can request special free, limited access licenses (I wasn't sure if that's what you were alluding to in your question) to enable developers to authenticate and create scratch orgs against Prod, without viewing CRM data.
Of course, some organizations may be unwilling for compliance or process reasons even to use those licenses, in which case you don't have much recourse other than a separate paid org or multiple Developer Editions.
answered 13 hours ago
David ReedDavid Reed
38.5k82356
Dev Hub can be enabled in Developer Edition orgs, but the scratch org limits are significantly lower than in paid Salesforce production orgs. In a Developer Edition org, the limits are just 3 active and 6 daily scratch orgs, which might suffice for an individual developer who is not using continuous integration but can be stifling in a process that likes to use a lot of orgs. It's not feasible to share a Developer Edition Dev Hub across a team; each developer would need their own.
Production orgs, as described in the linked documentation, offer an order of magnitude more scratch orgs. To use Dev Hub in production, you can request special free, limited access licenses (I wasn't sure if that's what you were alluding to in your question) to enable developers to authenticate and create scratch orgs against Prod, without viewing CRM data.
Of course, some organizations may be unwilling for compliance or process reasons even to use those licenses, in which case you don't have much recourse other than a separate paid org or multiple Developer Editions.
answered 13 hours ago
David ReedDavid Reed
38.5k82356
edited 13 hours ago
answered 13 hours ago
David ReedDavid Reed
38.5k82356
answered 13 hours ago
David ReedDavid Reed
38.5k82356
answered 13 hours ago
David ReedDavid Reed
38.5k82356
38.5k82356
1
Thank you, I was indeed referring to that limited access licenses. I think the limitations you mention are sufficient reason to try to change their mind on allowing us access to Prod. TPTB implied there was leeway in that regard.
– Jim
12 hours ago
add a comment |
1
Thank you, I was indeed referring to that limited access licenses. I think the limitations you mention are sufficient reason to try to change their mind on allowing us access to Prod. TPTB implied there was leeway in that regard.
– Jim
12 hours ago
1
1
Thank you, I was indeed referring to that limited access licenses. I think the limitations you mention are sufficient reason to try to change their mind on allowing us access to Prod. TPTB implied there was leeway in that regard.
– Jim
12 hours ago
Thank you, I was indeed referring to that limited access licenses. I think the limitations you mention are sufficient reason to try to change their mind on allowing us access to Prod. TPTB implied there was leeway in that regard.
– Jim
12 hours ago
add a comment |
So I need to know if having a Dev Hub org that is not my Prod org is ok.
Typically it should be OK. However you will end up having limited number of Scratch Orgs that you can create using a DE Org.
The Enable Dev Hub in Your Org documentation lists down all such considerations while using a trial or DE Org as Dev Hub. One of the key considerations out there is as below, so you should plan your implementation approach depending on the scenario.
If you plan to create package versions or run continuous integration jobs, it’s better to use a production or business org 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.
answered 13 hours ago
Jayant DasJayant Das
17.4k21330
1
Thank you, I think if I explain it this way I might be able to convince TPTB to allow us to have limited access licenses and enable the Dev Hub in Prod.
– Jim
12 hours ago
add a comment |
So I need to know if having a Dev Hub org that is not my Prod org is ok.
Typically it should be OK. However you will end up having limited number of Scratch Orgs that you can create using a DE Org.
The Enable Dev Hub in Your Org documentation lists down all such considerations while using a trial or DE Org as Dev Hub. One of the key considerations out there is as below, so you should plan your implementation approach depending on the scenario.
If you plan to create package versions or run continuous integration jobs, it’s better to use a production or business org 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.
answered 13 hours ago
Jayant DasJayant Das
17.4k21330
1
Thank you, I think if I explain it this way I might be able to convince TPTB to allow us to have limited access licenses and enable the Dev Hub in Prod.
– Jim
12 hours ago
add a comment |
So I need to know if having a Dev Hub org that is not my Prod org is ok.
Typically it should be OK. However you will end up having limited number of Scratch Orgs that you can create using a DE Org.
The Enable Dev Hub in Your Org documentation lists down all such considerations while using a trial or DE Org as Dev Hub. One of the key considerations out there is as below, so you should plan your implementation approach depending on the scenario.
If you plan to create package versions or run continuous integration jobs, it’s better to use a production or business org 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.
answered 13 hours ago
Jayant DasJayant Das
17.4k21330
So I need to know if having a Dev Hub org that is not my Prod org is ok.
Typically it should be OK. However you will end up having limited number of Scratch Orgs that you can create using a DE Org.
The Enable Dev Hub in Your Org documentation lists down all such considerations while using a trial or DE Org as Dev Hub. One of the key considerations out there is as below, so you should plan your implementation approach depending on the scenario.
If you plan to create package versions or run continuous integration jobs, it’s better to use a production or business org 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.
answered 13 hours ago
Jayant DasJayant Das
17.4k21330
answered 13 hours ago
Jayant DasJayant Das
17.4k21330
answered 13 hours ago
Jayant DasJayant Das
17.4k21330
answered 13 hours ago
Jayant DasJayant Das
17.4k21330
17.4k21330
1
Thank you, I think if I explain it this way I might be able to convince TPTB to allow us to have limited access licenses and enable the Dev Hub in Prod.
– Jim
12 hours ago
add a comment |
1
Thank you, I think if I explain it this way I might be able to convince TPTB to allow us to have limited access licenses and enable the Dev Hub in Prod.
– Jim
12 hours ago
1
1
Thank you, I think if I explain it this way I might be able to convince TPTB to allow us to have limited access licenses and enable the Dev Hub in Prod.
– Jim
12 hours ago
Thank you, I think if I explain it this way I might be able to convince TPTB to allow us to have limited access licenses and enable the Dev Hub in Prod.
– Jim
12 hours ago
add a comment |
Jim is a new contributor. Be nice, and check out our Code of Conduct.
Jim is a new contributor. Be nice, and check out our Code of Conduct.
Jim is a new contributor. Be nice, and check out our Code of Conduct.
Jim is a new contributor. Be nice, and check out our Code of Conduct.
Thanks for contributing an answer to Salesforce Stack Exchange!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function ()
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fsalesforce.stackexchange.com%2fquestions%2f255867%2fdo-i-need-to-enable-dev-hub-in-my-prod-org%23new-answer', 'question_page');
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
