Cascading Permissions

We have a team account and have begun work with outside group. They have added our team account with read permissions to their target private repository, but the privleges apply for the team account only. Any member of our team is unable to see the private repo in any way.

Is there a better permissions model to follow to ensure that our team is able to work with another teams repository?

1 answer

1 accepted

A team should not be added to another team. This will not have any effect. The teams will need to create groups and add each member individually. There is presently no way to connect two teams in the way you may be looking as permissions do not cascade.

For more information on how they all relate, take a look at https://confluence.atlassian.com/display/BITBUCKET/Teams+and+repos+and+groups

You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.

Comment

Products

Interests

Groups

Community resources

Support

Cascading Permissions

1 answer

1 accepted

Suggest an answer

Meet the community IRL

Claire Maynard

What is your #1 piece of advice to new users getting started using Bitbucket?

Atlassian User Groups

Find my local user group

Groups near you