Forums

Articles
Create
cancel
Showing results for 
Search instead for 
Did you mean: 

Issue upgrading plan: "Too many users" error shown despite having only 1 user

3シェイク
June 8, 2026

 

I am currently trying to upgrade my Bitbucket plan, but I am encountering an error and cannot proceed.

On the plan selection screen, it displays the error message "ユーザーが多すぎます" (Too many users) under the Standard plan. However, as you can see in the attached screenshot, the text above says "現在のユーザー数: 1" (Current number of users: 1), and the input for "How many people will use it?" is also set to 1.

Since there is actually only 1 user, this error seems to be incorrect. Could you please investigate this issue and help me upgrade my plan?

I have attached a screenshot of the error screen for your reference.

スクリーンショット 2026-06-09 14.35.00.png

1 answer

0 votes
Arkadiusz Wroblewski
Community Champion
June 8, 2026

Hello @3シェイク 

Since the screen shows current users: 1 and you are selecting 1, this "Too many users" message looks like an error rather than a standard plan-limit issue.

Before treating it as a backend glitch, double-check Workspace settings > User directory(and Plan details). Look closely for any pending invitations or hidden workspace members that might still be counting toward the seat total, and cancel any unneeded invites.

Best,

Arkadiusz🤠

3シェイク
June 9, 2026

Hi @Arkadiusz Wroblewski ,

Thank you for your advice.

I have checked the user directory, but there are no hidden members or unneeded pending invitations. I recently added one more member, so the total number of active users is now 2, as you can see in the newly attached screenshots. Both of them are authorized members.

Also, regarding the plan selection screen, the "How many people?" field automatically displays 2 based on our current user count. This field is grayed out, so I am unable to manually edit or change this number.

Despite the total users being correctly recognized as 2 on the screen, the system still shows the "You have too many users." error under the Standard plan.

Since everything looks correct on our end, this does seem like a backend glitch.

Thank you for your help.スクリーンショット 2026-06-09 16.08.28.pngスクリーンショット 2026-06-09 16.16.50.png

Suggest an answer

Log in or Sign up to answer
DEPLOYMENT TYPE
CLOUD
TAGS
AUG Leaders

Atlassian Community Events