Are you in the loop? Keep up with the latest by making sure you're subscribed to Community Announcements. Just click Watch and select Articles.

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!


Bitbucket Global Permissions vs. Project Permissions

I'm new to administrating Bitbucket.

I setup the Global permissions so that all Bitbucket users have Project Creator permission. This allows users to create new projects and repositories.

When I look at Project permissions it defaults to "No access" and only the person who created the Project is listed as an Admin

No one else can see the Project. When you up the Default permission in the project to "Write" people can see the project, but they still do not have permission to create new repositories.

It is only after I make a person an Admin in the specific project that they can create repositories.


This seems like over kill to make people Admins. I also do not want to have to go into each project to grant this access every time, when I've already set the Global permission.

Can anyone help with advice on understanding permissions better and how can I setup Bitbucket so that we can default projects with a standard set of people or groups that can create repositories?



Log in or Sign up to comment
AUG Leaders

Atlassian Community Events