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

[s_mokhov]

@Yana -- that doesn't work for me; they all have repos and Academic status; I re-use them as needed for courses. To consolidate I need to move the repos, which is a much bigger task and even worse since no automation for the checkbox. I also see that the linked workspaces do not disappear from the list yet to link. Anyway, given lack of usability and time, I'll settle for multiple auto-created orgs and ask for support later when/if needed. Thank you.

[Yana]

@Puru Kovvuri 

Yes, this requirement applies to all team workspaces. We are starting with those on paid plans and shortly after all other plans will follow. 

In your case however, you do not need to worry, your colleague Thomas has already linked your Bitbucket workspaces to the Atlassian org of their choice, you are all set. 

[Jeff S]

We have an Atlassian Org using Guard that has all our company users in it.    We have a Bitbucket workspace that only has our users in it.  I've already linked that one and it's showing in Atlassian Admin.

We have a second Bitbucket workspace that is mostly our users but also has users from other Atlassian Orgs.  If I link this Bitbucket account to our Org what happens to users from other Orgs? 

If I don't link the second Bitbucket workspace and a new Org is created, what happens with our users?  Can a user be in 2 Orgs?  Do I have to configure and pay for Atlassian Guard on the second Org if I want to enforce SSO?

Thanks in advance,
Jeff

[Julie Leonard]

I am an org admin and am trying to set up the bitbucket product from our admin section. Another user (not an admin) had set up a bitbucket account before trying to be helpful, but they set it up incorrectly (naming, permissions). They have now deactivated that workspace and I am trying to start from scratch following the best practices I see here and other sources. However, now when I try to follow these instructions, it forces me to create another organization which I don't want and don't understand why that's needed. How can we get around and set up a new bitbucket workspace for our existing organization?

(PS: To anyone from Atlassian reading this: I tried to open a support ticket on this and went in several circles with AI agents, never getting to the point of actually being able to submit a ticket. It's been pretty frustrating.)

[Yana]

@Jeff S 

Thank you for your question. It is difficult to advise without understanding what you mean by "what happens to users from other orgs?". 
A single user cannot be claimed in 2 different orgs if they are on the same domain. 

Additionally, you cannot verify the same domain under 2 different orgs. 
I would recommend reviewing  these 2 documents: 
https://support.atlassian.com/user-management/docs/verify-a-domain-to-manage-accounts/

https://www.atlassian.com/software/guard/guide/organizations-domain-claim#what-is-an-atlassian-organization 

and then reach out to our support team for Atlassian Administration help and provide details on what you would like to achieve and that team of experts will be able to provide you with a solution that is specific to your company's unique needs. 

Thank you

[Yana]

@Julie Leonard 

I'm sorry that you didn't have a good experience trying to raise a support ticket. 

Let me have a member of our support team reach out to you and help you achieve your goal with creating a new Bitbucket workspace under a correct Atlassian Org. 

Thank you

[Jeff S]

Thanks for replying @Yana.  Looking at the link for "What is an Atlassian Org" I've confirmed our company has a single Org, linked to our domain, that all our users are under.   Our main Bitbucket workspace is already linked to our Atlassian Org.

We have a second Bitbucket workspace that has some of our users in, and some users from a couple of other government departments.   Those government departments will each have their own Atlassian Org.   If I connect our second Bitbucket workspace to our Atlassian Org will that cause any issues with the government users that are in their own Atlassian Org?

From what you've said in this comment https://community.atlassian.com/forums/Bitbucket-articles/Calling-on-all-workspace-Admins-Connect-your-Bitbucket-workspace/bc-p/3111396#M2550 it appears billing will be bought across to our Atlassian Org but the users won't be bought across.  Is this correct?   I can't have the government users lose access to our shared Bitbucket workspace.

[Yana]

@Jeff S 

By linking your second Bitbucket workspace to your primary company org, will not change user's apps  access at this time. Users that have access will continue to have access. 
Later this year, we will be migrating all workspaces to centralized user management.  We already offer it on demand too and it  doesn't require a down time. 

Once we migrate your users for the second workspace, those users that are not under your company domain will also be added to your Atlassian Org, but will not be managed, they will be considered External users https://support.atlassian.com/security-and-access-policies/docs/who-are-external-users/. 

As long as you do not remove their Bitbucket access after migration, their product access will not be impacted. 

Security policy is a separate issue and will not impact their current product access. 

Also remember, that if your Bitbucket workspace is on Premium plan, you can simply enforce requirement for 2FA to access the data hosted in Bitbucket under that workspace, that would solve the security policy issue. 
Currently linking both your Bitbucket workspaces to the same Org I believe should be the way to go. 

One thing to remember however, the external users that have access to any Atlassian product can be configured as billable and not billable under Atlassian guard, please read more here https://support.atlassian.com/subscriptions-and-billing/docs/manage-your-bill-for-atlassian-guard-standard/ 

Thank you