Groups assigned to new repositories

Issue #8866 resolved
Jim Koelkebeck
created an issue

After creating a new repository, I went to "Access Management" to assign groups and permissions. I was not happy to find that a set of groups had already been assigned access to the repository. I had to remove most of them and reassign as I needed.

Why does BB make assumptions as to which of my groups should be assigned to new repositories? I see this as reckless, given that we have several disparate groups, including outside contractors.

How can I manage these assignments, as in remove all assignments and leave it to me to make them myself according to the individual needs of each repository?

I don't know what "Kind" of ticket this is, so I'm leaving it as a bug.

Comments (8)

  1. Brian Nguyen

    Hi Jim,

    When you create a new repository, Bitbucket uses the default group permission to determine what groups to add.

    You can avoid this by setting the default permission of each group to none. I have attached a screenshot of where you can find this.

    I hope this helps.

    Cheers, Brian

  2. Jim Koelkebeck reporter

    Unfortunately, I can not change the "default" permission without it changing the permissions for all of the repositories to which a group has been assigned. I tried to set one of the groups to "None" and was prompted with "This will update the group's permissions on %(affected_repos)d of your repositories", I could accept or cancel. I cancelled because I DO NOT want to change existing permissions, and the default permission remained the same.

    Also note the error in the message I received (see quoted text above).

  3. Brian Nguyen

    Hi JIm,

    Unfortunately, with how the groups page is set up at the moment, there is no way to update the default permission without, updating permissions on the affected repositories.

    I have raised an issue for this at #8888.

    In the meantime, we can change the default permissions for you manually. If you can let us know what groups you want changed, we can help.

    If you are unwilling to post this information on the public issue tracker you can email us at and we'll sort it out.

    Cheer, Brian

  4. Tim Jarvis

    I have this same problem. I do not want groups added to new repositories by default. Given that #8888 is not yet done, and marked as minor how do I organize to get my permissions changed?

  5. Log in to comment