The Atlassian Community Forums are currently in read-only mode. We will be relaunching on a new platform on September 22 (read more here). We apologize for the extended downtime. For concerns or questions, please email communitymanagers@atlassian.com. See you on the other side, on the new Atlassian Community Forums! :)
I need to setup group access right to repositories. I would like to set permissions for groups as I do not want to set rights per user. I only way I see to so this is by Bitbucket team.
1. Approach one is to create a team and create a repository for the team. This repository will be shown when you go to the team homepage.
2. Second approach is to create a repository and a team separately. Then, we do not create a repository for the team. We only go to the repository settings and then give access to the team ( usually some groups of the team) to the repository. If you go to the team page in this case, there are no repositories shown for the team.
Both of the above can work for me, but I was wondering if any of the approaches has any advantages over the other ?
Thanks,
1 answer
Comments for this post are closed
Community moderators have prevented the ability to post new answers.
0 votes
Deleted user
November 27, 2015 edited
Can you provide screenshots here? I am confused on what do you actually mean by "set up a team" in Bitbucket server
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.