Can't sign in? Troubleshooting login and 2FA

Current sign-in works one of two ways depending on how your workspace is set up: a password plus a second factor (the emailed code, or an authenticator app or passkey once you have one), or single sign-on through your identity provider (Microsoft Entra ID, Okta, Google Workspace). Most "can't log in" problems trace back to one of a handful of causes below.

Enter your email first. Current checks whether your domain is set up for SSO and, if so, redirects you to your organization's sign-in page automatically. Otherwise you'll sign in with your password.

1. 1
   Code not arriving

   Check spam first, codes come from Current's transactional sender. You can request a new code, but there's a short cooldown between requests, so repeated immediate clicks won't speed it up.
2. 2
   Too many wrong codes

   After several failed attempts, verification locks briefly as a precaution. Wait it out and try again with a fresh code rather than continuing to guess.
3. 3
   Still stuck

   Confirm you're entering the most recent code. Each one expires after a short window, so an older email in your inbox won't work.

If your workspace has turned on Duo sign-in, you see Approve with Duo Push and Enter a Duo passcode after your password. No push arriving? Check Duo Mobile, or type a passcode from it. Use an email code instead is always on the same screen. The first time you approve with Duo, Current also emails you a code once to link your Duo account; after that Duo is enough. A push you report as fraud pauses your sign-in for 15 minutes and tells your Tenant Admins. Setup is in "Duo sign-in: approve with Duo, email code as backup".

Nobody can change their own sign-in email. A Tenant Admin changes it in Users & roles, and nothing changes until you open the link Current sends to the new address and press its button. The link works once and expires in 24 hours. Until then you keep signing in with the old address; after it, only the new one works and each computer asks for a sign-in code once more. If the link expired or never came, ask your Tenant Admin to send a new one.

If your workspace signs in through an identity provider and you land on the "Sign in with single sign-on" page after typing a password, that is the mandate working: your address is on a domain the provider serves, so choose Continue with single sign-on. If the redirect itself errors, see "Set up single sign-on (Microsoft Entra ID, Okta, Google Workspace)" for the exact errors (a reply-URL mismatch, an unreachable metadata URL) and how a Tenant Admin fixes them; those are configuration issues on the provider's side, not something an individual user can resolve, so loop in your Tenant Admin. If the provider itself is down, a Tenant Admin gets in with a recovery code: see "If your identity provider is down: recovery codes and password windows".

If you land on a pending-access screen after signing in, it means Current recognized you but a Tenant Admin hasn't assigned you a role yet. Common right after a workspace turns on SSO, since the first sign-in and the role assignment are two separate steps. The screen checks automatically every few seconds and moves you into the workspace the moment you're approved, no need to keep refreshing manually.

If a Tenant Admin has deactivated your account, signing in takes you to a distinct "access turned off" message rather than the pending screen. This isn't a bug or a lockout to troubleshoot. It means access was intentionally revoked. Contact your Tenant Admin to be reactivated.