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

can't push or pull to git because reached user limit



we are having a problem pushing or pulling to Git at the moment, it says we have reached the limit of users. We have all been using this for a long time and these problems have only just happened. My boss has checked his account and updated his credit card number on the billing section but we still can't push. What do we need to do to resolve this issue? I have a personal and a work account, its the work account that is not working which is and it is the Handsam account that is not working

1 answer

1 accepted

0 votes
Answer accepted
Ben Atlassian Team Jun 27, 2022

Hey Helen,

I have reached out to our billing & licensing team and can see that the card details have not yet been updated for the handsam workspace.

You will need to ask the main billing/technical contact for that workspace to update the details here:


- Ben (Bitbucket Cloud Support)

Hi, strangely, my boss had already updated his credit card details in this section. We have just gone back in to his my.atlassian page and checked and then 2 minutes later I received an email to say the plan had changed and now we can push again. So, not sure why it wasn't working but it is now

Ben Atlassian Team Jun 28, 2022

Hey @Helen Postle - glad to hear it has been resolved, there is a chance that the change was either not saved on the form or there was a processing time involved for the card to be charged.


- Ben (Bitbucket Cloud Support)

Suggest an answer

Log in or Sign up to answer

Atlassian Community Events