We have a Bitbucket team for all our company's repos. We occasionally have contractors that need to work on one or more repos.
So far I have added those contractors' accounts to our team without automatic access to any repos, then granted them access to the specific repos they need to use. However, there doesn't seem to be any restriction with granting repo access to non-teammember accounts.
Is there any functional difference between the two approaches?
It looks like by adding and increasing the number of team members there could be a billing implication, but by simply granting access there won't be. Is that correct?
Unfortunately this has been a confusing topic in Bitbucket cloud for quite some time.
You have the ability to grant access to a repository to anyone with a Bitbucket account. When you do this, it does impact billing. Anyone with repository access is counted towards the number of users you are billed for. You can see the users that you are being billed for by going to Settings, choosing your team from the dropdown at the top of the page, and then choosing PLANS & BILLING > Plan details
Adding users to your team (and groups) just gives you an easier way to manage permissions, otherwise it is "equivalent" to giving manual access to a repository.
As a project manager, I have discovered that different developers want to bring their previous branching method with them when they join the team. Some developers are used to performing individual wo...
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