Impact of linking multiple isolated Bitbucket workspaces to a single Organization

[sharma-akshay]

We currently have multiple Bitbucket workspaces that operate independently, each with its own users, admins, billing, and repositories. For example:

• Workspace A – 40 users, Admins A & B

• Workspace B – 14 users, Admins C & D

• Workspace C – 4 users, Admin E

These workspaces are completely isolated: users from one workspace do not have access to repositories in another.

With Bitbucket’s new Organization model, we would like to understand how this setup will be affected if we create a single organization under our company name.

Specifically, we would like clarity on the following:

1. Will the existing workspace admins (A, B, C, D, E) continue to fully manage their own workspaces and repositories after linking them to an organization?

2. Will organization-level admins have visibility into or administrative control over all repositories across all linked workspaces?

3. How will billing work once workspaces are linked to an organization? Will billing remain at the individual workspace level, or will it be consolidated at the organization level?

4. Can we ensure that users and admins from one workspace cannot see or access repositories in other workspaces, even when all are linked under the same organization?

5. If we choose not to create or link to a central organization, what organization (if any) will Bitbucket associate with these workspaces by default?

We want to understand whether moving to the Organization model preserves the current isolation, administration, and billing structure between our teams.

[Ben]

Hi @sharma-akshay 

To answer your queries:

1. Yes, workspace admins still handle the assignment of permissions for user groups within a workspace, primarily via project permissions. Invitation of new users/syncing users from iDP/general user management is handled in Atlassian Admin.

2. For control over both the users and their permissions within the workspace as well as access/control over the content within the workspace, a user must be both a workspace admin as well as be an organisational admin for the org. 

3. Plan management/usage details are handled in the Atlassian Admin console, but the billing is still on a per-workspace model - it is not consolidated per org

4. Permissions within Bitbucket Cloud (assigned by the workspace admin) will prevent users from being able to access Bitbucket Cloud content

5. More details on this will follow closer to the migration date (which is still TBA)

To clarify, linking your workspace will change nothing in the UI or in the management of your users at this time. It is simply a pre-requisite step which will get your workspace ready for migration at a later date (TBA).

Hope this helps. If you have more specific queries which would warrant sharing sensitive data - I'd suggest you raise a support ticket directly using your paid workspace URL rather than sharing such details on a public forum such as community:

• support.atlassian.com/contact

Cheers!

- Ben (Bitbucket Cloud Support)

[Aron Gombas _Midori_]

We have only one Bitbucket workspace, but I noticed that after linking this workspace to the organization, I still have to manage groups (and memberships) on the Bitbucket side!

In case of Jira or Confluence, groups are managed under the administration interface of the organization, but Bitbucket seems to be an exception.

And if so, then I think admins of "A" and users of "A" will be separated from those on "B" and "C". Also meaning that linking did not change anything in this sense, within our organization.