Forums

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

Impact of linking multiple isolated Bitbucket workspaces to a single Organization

sharma-akshay
I'm New Here
I'm New Here
Those new to the Atlassian Community have posted less than three times. Give them a warm welcome!
January 15, 2026

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.

1 answer

0 votes
Aron Gombas _Midori_
Community Champion
January 16, 2026

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.

Suggest an answer

Log in or Sign up to answer
DEPLOYMENT TYPE
CLOUD
PRODUCT PLAN
STANDARD
PERMISSIONS LEVEL
Product Admin
TAGS
AUG Leaders

Atlassian Community Events