Showing results for 
Search instead for 
Did you mean: 
Sign up Log in

It's not the same without you

Join the community to find out what other Atlassian users are discussing, debating and creating.

Atlassian Community Hero Image Collage

Restrict admins to repos in projects, not all repos


I am wondering if there is a way to create admin groups that only have admin access within all repos in a specific project. 

Example: Let's say I have Project A and Project B.

Project A has Group A, which is granted the admin repo access by default when new repos are created. 

As it is now, this allows Group A admin privileges on new repos in Project B too, not just Project A. 

Is there a way to restrict a group to a single Project? Making the repo private does not assist in this. 

Thanks in advance,

1 answer

1 accepted

0 votes
Answer accepted

Hi Julia,

I'm afraid that it is not possible to manage permissions on a project level at the moment. We have a feature request about this in our issue tracker: and updates will get posted there regarding the status.

In the meantime, I can suggest the following as a workaround:

  • Create the two admin groups, Group A and Group B
  • Change the default access of these groups from Admin to None. You can do so by opening the User Group in Bitbucket UI > select Edit from the top right corner and then change Default repository access to None
  • Then, you can manually add the appropriate group to each of the repos with Admin access, from each repo's Repository settings > User and group access

I understand that this creates a bit more work, since the groups will need to be manually added to the repos, but it's the only way to prevent the groups from gaining automatically admin access to all repos.

Please note the following:

If these groups also have permissions to Administer workspace (you can find this setting in the same dialog as Default repository access), even though they won't be able to view any repos they haven't been added to, they can still gain access to the repo if they know its url, by navigating to<workspace-id>/<repo-slug>/admin/access and restoring their own access.

This is because they are workspace admins.

However, if they don't have permissions to Administer the workspace, this is not an issue.

Finally, I would suggest that you add yourself as a watcher in the public feature request I gave you (by selecting the Start watching this issue link in that ticket), if you'd like to get notified via email on updates regarding project permissions.

If you have any questions, please feel free to let me know.

Kind regards,

Thank you Theodora, for your very thorough reply. 

Suggest an answer

Log in or Sign up to answer
Community showcase
Published in Bitbucket

New improvements to user management in Bitbucket Cloud 👥

Hey Community! We’re willing to wager that quite a few of you not only use Bitbucket, but administer it too. Our team is excited to share that we’ll be releasing improvements throughout this month of...

3,826 views 10 16
Read article

Community Events

Connect with like-minded Atlassian users at free events near you!

Find an event

Connect with like-minded Atlassian users at free events near you!

Unfortunately there are no Community Events near you at the moment.

Host an event

You're one step closer to meeting fellow Atlassian users at your local event. Learn more about Community Events

Events near you