Expand the user security model to restrict user compare / deployment access to defined comparison filters
Hi guys -
In many instances, we would like to restrict user access to certain compare / deploy metadata filters. In our case, it would be rare that all metadata changes are to be deployed and we would like to give our engineers access to only certain filters. This would reduce the risk that items that should not be deployed at a high level will not be deployed. In the current model, if a user has deploy access, they can deploy anything and everything. This is what we are looking to avoid.
Thanks in advance for your time!
Best,
Richard
Richard Scott
shared this idea
-
Perry Inaldo
commented
Not sure if this is different than what you are asking but I would also like to have an account level access something like the org level delegate access of Comparison, Validation, Deployment. This way you can set what a team member can only do. Not everyone should have a deployment access, thus preventing breaking code they accidentally deploy.
-
Josh Long
commented
Similarly we are looking to give some users access to deploy more "Config" items only. (Objects, Fields, Layouts, etc.)
While having others users able to deploy all items. So we have more control over what is being deployed and by whom for visibility and other approval process.