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

How to create Bitbucket cloud site that is owend by my organization?

This questions is about Bitbucket cloud, your website won't let me select BitBucket Cloud as the product to create a question about.

I need to know how I should create a Bitbucket Cloud site for my organization, I don't want my email to be the sole owner of the Bitbucket cloud site, should I use a generic email from my Organization to create the Bitbucket cloud site?



2 answers

From an organization view you don't expect accounts, workspaces, repos or any other object to be "owned" by an individual.  These items may be "managed" by an individual, with the explicit expectation that the management of that object can be transferred to another admin/manager.

Ownership implies more than responsibility, in implies claim to property.  For organizations to use this product, the terms should be more aligned with organizational language and usage.

0 votes

Hi Chad,

You can first create a Bitbucket Cloud account with your company email. When you do, a workspace will also get created for your account. The workspace is like a container which contains projects and repositories.

Afterwards, you can create a separate workspace for company purposes. While you are logged in to your account, got to, select the plus sign + from the left hand column and then > Create workspace. If you navigate to its Settings > User groups you can add more users as administrators, and any admin is also considered an owner. I suggest a second workspace, so that it's different from the one created automatically for your account.

If you want to have a paid plan for the company workspace, you can also change or add billing and technical contacts for the license of the workspace in

You can always use a generic email to create a Bitbucket account and use the workspace that comes with that. However, if you add more admins in any workspace, they will be considered owners as well.

Please feel free to let me know if you have any questions.

Kind regards,

I have a follow up question:

Once someone gets added as admin to any workspace, I believe that person (also an owner) can create multiple other workspaces within that company's account. Now those new workspaces can only be seen by users who are added to it by the original creator/owner. 

If a specific user of any of the subsequently created workspace is marked as Admin, that person can create further workspaces, under the company's account. This process can go on and many many workspaces can be created.

Now the original user or the person who created the company's account and first default workspace would not know if such additional workspaces exists (unless admins of such workspace adds the original user to them)

Typically the original user should be in charge of managing all the workspaces as well as the company's account on behalf of the company. But it appears that's not the case.

Is my above understanding correct?

Hi @Shad,

  • When someone sings up for a Bitbucket Cloud account, a workspace is automatically created by Bitbucket for that user.
  • Afterwards, this user can create additional workspaces as well.
  • It is correct that these workspaces can be seen only by this user, and any users who are added by the original creator/owner.

I understand the concern you're raising here. Would it be useful to have the option to prevent managed accounts from creating additional workspaces?

A similar request has been made by other customers but regarding repositories, i.e. give admins the ability to prevent certain managed accounts from creating repos in their personal workspace:

If you'd be interested in a way of restricting the creation of additional workspaces, please feel free to let me know and I can create a feature request for our development team to consider.

Kind regards,

Suggest an answer

Log in or Sign up to answer

Atlassian Community Events