More granular permission settings for sub groups of a large team
Giving team owners/leaders the ability to define sub groups of team members and control their ability to deploy to certain environments.
For example not being able to connect to/make deployments to 'production' orgs.
10
votes
Anonymous
shared this idea
-
Chris Vaughan
commented
Currently, there is no mechanism in place to prevent a user that has credentials from connecting Gearset to a production or UAT org. It would be an awesome feature to lock deployments at the org level in order to prevent users from connecting to sensitive environments within Gearset rather than doing this via permissions in each org.