You need to sign in to do that
Don't have an account?
Jeff L
Prevent Force.com IDE Access to Production Org
We are trying to design and document our development processes and scenarios and generally want to use Change Sets to deploy code/configurations to our Production org. We also heavily leverage the Force.com IDE for development efforts, but want to limit the use of the Force.com IDE for deploying configuration/code to the Production org because it is often easy to accidentially save/deploy a piece of code into the Production environment unknowingly.
Is it possible to make configuration/security changes to selectively (e.g., user specific) prevent either:
1. Deployment of code from Force.com IDE project to the Production Org.
2. Creation of a Force.com IDE Project that is wired to the Production Org.
Thanks in advance.
Jeff L.
Is it possible to make configuration/security changes to selectively (e.g., user specific) prevent either:
1. Deployment of code from Force.com IDE project to the Production Org.
2. Creation of a Force.com IDE Project that is wired to the Production Org.
Thanks in advance.
Jeff L.
From my knowledge you cannot prevent accessing any org data in force.com ide or change set.
But alternatively you can completely restrict API Access in Profile setting to avoid accessing Production data in force.com.
Please let me know if you know any idea.