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!


Come for the products,
stay for the community

The Atlassian Community can help you and your team get more value out of Atlassian products and practices.

Atlassian Community about banner
Community Members
Community Events
Community Groups

What does UNLICENSED user mean in Bitbucket Server?


The UNLICENSED lozenge means that the user has not been granted (directly or via a group) access to Bitbucket Server.

In order for a user to have access to Bitbucket Server and be able to perform any git operations (including clone and pull), the user has to have at a minimum the "Bitbucket User" permission level. See the Global permissions page for reference.


In Bitbucket Server, users can be defined directly in the application or sourced from an external user directory (e.g. LDAP, Crowd, Jira).


These are the most common reasons for users appearing as UNLICENSED:

- the user does not belong to a group that has been granted access to Bitbucket Server

- the external directory synchronization is not functional


As a best practice, for external users, we recommend the change (likely adding the user to a group) to be done in the external directory and then trigger the Synchronization in Bitbucket (or wait for the synchronization to be automatically performed - the default is one hour).


For internal users, the user can be added to a group (preferred option) or the permissions can be directly granted.



Caterina - Atlassian


Marek S_
Atlassian Team
Atlassian Team members are employees working across the company in a wide variety of roles.
May 14, 2018

Hi @Caterina _or Kate_ Curti - while I haven't had a chance to come across this yet, your explanation seems to make perfect sense. Thank you! :-)

Hi @Caterina _or Kate_ Curti 

In my scenario user is already in a group with read/write permission. but his profile is listed as unlicensed and the user is not able to login to Bitbucket 

Caterina _or Kate_ Curti
Atlassian Team
Atlassian Team members are employees working across the company in a wide variety of roles.
Feb 07, 2020

Hi @Sai kiran P ,

For the user to be able to log in, you'll need to make sure that the group he belongs to (or the user him/herself) has the "Bitbucket User" permission in the Global permissions. To go there, click the 'cog' menu in the header to go to the admin area and click Global permissions (under 'Accounts').

This is how that user interface looks like:



Could it be that the the read/write permission on a project or on a repository? If that's the case, this would not be enough for the user to be granted access to Bitbucket but only to get access to a repository. Having access to Bitbucket is still a pre-requisite.





Log in or Sign up to comment
AUG Leaders

Atlassian Community Events