Hello Tushar, Unfortunately, no. Permissions are at a group level and not at a server level. Having it in both places would complicate that structure even more (if permissions are defined at both levels, we'd need to figure out how overrides work, etc).
Cheers, Aravind On Tue, Jul 5, 2016 at 6:43 AM, TUSHAR GARG <[email protected]> wrote: > Greetings, > > Is there a way to define *role level permissions* at *go-server* level > instead of *pipeline-group* level ? > > For eg., consider the following scenario : > My project has a good number of pipeline-groups (say *G1, G2..., G10)*. > We need to add a new role (say *contributor*) which will have *view *and* > operate *authorization rights across all pipelines. > In order to do it, the *role level permissions* needs to be updated in > all pipeline groups (from *G1...G10*). Same effort needs to be repeated > 10 times (or more depending upon pipeline groups). > > I have tried playing around with user management in Go and also searching > through this group. But couldn't find it. > Any help will be appreciated. > > > > -- > You received this message because you are subscribed to the Google Groups > "go-cd" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to [email protected]. > For more options, visit https://groups.google.com/d/optout. > -- You received this message because you are subscribed to the Google Groups "go-cd" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/d/optout.
