Confession time...

[#1]

As a Jira Administrator, I spend a lot of time in the Atlassian ecosystem, but until today I had no idea that I could link my personal Atlassian account with my company account.

I've been switching between accounts manually and just accepted it as part of my daily workflow.

After discovering the account linking feature, everything became much easier.

If you're struggling with multiple Atlassian accounts, don't worry. Take a moment to explore your account settings because there may be a much better way to manage them than constant sign-ins and sign-outs.

It's one of those small discoveries that can save a surprising amount of time and frustration.

Sometimes even experienced admins learn new tricks!

[Cengiz Akyildiz]

I still prefer to keep them separate. Once you merge them, your account becomes a managed account, and you lose some control over it. Depending on your organization's security policies, you may not even be able to spin up a new test instance to evaluate new products or apps. It's a trade-off: while merging can simplify account management, it also reduces your flexibility and independence. Cheers!

[Josh McManus]

Yes! Unfortunately this was a brand new feature and still had some bugs when I was getting laid off of my last job, meaning my community contributions ended up orphaned under my work user account. Be sure you do this before you need it!

Also, @Cengiz Akyildiz this really only applies to your Community user...you're not merging accounts, you're linking them together. You can have a Managed user linked to your Personal account and your Personal account remains as the "owner" of your community content. Your work account has its permissions and management and your personal remains separate and doesn't have an impact on the Atlassian apps.

[Cengiz Akyildiz]

Ok, this seems to be new. It looks like it could be a useful addition for community interactions. Thanks for the clarification, @Josh McManus 

There have been a lot of changes around accessing and managing Atlassian Cloud environments lately. Even the API landscape has become quite confusing—there are now multiple APIs for user accounts, and the right one depends on factors like the user type and an organization's user management strategy. Because of that, I'm still approaching these new capabilities with a bit of caution :)

[Viswanathan Ramachandran]

Hi @Sonal Malik 

It's a Aha moment. Personally, I would like to keep accounts separate. 

While this feature is cool, it is far too hidden.

• The Problem: Many users and admins confuse linking with merging and out of fear of mixing corporate and personal data, they resort to inefficient workflows (like constant sign-outs or multiple browser profiles). If you are currently active on your personal account (browsing the Atlassian Community) and you click a link to a corporate, the system breaks.

While organisations block certain controls with their security policies, for ex: you cannot access community portals from your corporate network. Instead, I also like to see a smart UX Bridge feature.

Rather seamlessly routing you, the system usually gives you a harsh Access Denied or 404 Page Not Found error. This would recognise that you have a linked corporate account in the background and say: "Hey, you cannot access your personal account from here" and vice versa, "You cannot access your corporate account from here". 

This would help the users trying to find risky workarounds.

[zoltanersek _outpostlabs_dev_]

I always enjoy discovering little small features that make my life better,

I'd love some improvement around clearer visibility into which identity is currently "active" myself

[Brita Moorus]

We’ve all had those “wait… this existed all along?!” moments 😅 Thanks for sharing, I’m sure this will save a few fellow admins some frustration 💙

[Dave Mathijs]

What are the benefits of linking your personal and work account?

I use the Atlassian Community with my personal account because I want to keep my contributions should I ever decide to switch employer.

On the other hand, many Atlassian Events / Webinars required a business email address meaning that if I register with my work account, I don't get kudos here.

What actually happens if you link both personal and work accounts? If you work account is managed and deactivated at a certain point, will you also lose access to your personal account?

[Kirstin Seidel-Gebert]

until today I had no idea that I could link my personal Atlassian account with my company account.

Interesting... how can you actually link accounts? I was only aware that you can link different instances under the same account and use the instance switcher.

Is it possible to link two business accounts, e.g. when you have an account at your own company, and another account at a client's instance?

[Becker_ Rene]

I understand the intent behind this feature but it's the same as with MS.

Personal and company accounts don't mix. Any data and security governance would having heart attacks discovering that this is actually used productively. Using one account over multiple tenants makes it even worse.

But what's more important to me: If you are using a different Identity Provider (for example Entra), it becomes messy. And if you handle all permissions via this IDP this feature causes only problems and some confusion.

For example:

