Cannot Delete Workspaces

[Jonas Lundh]

Hello everyone and someone :)

I'm member of two workspaces.

• Workspace 1, I'm the "organizational admin". The owner/creator has left the workspace.
• Workspace 2, has only 2 members including me. The owner/creator has left the workspace as well, but has been used by me only.

These workspaces will not be used anymore and I would like to remove these.
For Workspace 1 I have been able to remove repo and project but cannot delete the workspace.
For Workspace 2 I cannot do anything. The last of my commits are dated 2024.

These two workspaces were a fork only from another workspace that have now fully become the original, where commits are done on a daily basis.

[Syahrul]

Hey @Jonas Lundh 

As Prasanna mentioned, it’s likely that you only have permissions at the project or repository level. If you can see the workspace settings, that means you’re a workspace administrator and should be able to delete them. If you can’t see the workspace settings, then you’re not a workspace admin.

Also, if you are not the workspace admin, you can't do anything there except leave the workspace. Only the workspace admin can delete the workspace.

I hope this helps.

Regards,
Syahrul

[Jonas Lundh]

Thanks @Syahrul and @Prasanna Ravichandran for your answears.

On Workspace 1 I can access the Workspace setting but cannot see "Delete Workspace" as in:

https://support.atlassian.com/bitbucket-cloud/kb/how-to-delete-bitbucket-cloud-workspace/

Is it possible to raise an Atlassian support ticket to request removal of the workspaces, due to the fact that there are no administrators left and the workspaces are not used. If so, how do I create such request?

[Prasanna Ravichandran]

Hi,

If the original workspace owner has already left, the main thing to verify is whether you still have the exact workspace admin / owner-level permissions needed to delete it, because being an org admin does not always give full control over every Bitbucket workspace action. For the workspace where you cannot delete projects or repositories either, it is likely a permissions or ownership state issue rather than a repository activity issue. At that point, the practical next step would be to check the workspace membership and admin roles, and if no active owner can manage or delete it, raise a request with Atlassian support so they can review the orphaned workspace state.