Team Segregation - Bamboo

[Clinton Smith]

Is it possible to segregate development teams in Bamboo?

I.E

Two teams, Team 1 and Team 2

Team 1 cannot see Team 2's plans and vice versa.

We are looking to POC Bamboo to see if it will work for CI at an enterprise scale.  We will have hundreds of teams, all should only be able to see their own plans.

We would also need to have governance implemented.  Such as approvals before a production deployment and seperation of duties (whomever approves to deploy to production will not be able to perform the actual deployment).

Any insight would be great.

[Krystian Brazulewicz]

This feature is on our roadmap (permission for approving releases before deployment) but I'm unable to tell now when we'll ship it.

[serge_poueme]

Hello. We are looking into a similar use case, since we are going through ISO compliance work. We would like to add an approval step before a production deployment, that step would be condititional to the successful deployment and testing of a release in staging. Is it possible to track that feature request from your roadmap so that we can plan accordingly ?

[Clinton Smith]

Perfect.  Thank you.

How about the seperation of duties?  Can an approval step be setup before a production deployment that does not allow the approver to deploy to production?

[Krystian Brazulewicz]

Clinton

I think this documentation covers your question: https://confluence.atlassian.com/display/BAMBOO/Users+and+permissions

In short: yes we implement plan permissions and we also allow authenticate/authorize users with LDAP directory.

[Samuel Cameron]

Yes. Access is controlled through groups. You just put them into different groups and remove access for the groups "Anonymous users" and "Logged in users".