nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

2FA issue with Atlassian

Riley PICU

My Trello account requires a code from an email when logging in via a computer. I would like to disable this. I have been told it's set up through Atlassian. When I log in to Atlassian, 2FA is not active (it appears to be disabled). I can't figure out how to disable 2FA in my Trello account. And neither service appears to have actual people to help. And I get the same information over and over and what to do which clearly isn't working. It's an older Trello account. I read something about "legacy" but still no instructions on how to fix the issue.

Please advise.

Accepted answers

All comments

Matthew Sinclair

A quick google shows that it requires Atlassian Support to get involved - they trigger an event that requires you to respond to an email.

https://support.atlassian.com/contact#/

I'd suggest starting there - or waiting for one of them to show up here which may take longer.

Carlos Garcia Navarro

Hi @Riley PICU ,

What is the exact message that you see? From this doc: https://support.atlassian.com/trello/docs/troubleshooting-two-factor-authentication

Nearly all Trello users will use their Atlassian account and Atlassian two-step verification settings to access Trello. If you haven’t logged in to Trello in a long time, your account may still be using Trello’s legacy two-step verification.

Try the Atlassian account recovery steps first.

Trello’s legacy two-step verification will ask for a “Two Factor Authentication Code” and have a checkbox with the option “Don’t ask for codes when I log in on this device.” If you see this and your legacy Trello two-step recovery codes are not working, please contact support.

You could also try a passkey, if this is a personal account:

Sign in once and open Atlassian security settings, using the same email address as your Trello account.
Under Passkeys, select Create and manage passkeys, then Register key.
On your next login, go to Atlassian login, select Passkey, and then open Trello.

Atlassian documents passkeys as an alternative that uses your computer’s PIN, fingerprint, or other device security instead of a password and 2FA. This is a practical alternative to try; it does not switch off the email-verification policy. Passkeys are available only for accounts that aren’t managed by an organization.

Riley PICU

We log into this account all the time. That is not an issue. It is not personal so I do not want a passkey.

When I log-in from a location that I have used recently, it will ask me about 2FA and allow me to decline. Then nothing else is required and it works fine.

However, when I log in from a "new" location, that does not happen. After I input the password it says:

We've emailed you a code. We require additional verification to protect your account. Check your email to continue: email address. Verification code followed by 6 empty boxes. The website at that time is: id.atlassian.com. There is no choice in the matter. This is what I want to disable. But can't figure out how to.

Anwesha Pan

Hi @Riley PICU

Here are few steps you could follow to stop the prompt every time (w/o 2FA or passkeys):

1. Check browser cookie & privacy settings

If your browser deletes your session cookies when closed, Atlassian treats every visit as a "brand-new unknown device":

Chrome/ Edge/ Firefox: Ensure "Clear cookies and site data when you close all windows" is disabled, or add an exception to allow cookies for:
- [*.]atlassian.com
- [*.]trello.com
Private/ Incognito Windows: Try not to log in via Incognito mode if you want the session remembered.

2. If you are already using social sign-In (Google/ MS/ Apple SSO)

If your Trello email matches a Google, Microsoft, or Apple account:

Click "Continue with Google" (or Apple/Microsoft) on the login screen instead of typing your email and password. When you authenticate via third-party SSO, Atlassian delegates identity trust to that provider and skips its internal email OTP verification check entirely.

3. Use the Dedicated Trello Desktop App

If web browsers continue to purge your session tokens, installing the official Trello Desktop App (macOS / Windows) maintains long-lived persistent auth tokens in local OS storage, keeping you logged in indefinitely without frequent web session re-authentications.

I hope this helps & resolves your issue. 🙂

Thanks,
Anwesha

Riley PICU

These are work computers. I don't have admin access to do 1 or 3. Maybe 2 is an option. Will have to look into it.

Anwesha Pan

Try option 2 and let me know if it worked for you @Riley PICU

Riley PICU

It works on my home computer but not the work desktop. Message: Couldn't sign you in. Google couldn't verify this account belongs to you.

Riley PICU

@Anwesha Pan

It works on my home computer but not the work desktop. Message: Couldn't sign you in. Google couldn't verify this account belongs to you.

Any other suggestions?

Anwesha Pan

Hi @Riley PICU

Sorry for the delayed response since Friday I was out.

Looks like might be your enterprise-managed browsers are enforced with restrict sign-ins to company Google accounts only, which might be blocking personal Google/Gmail accounts.

Below are few suggestions to bypass the Google authentication:

Set a direct Atlassian password
1. Go to —> Security and set or change your Atlassian account password. (Alternatively, from the Atlassian/Trello login screen, enter your email and click Forgot password to create one).
2. On your work computer, go to —> Trello —> enter your email —> click Continue, and type your Atlassian password directly instead of clicking "Continue with Google".
Enable an Authenticator app on your Atlassian account: You can try to set up an authenticator app (like Google Authenticator, Microsoft Authenticator, or Authy) under id.atlassian.com/manage-profile/security, Atlassian will send the 6-digit code on your phone rather than relying on email codes.

Let me know if any of these worked. 🙂

Thanks,
Anwesha

Riley PICU

I tried suggestion 1. It did not work. Still sent the email for code verification.

I don't know if I can try suggestion 2 as it's a group account which means lots of different phones. We use Microsoft Authenticator for other things so everyone already has it, but will it always send the authentication to the same phone? Mostly likely mine.

I tried to set it up. It's for an individual phone so does not look like it would work for a group.

Anwesha Pan

Hi @Riley PICU

Even on typing the password it didn't work?

Does everyone share the same account? If you are trying to access your own account then the code for MS authenticator should go to your phone only.

Riley PICU

@Anwesha Pan I tried in Microsoft Edge with the new password and it worked. But then tried in Google Chrome and it sent the email with the verification code.

Yes, everyone is sharing the same account.

Anwesha Pan

Atlassian Identity monitors device fingerprints, browser cookies, IP addresses, and geographic locations. If Microsoft Edge already had a trusted session or existing authentication token, Atlassian allowed login with just the password. Now when you open Google Chrome, Atlassian’s security engine flags the attempt as a new/unrecognized device and automatically issues a step-up verification code to the registered email address to prevent account takeover.

Since you are sharing a single Atlassian/Trello account across multiple team members triggers these security challenges.

I would recommend:

Switch to individual free accounts rather than sharing credentials. Invite each team member’s email address to the existing Workspace or directly to the relevant boards.
If account sharing cannot be avoided:
- Use shared mailbox/distribution list. Change the account's primary email address to an internal DL or shared mailbox so that when the verification code is triggered, any team member currently logging in can retrieve the code directly without having to ask the account owner.
- Use Authentication App: enable 2-Step verification using an Authenticator app (e.g., Google Authenticator, 1Password, Bitwarden). By scanning the QR code into a shared password manager or multiple devices during initial setup, any team member can generate the 6-digit code instantly.