Calling on all workspace Admins - Connect your Bitbucket workspace to an Atlassian organization

[#1]

Update as of September 8, 2025

For workspaces that are not yet linked to an Atlassian Org, we have implemented a reminder UI modal for workspace Admins.  To avoid interruptions please take the time now to link your workspace, by doing so you will shortly be able to benefit from: 

• Centralized user management

• A unified billing experience. To learn more, please visit this blog post

• Rovo Dev AI capabilities to streamline development

  • Code Reviewer

  • Set up Rovo Dev Agents

• The upcoming Bitbucket Packages feature includes support for Docker images via a built-in container registry

  • This new feature will enable smooth storage, management, and deployment of containerized applications, all from within Bitbucket Cloud – avoiding the need for expensive third party solutions

• Workspaces not linked to an Org will not be able to install Forge Apps

----------------------------------------------------------------------------------

Hello Bitbucket Community,

We are significantly enhancing Bitbucket Cloud by deepening its integration with the Atlassian platform, providing our customers with a more unified experience across all Atlassian cloud products. Our primary goal is to enable administrators within your Atlassian organization to manage Bitbucket Cloud users, permissions, and billing alongside your other Atlassian flagship products, all directly within Atlassian Administration. Furthermore, this centralizes your organization's content to unlock enhanced benefits with Atlassian AI.  

Who needs to take action?

If you’re an admin of a Bitbucket Cloud workspace that is on Standard or Premium plan, please link your workspace to your company’s Atlassian organization.

Note: To link your workspace to an Atlassian organization, you need to be a Bitbucket workspace admin and an Atlassian organization admin.

Steps to link your workspace to an Atlassian Org

Please follow the steps in Add a new Atlassian app to your organization | Atlassian Support or use the steps provided below to complete the linking process.

If you are a Bitbucket workspace admin and an Atlassian organization admin

1. Go to admin.atlassian.com.

2. Select the organization you would want to link your workspace to. (Note: Please only select the workspaces that you want to be part of your organization as you will not be able unlink them later.)

3. Once inside the organization, select Apps 

OR 

Under Apps, click Atlassian apps

4. In the upper-right corner, click "..." and then select Link Bitbucket from the dropdown menu

5. Click Next on the screen 

6. Select the workspace you want to link to your Atlassian organization. Note: You can only link one workspace at a time.

7. Confirm that this is the workspace you would want to link and click Link

8. Refresh the Apps view to see the newly added workspace on the list of available apps.

If you are a Bitbucket workspace admin but not an Atlassian organization admin

1. You will need to reach out to your organization’s admin.

2. Either ask them to make you an org admin, or follow the steps provided below to add them as a workspace admin to your workspace so they can complete the linking process.

   1. Go to Workspace settings.

   2. Select User groups.

   3. Select the group with the Admin lozenge associated with it.

   4. Select Add members in the upper-right corner.

   5. Enter the user’s email (or multiple emails if sending to multiple administrators).

   6. Select Confirm.

   7. The user(s) will receive an invitation email to join the workspace as an admin.

Once those steps are completed, they can follow the steps outlined in the “If you are a Bitbucket workspace admin and an Organization admin” section above to link your workspace to an Atlassian organization.

Not sure if you already have an Atlassian organization?

1. You can verify whether or not your company already has an Atlassian organization by going to https://admin.atlassian.com/.

2. If you are not part of any organization, you will see a prompt to create one 

you can also follow the steps outlined in our help documentation. 

3. When prompted, you can take a tour or close it 

4. From the Atlassian Guard Standard screen, select a trial or click X to skip.

5.  Once the org is created, follow the steps outlined in the section “If you are a Bitbucket workspace admin and an Organization admin” to link your workspace to an Atlassian organization.

Eligibility

Only workspaces that are eligible to be linked will appear in the list under ‘Select a workspace to link’.

If your workspace isn’t listed, it’s not yet eligible. Don’t worry—you’ll receive a notification when it becomes eligible.

For our customers with Atlassian organizations that are still on separate user management (or original user management), please follow this public feature request

AX-472 

to get progress updates on when your organization will be able to benefit from managing your users across all your Atlassian Cloud products in a unified manner.

FAQ

1. Is this step mandatory to continue using BB ?
   Linking your Bitbucket workspace to an Atlassian organization is required. Taking action now will also help you maintain uninterrupted access to the product and benefit from new upcoming enhancements.

2. What happens if I don't link my workspace ?
   If you do not link your workspace to an Atlassian org, Admins will experience a temporary interruption in your ability to administer your workspace until the linking process is completed. Taking this step promptly will help ensure continued access and a seamless experience.

3. If my company has multiple Atlassian Organizations, which Organization should I pick to link my workspace to?
   To best support centralized user and billing management across your Atlassian suite, we recommend selecting an Atlassian organization that already serves as your primary hub for flagship products like Jira and Confluence Cloud, and where you have existing integrations with Active Directory for user management. Consolidating your cloud products under a single Atlassian organization not only streamlines user and billing administration, but also unlocks advanced capabilities such as Atlassian AI, powered by the Atlassian Teamwork graph.
   
   Administrators should also consider active integration between Jira Cloud and Bitbucket workspace when making a decision about which Atlassian Org to choose. Consolidating all your cloud products under a single organizational umbrella will greatly simplify the daily responsibilities of administrators.

4. Will we lose any Bitbucket features or have impact on users access by linking our workspace to Atlassian Administration?
   No, no features or user access will be impacted by taking this step.

5. What is the role of Atlassian Organization Admin?
   Within Atlassian Organization, Admins have multiple roles, please refer to https://support.atlassian.com/user-management/docs/what-are-the-different-types-of-admin-roles/ to learn more.

[Jimi Wikman]

Very nice!

[Daniel SHEN]

where can I find this "In the upper-right corner, select ..."?

[furkan_eryilmaz]

For people that cannot find it with the instructions above:

I found it under Products -> ... (next to Add product) -> Link Bitbucket

[Yana]

@Daniel SHEN 

When you access your Atlassian Org from admin.atlassian.com > Navigate to Apps or Products on the horizontal navigation menu and you should see a "..." per screen shot below. Hope this helps clarify. 

Thank you. 

[Marco Cornelio]

Why exactly is there a specified date of September 2nd to link the two? Will you not be able to do this after Sept 2nd? What if you become a new customer after this date? It seems strange that Atlassian would set and arbitrary time limit to link to of their products.

[Daniel SHEN]

@Yana good news is I found it, bad news it I found it on the wrong organization... and linked it to that wrong organization! so the UI display in two of my organizations are different, only one of them has that ... button and the other simply doesn't. Moreover when I was searching on web to find out where that ... button is, one link directly took me to the page that has the ... button, without letting me select organization, it's just so subtle that I didn't notice the fact it's not the intended org. 

To make it worse, Atlassian even deliberately made it an one-way trip, now I'm stuck with this wrong linkage. The overall UI design in the admin area is a nightmare, I found it hard to believe that a company with a reputation in software engineering can make such a mess of it. 

[Yana]

@Daniel SHEN 

I'm sorry to hear that you linked your Bitbucket workspace to a wrong Atlassian Organization. 

let me ask our Support team to help you get untangled and get you on the right track. 

Please look out for a ticket from us. 

Thank you

[Daniel SHEN]

I've reached out to support team and they've successfully unlinked my workspace, many thanks @Yana !

[Yana]

@Marco Cornelio 

Thank you for your question, I have updated my post to add an FAQ, that should help answer your question. 

Thank you 

[bcrabb]

we use atlassian admin to enforce SSO for jira/confluence/etc

if we onboard bitbucket, will those SSO authentication requirements be automatically applied to the bitbucket environment?

[Yana]

@bcrabb 

Authentication via SSO is done through Atlassian account, so this applies to all users regardless of product access. However product access and groups synching with your AD provider will not yet be supported with this initial step of linking your Bitbucket workspace with Atlassian Org.  As a followup step, our team will be onboarding your Bitbucket workspace to Atlassian Administration for centralized user management. 

If you would like to join our EAP program to fully onboard your workspace to Atlassian Administration, please fill out this form and we will reach out to you separately. 

Thank you 

[jarney]

Does this mean that if users are part of two different Bitbucket workspaces, and then both workspaces are linked to the Atlassian organization, that the same user still gets billed twice, once for each workspace?

[Yana]

@jarney  

Bitbucket billing doesn't change with either linking of the workspace or migrating users to Atlassian Administration. Each user is billed based on product access and license they consume within each workspace.  

If you have 2 separate workspaces right now, they are billed separately and linking both to the same Atlassian Organization doesn't change that. 

And by linking both Bitbucket workspaces to the same Atlassian Org will soon allow you to see billing across all your Atlassian products in Atlassian Administration without having to navigate to multiple workspaces. 

[EC]

Hi Atlassian Team!

If I do not want to manage users and payment through Atlassian do I need to pay extra for Atlassian and need to link my bitbucket workspace?

All we need is to keep using Bitbucket, our paid plan with this is more than enough for how we use it.

In the FAQ above it mentions we need to link our Bitbucket workspace to avoid 'temporary interruption in our ability to administer our workspace until the linking process is completed'. When i go to link it though, I am prompted to select another payment plan with Atlassian even though I have no use for any of the changes apart from using Bitbucket (which we already pay for). 

[Yana]

Hi @EC 

Linking your workspace to Atlassian organization is completely Free, you do not need to pay anything extra. 

Signing up for an Atlassian org for your company, if you do not already have one, is also free and doesn't require a payment method. 

Please reach out to our Support team if you need help with any of the steps and they will be happy to assist you. 

[Joe Lupfer]

Our company got the Email directing us to link Bitbucket to our organization which currently has JIRA.
During the process though I see this concerning message:

Link Bitbucket

You won't be able to administer users, groups, and access for this workspace in Atlassian Administration. You also can't unlink this workspace or transfer it to another organization once it's linked.

The link at the end of the message doesn't explain how an administrator can manage users after linking Bitbucket.

We don't have a high turnover of Bitbucket users here but loosing the ability to manage users seems to be a non-starter.

Would you care to comment on this?

[Dave Biddle]

I found that on creating an organization we are entered into a free trial of Atlassian Guard. What  happens when that expires if we don't sign up for it?

We only use Bitbucket, we're a small team of developers at a busy agency and our primary concern is business continuity.

[Gen]

Hi Atlassian Community,

First of all, thank you for this great feature update! It’s exciting to see Bitbucket evolving steadily toward more enterprise-ready capabilities.

One of our customers currently manages Jira/Confluence and Bitbucket with separate administrators; their Corporate IT team manages Jira/Confluence, while Bitbucket is managed by their engineering department responsible for development activities. In this organization, users are not managed in an external Idp and are managed in Atlassian's internal directory.

With the upcoming requirement to link Bitbucket workspaces to an Atlassian Organization, they have the following concerns:

1. Does linking require that Bitbucket workspace admins also become Organization admins?
   If so, there is a concern that Bitbucket workspace administrators might be granted excessive privileges—such as permissions to configure organization-wide security policies or manage access to other Atlassian products—which may not align with their intended scope of responsibility.

2. Is it possible to continue operating with separated user and admin management (i.e. without linking), even after the September 2, 2025 deadline?

3. If linking is mandatory, is there a way to restrict admin capabilities so that administrators can only manage users and settings related to the specific product (e.g. Bitbucket), without broader organization-level access?

I'd also really appreciate hearing from others who are currently managing Bitbucket and Jira/Confluence separately—especially if you’ve been considering (or have recently gone through) the process of linking and unifying administration under an Atlassian Organization.

If you have any insights or ideas about how to maintain a clean separation of responsibilities after linking, I’d love to hear your thoughts!

Thank you in advance!

[Mat]

Okay - so you want us to jump through some more hoops. Whatever.

But we already pay on a per seat basis for our use of Bitbucket. By creating an organisation it looks like we have to sign up to pay for another per seat charge of $4 per month per user.

Please tell me I've got this wrong?

[gazj354]

More pointless nonesense from Atlassian.

We just want to get work done. Why do we have to jump through all of these steps for zero benefit?

[Yana]

@Joe Lupfer 

Hi there, 

By linking your workspace to an Atlassian org, you will not lose the ability to manage users in Bitbucket and at this time everything will remain the same. 

However by taking this fist and critical step you are: 

1. Creating a map to allow our team to then migrate your users and group to this Org that you chose, for centralized user management. Admins will be able to benefit from IDP integration for easy user management across all your Atlassian apps. Currently Bitbucket users are managed separately and we do not have a native integration with IDP. (if you are interested you can also join our EAP program to migrate your workspace users and group to Atlassian Administration by filling out this EAP participation form  )

2. Creating a map to allow our team to enable new billing experience for your team, to manage all your Atlassian apps, including Bitbucket from centralized billing in Atlassian Administration. 

3. Benefit from the value of Teamwork Graph by contextualizing content across all products within your Organization and for your team to benefit from improved visibility and efficiency. 

Please feel free to reach out to our Support team if you have further questions or need help.

[Yana]

@Dave Biddle 

You do not require a payment method to try our product. Once the trial runs out, and you do not wish to use the product, you'll just lose the features that Guard offers. It will not have an impact on your Bitbucket operation or workflows. 

[Yana]

@Gen 

Hi there and appreciate your questions. 

Here are the answers: 

• Does linking require that Bitbucket workspace admins also become Organization admins?
  If so, there is a concern that Bitbucket workspace administrators might be granted excessive privileges—such as permissions to configure organization-wide security policies or manage access to other Atlassian products—which may not align with their intended scope of responsibility.

In order to link your workspace to an Atlassian Org, the user must be an Org Admin and a workspace Admin. However that doesn't require then for the workspace Admins to become Org Admins. Atlassian Administration has a role of User Access Admin, this role allows users to manage product access but not have access to the product and doesn't require Org Admin role. To learn more please refer to this help document.

• Is it possible to continue operating with separated user and admin management (i.e. without linking), even after the September 2, 2025 deadline?

By linking your workspace, you will still continue managing users separately.  Please see my response above to Joe for more details. 

• If linking is mandatory, is there a way to restrict admin capabilities so that administrators can only manage users and settings related to the specific product (e.g. Bitbucket), without broader organization-level access?

Yes, please refer to the following help documents: 
https://support.atlassian.com/user-management/docs/what-are-the-different-types-of-admin-roles/ 

https://support.atlassian.com/user-management/docs/give-users-admin-permissions/

Thank you and please feel free to reach out to our Support team for help

[Yana]

@Mat 

Hi there, 

Creating an Atlassian Org is free and you do not pay for users in the Org. 

That might have been for a Guard subscription, which your team gets a free trial of for 30 days and you do not have to signup for it after the trial runs out.  

To learn more about an Atlassian Org please  refer to 

https://support.atlassian.com/organization-administration/docs/get-started-with-an-atlassian-organization/ 

and 

https://support.atlassian.com/organization-administration/docs/what-is-an-atlassian-organization/

Thank you 

[Mat]

@yana Okay, moving on from the Guard debacle - You appear to be saying that I have now to add every user onto the organisational panel by physically typing their email address? Doesn't bitbucket already have this information? Why do I have to enter it again?