I suggest you...

more granular team/project roles

It would be nice if there was a way to expand the roles for a team on a per environment basis. For example I'd like I'd like for the developer team to be able to create and edit variables in the production scope, but not be able to deploy there.

1 vote
Vote
Sign in
Check!
(thinking…)
Reset
or sign in with
  • facebook
  • google
    Password icon
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    Doofenshmirtz shared this idea  ·   ·  Flag idea as inappropriate…  ·  Admin →

    1 comment

    Sign in
    Check!
    (thinking…)
    Reset
    or sign in with
    • facebook
    • google
      Password icon
      Signed in as (Sign out)
      Submitting...
      • Anonymous commented  ·   ·  Flag as inappropriate

        You should be able to achieve this sort of behaviour with existing functionality...

        Custom role for Variable Manager (see my comment here: https://octopusdeploy.uservoice.com/forums/170787-general/suggestions/15080820-review-variable-edit)

        Create new Teams that have permissions scoped to the environments appropriately.
        1) Remove deployment permissions from your default developers team
        2) Add Variable Manager role to developers team
        3) New team that includes the developers, scoped to non-live environments, that has deployment permissions

        Hopefully I've explained that right!

      Feedback and Knowledge Base