Can't Log Into Lattice (SSO or Invalid Token)

Workaround available Web, iOS, Android Updated October 21, 2026

Quick answer

Most Lattice login failures come from using the wrong login URL ([account].latticehq.com/login), an email that doesn't match your Lattice account, or an SSO setup where you aren't assigned to Lattice in your identity provider. Super admins can bypass SSO with a password.

Most likely fix: Use your company's login URL.

Symptoms

'Invalid token', wrong email/password, 'Cannot POST' or 'Not Found' after SSO, or admins locked out after an SSO certificate expires.

Why it happens

  • Wrong login URL
  • Email in Lattice differs from the one you enter or the one in your SSO provider
  • User not assigned to the Lattice app in the identity provider
  • ACS URL typed with stray spaces
  • Expired SSO certificate with forced SSO login
  • Lattice login incident

How to fix it

Try these in order — the most common fix is first.

  1. 1. Use your company's login URL

    1. Go to [account name].latticehq.com/login with your company's account name
  2. 2. Reset password or verify email

    1. Ask your Lattice admin or IT to reset your password
    2. Ask the admin to confirm the email on your Lattice account matches what you type
  3. 3. Fix SSO (admins)

    1. Confirm the user is assigned to Lattice in Okta/Entra/your SAML 2.0 provider
    2. Check the ACS URL has no leading/trailing spaces
    3. Re-upload the IdP XML metadata if errors persist
    4. If forced SSO locked admins out after a certificate expired, sign in as a super admin with password or contact Customer Care
  4. 4. Check status

    1. Visit status.lattice.com for login incidents

This guide also covers

  • can't log into lattice
  • lattice sso not working
  • lattice invalid token
  • lattice login

Still not working?

If Lattice keeps failing, you're not alone. See every Lattice problem users report or the alternatives people switch to.

Other Lattice errors