Daniel B on 01 Mar 2023 13:22:57
Pipeline access is limited to just one level: Admin
This means that development leads (usually multiple ones for a single pipeline) are able to delete the pipeline and add other users to it
Neither of these features should be allowed for pipeline users, and should be admin only features
The ability to select different levels of access to the pipeline would discourage developers from publishing directly to Test and allow more people to have visibility into the deployment pipeline (something we can't share widely as there is a risk of users deleting the pipeline and adding more users to it)
- Comments (2)
RE: Allow for more access roles in Pipelines, at least Admin and Users
The main role I'd like is "User".For someone that can view the pipeline and deploy between stages, but not edit permissions, change workspace mappings, or delete the pipeline."Reader"/"Approver" roles would also be nice, but they're less useful and more complicated to implement respectively. There's no need for them to block the implentation of a User role as a first step.
RE: Allow for more access roles in Pipelines, at least Admin and Users
We have exactly the same problem, would help us a lot if we got the User role!