Account locked to Google SSO after Loom migration – password login not available

Question

My Loom account was migrated to Atlassian and my Atlassian account is now enforced to use Google SSO only.

I can successfully set a password in the Atlassian account hub, but when I attempt to log in, the password field is never shown and I am forced to continue with Google.

This indicates my account is still flagged as externally authenticated via Google.

I need Atlassian identity support to remove Google as the enforced authentication method and enable email/password login.

I am unable to submit a support ticket because I do not have an Atlassian site, and the contact form redirects me to the community.

Christine Callender · Answer

Thanks for the response. I want to clarify that I am the Atlassian organization admin for this account, and there is no other Jira or Atlassian administrator.

I have confirmed:

I did not intentionally enable Atlassian Guard

There is no directory sync configured

There are no authentication policies that I can modify or disable

This account originated from a Loom-only migration, not a Jira/Confluence organization

Despite this, my account is still being enforced to use Google SSO only. I can set a password successfully, but password login is not presented at sign-in and I am forced to continue with Google.

I am also unable to submit a standard Atlassian support ticket because this account does not have a paid Jira or Confluence site, and the contact form redirects me to the community.

This appears to be a residual identity/SSO enforcement from the Loom to Atlassian migration, not an org-configured policy.

Please escalate this to Atlassian Account and Identity Support to review and remove the enforced Google SSO flag on my account, as this is not something I can manage as an admin.

Thank you!!

Alex Ortiz · Answer

@Christine Callender

You should reach out to your Jira/Atlassian administrator.

They most likely just purchased/enabled Atlassian Guard which configures SSO.

Your account (email) is most likely in a group that is being synced with Guard.  As a result, the authentication policy is affecting you and forcing you to SSO.

Atlassian wouldn't be able to help you here as this is an org policy that your company configured.  They'll most likely just redirect you to speak to your Atlassian admin.