Bitbucket Free workspace incorrectly read-only with 1 user

[THIRUMALESH KODAGANTI]

Workspace: thiru-quant
Repository: thiru_quant_base_repo

Plan: Free
Users shown in billing: 1
Git remote: git@bitbucket.org:thiru-quant/thiru_quant_base_repo.git

Issue:
My Git push is blocked with this message:

[ALERT] Your push failed because the account 'thiru-quant' has exceeded its user limit and this repository is restricted to read-only access.

However, Atlassian billing shows Bitbucket Free with Quantity: 1 user. There are no additional workspace users involved; the three SSH keys are only keys for my own machines.

The local commit is valid and ready to push:
2913506 chore(ac16): establish clean baseline seed

Additional evidence: the Contact Support app selector shows two identical “Bitbucket (Cloud Free)” license entries for the same workspace, https://bitbucket.org/thiru-quant. However, Atlassian Billing shows only one Bitbucket Free subscription with Quantity: 1 user. Please investigate whether a duplicate entitlement or provisioning record is causing the workspace to be incorrectly placed in read-only mode for an alleged user-limit violation.

Please investigate and clear the incorrect read-only/user-limit restriction on this workspace.

Error details for your reference:

GIT_SSH_COMMAND="ssh -i $KEY -o IdentitiesOnly=yes" git push origin master

********************************************************************************

[ALERT] Your push failed because the account 'thiru-quant' has exceeded its

[ALERT] user limit and this repository is restricted to read-only access.

[ALERT] Change your plan to restore write access:

[ALERT] https://bitbucket.org/thiru-quant/workspace/settings/plans

********************************************************************************

fatal: Could not read from remote repository.

Please make sure you have the correct access rights

[Ajay _view26_]

Hi @THIRUMALESH KODAGANTI 

A few things to confirm and try:

First, SSH keys don't count as users. You can have multiple SSH keys on a single account and they all authenticate as the same user, so having three keys on your machines is not the problem.

Second, check your workspace's User Directory at Workspace settings → User directory (or go directly to `bitbucket.org/thiru-quant/workspace/settings/groups`). Verify that only your account appears. Sometimes old invitations that were never accepted still count as provisioned users. If you see any entries besides your own — even greyed-out invited users — remove them.

Third, the Free plan user limit is 5 users, and your billing shows Quantity: 1, so you're well under it. The read-only lockout with only 1 user and no overages on storage (the other trigger for read-only mode since the May 2025 Free plan changes) almost certainly points to a provisioning glitch on Atlassian's side.