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

Earn badges and make progress

You're on your way to the next level! Join the Kudos program to earn points and save your progress.

Deleted user Avatar
Deleted user

Level 1: Seed

25 / 150 points

Next: Root


1 badge earned


Participate in fun challenges

Challenges come and go, but your rewards stay with you. Do more to earn more!


Gift kudos to your peers

What goes around comes around! Share the love by gifting kudos to your peers.


Rise up in the ranks

Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!


Public Repo - allow only internal user to be Reviewer



I have a couple of questions about Public Repositories. 

 We have a public repository, and it seems that anyone in the world (with a Bitbucket account) can Approve or Request Changes on an open PR. 

1) Is it possible to have a public repository but only have our internal users (users who have been granted access to our Bitbucket and then project/repository) as our only reviewers where only they can approve/reject and merge? 

I understand that public users can not merge PR, but we got a request for the public logged-in Bitbucket user not having the capability to review (Approve/ Request Changes/decline and so on). Is that even possible?

2) When assigning reviewers is it possible to only have our internal users as reviewers (and only for internal users to show up in the user picker list?) Or the reason we get a public list of users in the user picker list is driven by the fact that this is a public repository? 

3) When our repository is set to private all of our internal members show up in the Reviewers User picker list, when the repository is set to public many of our internal users don't show up in the Users picker list when I search them up (including the ones that did show up when the repo was set to private). does anyone know why that is happening?

Thank you,




1 answer

0 votes
Atlassian Team
Atlassian Team members are employees working across the company in a wide variety of roles.
Sep 20, 2023

Hi Valeria,

The nature of a public repository is that the repository is accessible by anyone with few restrictions. I have raised a feature request on your behalf with our developers to provide this option, you can Watch this request to receive future updates related to it and Vote for it to improve its visibility:

I believe the issue you are facing related to users not showing up depends on their privacy settings. Previously, when you signed up for a Bitbucket Cloud account - your account would be associated automatically with a personal workspace (this was used for authentication). If these users have a personal workspace tied to their account this personal workspace may be listed as "Private" and therefore are incompatible with a Public workspace for this reason.

I hope this helps.


- Ben (Bitbucket Cloud Support)

Suggest an answer

Log in or Sign up to answer
AUG Leaders

Atlassian Community Events