If I setup a database password variable and scope it to each environment, and setup the prod version of the variable to sensitive. Can a developer change the scope of my production scoped variable to dev and deploy and end up seeing my production database password as it would get put into the dev web.config. They could then return the variabes back to their old scope and noone would ever know that they now know the production password
Can I secure access to variables so developers can’t touch Prod scoped variables?
Thanks for reaching out! Variable permissions are inherited from what the variable is scoped to. A user who doesn’t have permissions for the Production environment won’t have access to variables scoped to Production. If you singularly scope your database password variable to the Production environment, then the user won’t be able to view or change it. To control which environments your users have permissions for, you can create different teams with defined permissions, as shown in our documentation.
To have very specific user permissions, you can define your own user roles and incorporate this into the mixed environment permissions, as our out of the box permissions are very broad and designed to be generic.
