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?
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
Bitbucket Pipelines helps me manage and automate a number of serverless deployments to AWS Lambda and this is how I do it. I'm building Node.js Lambda functions using node-lambda ...
Connect with like-minded Atlassian users at free events near you!Find a group
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no AUG chapters near you at the moment.Start an AUG
You're one step closer to meeting fellow Atlassian users at your local meet up. Learn more about AUGs
We're bringing product updates and pro tips on teamwork to ten cities around the world.Save your spot