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:
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?
Will organization-level admins have visibility into or administrative control over all repositories across all linked workspaces?
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?
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?
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.
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.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.