External users (providers, sub-contractors, ...) have an account in our AD. We used to add their actual e-mail addresses in the mail-field (several reasons). Once they also use Atlassian somewhere else, the apps go boom-boom, provisioning breaks etc. In theory it should work but mostly it does not or causes random errors.

Retrogradely changing the user accounts to carry an address of our own, causes the Atlassian directory to also go boom-boom because, although it should only use SID (in case of IDP), Atlassian's products rely heavily on mail addresses.

So again ... I understand the intent but as always Atlassian did not think about IDP-managed accounts.

Great feature though for pure private accounts that work on public systems.

---

[Sonal Malik]

Hi @Dave Mathijs ,

Since I'm still fairly new to this, my experience is limited so far. However, if I post anything during office hours, I can still view it later from home using my personal account. I can also see all of my contributions from both accounts.

I haven't had the chance to test how Atlassian Events or webinars work in this setup yet, but I should know more within the next week.

I also have an open support ticket with Atlassian because, although I can see my credentials, I'm currently unable to download them using my personal account.

As far as I know, you can always delink the accounts if needed.

Update: I am able to download my credentials from both accounts successfully. 

[Sonal Malik]

Hi @Becker_ Rene , 

That's a very fair point, especially in environments that use Entra ID or other IDP-managed authentication and provisioning.

Just to clarify, my comments were specifically about the Atlassian Community experience and the ability to view contributions across linked personal and work accounts. I haven't used this feature in any enterprise, tenant management, or IDP-governed context.

I completely understand how account linking could introduce challenges around provisioning, email attributes, and identity management in organization-managed environments. For me, the benefit is mainly on the Community side, where it allows continuity of contributions and credentials while keeping participation tied to the same individual.

Thanks for sharing the real-world IDP perspective. It's definitely something Atlassian should consider as they continue to evolve the feature.

[Sonal Malik]

Hi @Kirstin Seidel-Gebert , 

My understanding is that it's more about preserving your Community identity, contributions, and credentials than linking access between different company instances. The value for me is that your knowledge sharing and participation in the Atlassian Community remain associated with you, even if you change jobs or work across multiple organizations.

[Sonal Malik]

Hi @Brita Moorus , 100%! 😄 It was a surprise discovery for me as well. If it helps fellow admins keep their Community contributions, credentials, and knowledge-sharing history connected, then it's a win in my book. 💙

[Sonal Malik]

Hi @zoltanersek _outpostlabs_dev_ , Totally agree! 😄 It's the little features that often have the biggest impact. A clearer way to see which identity is currently active would definitely make the experience smoother and reduce confusion when switching between accounts. 👍

[Sonal Malik]

Hi Viswanathan Ramachandran

Thanks for sharing your perspective. 😊

I agree that the feature is quite hidden and that many people may assume "linking" means "merging," which can understandably make them hesitant to use it.

I really like your idea of a smarter UX bridge. A more helpful message explaining why access isn't available, and guiding users to the appropriate linked account, would create a much better experience than a generic 404 or Access Denied page.

Personally, what I find most valuable about account linking is preserving Community contributions, credentials, badges, and knowledge-sharing history across different stages of your career, while still keeping personal and corporate accounts separate.

Your suggestion would help make that distinction much clearer and could prevent a lot of confusion and unnecessary workarounds. Thanks for highlighting this use case! 👍💙

[Sonal Malik]

Hi Cengiz Akyildiz

Thanks for sharing your perspective! 😊

One thing worth clarifying is that linking accounts and merging identities aren't necessarily the same thing. From what I've seen, the primary benefit is around maintaining continuity of your Atlassian identity, Community contributions, badges, and credentials, rather than combining access or permissions across organizations.

I completely agree that managed accounts come with organizational controls and security policies that may limit certain activities, such as creating test sites or experimenting with products. In those cases, keeping accounts separate can absolutely provide more flexibility and independence.

For me, the biggest value is on the Community and knowledge-sharing side. It helps ensure that the contributions, certifications, and reputation you've built over time remain associated with you, even if you change roles or organizations, while still respecting the governance policies of the organizations you work with.

Ultimately, I think it comes down to individual preference and organizational requirements. It's great that Atlassian provides options so users can choose the approach that works best for their situation. 👍💙