1. Bitbucket
  2. Public Issue Tracker
  3. master
  4. Issues


Issue #4248 invalid

Team permissions not applied to team repositories

created an issue


I already posted a message about this issue on the forum the last week but I got no answer.

I have a team account that contains 3 groups: one for admin permissions, one for read/write permissions and one for read permissions. However, the permissions for these groups and the users associated to these groups are not automatically propagated to all the repositories that are owned by the team account (although the checkbox that says "Group name have write access to this account's repositories" is ticked).

To make it works, I have to go to the administration of each team repository; then access management and finally to add the team groups by specifying again the permission type (read/write/admin) whereas the team groups already have these information.

Is it a bug? If not, the sentence "have read/write/admin access to this account's repositories" is really embarrassing. Is there a page that explains group and team permissions in details?

Also, I have some team members that complain to receive emails each time I perform some tests with groups and permissions. Could you add a checkbox or something to disable notifications from the team administration?

One more question about permissions, if I give admin permission to a user through a team group does it also gives write access to team repositories?

Comments (5)

  1. Marcus Bertrand staff

    This is not how this is designed to work, and I haven't been able to reproduce it. Please send us an email to support@bitbucket.org with an explanation of the specific repositories and we'll take a look. As for the other question, please make a new ticket for the feature request.

    For the last question, it does not. Admin access is only to administrate the repository, not necessarily read or write the data.

  2. Log in to comment