Skip to content

I cannot sign in

/auth/login·/auth/callback·/auth/mfa-challenge

Lexpoint has no password, so almost every sign-in failure is one of four things: a link that is no longer valid, a link that never arrived, the wrong Google account, or a six-digit code that does not match. Each has a different fix.

Signing in normally is covered in sign in and account recovery. This page is for when it does not work.

Section titled “The link in my email took me to the sign-up page”

Cause. A magic link is single-use and time-limited. When you open one that has already been used — or one that has been superseded by a newer link you requested afterwards — no session is created. Lexpoint does not leave you on a dead screen: it sends you to the sign-up screen, and the address bar ends in ?error=no_session or ?error=auth_failed.

Nothing has happened to your account. The sign-up screen is a fallback destination, not a statement about your file.

The same thing happens if you request the link in one browser and open it in another — a link opened somewhere other than where it was requested cannot complete the sign-in.

Fix.

  1. Go back to my.lexpoint.io/auth/login.
  2. Enter the same email address and select Send Magic Link.
  3. Open the newest email. If several Lexpoint emails are in the inbox, only the last one works — every new link supersedes the one before it.
  4. Open the link in the same browser you requested it from. If your mail app opens links in its own in-app browser, copy the link and paste it into the browser where you use Lexpoint.
Where a stale magic link lands you — the sign-up screen, with the error code still in the address bar.
Where a stale magic link lands you — the sign-up screen, with the error code still in the address bar.

Cause. In order of how often it happens: the mail is in a spam or promotions folder, the address was mistyped, or you are watching a different inbox than the one on the account.

Fix.

  1. Search the spam and promotions folders for lexpoint. The confirmation dialog says Check spam folder if you don’t see it for a reason.
  2. Check the address in the dialog. If it is wrong, select Use a different email and try again. The email field validates as you type and shows a green checkmark when the address is well formed — but it cannot tell a valid address from your address.
  3. Wait for the Resend in 60s countdown to finish, then select Resend. The countdown exists to stop a double-tap from sending two links, which would make the older one useless.

If your address is right and nothing arrives after a resend, the block is on the mail side. Bring the exact address and the time you requested the link to Help & Support.

Continue with Google signs me in, but my file is gone

Section titled “Continue with Google signs me in, but my file is gone”

Cause. You are in a different Lexpoint account. A Google sign-in identifies you by the Google account’s email address. If that address is not the one your Lexpoint file was created with, you land in a second, empty account rather than yours — usually because a personal Google account was picked in the account chooser when the file belongs to a work address, or the other way round.

Fix.

  1. Sign out from the account menu.
  2. Return to the sign-in screen and use Send Magic Link with the email address you know the file is under. A magic link signs you into the account for exactly that address.
  3. Once inside, open Settings → Account → Sign-in & security. The Sign-in methods panel lists every method connected to this account — that is the definitive answer to which Google account belongs to this file. See sign-in methods.

The screen shows Invalid code. Please try again. and the boxes turn red.

Cause. Two-step verification codes are generated from the clock on the device running your authenticator app. If that clock has drifted by more than a few seconds, every code it produces is rejected, including the one currently on screen. The second cause is timing — a code lives for 30 seconds, and one typed as it rolls over will not verify.

Fix.

  1. Turn on automatic date and time on the device running the authenticator app, then open the app again.
  2. Wait for a fresh code to appear rather than entering one that is about to expire, and enter it promptly.
  3. Confirm you are reading the Lexpoint entry in the app, not another service’s.

Sign in with a different account, below the code boxes, does not help here — it abandons the sign-in and returns you to the start. Use it only when you have begun signing in as the wrong person.

If your clock is correct and fresh codes are still rejected, stop — you have lost access to the factor. Contact Help & Support. Identity is confirmed before two-step verification is reset, which is deliberate: an easy reset would defeat the protection. See two-step verification.

The sign-in buttons are greyed out, or a CAPTCHA message appears

Section titled “The sign-in buttons are greyed out, or a CAPTCHA message appears”

Cause. Two different gates disable the buttons.

  • A CAPTCHA that has not finished. The sign-in screen runs a background bot check. Until it completes you see messages such as CAPTCHA verification required. Please wait for verification to complete, then try again. or CAPTCHA token expired. The check also expires if the page sits open for a long time.
  • An unticked partner consent box. If you arrived through a partner or referral link, the screen shows a consent panel and both Continue with Google and Send Magic Link stay disabled until it is ticked. Attempting to submit shows Please accept the partner consent checkbox to continue.

Fix. For the CAPTCHA, wait for the checkmark and try again, or refresh the page if the message was Failed to load CAPTCHA. Please refresh the page. For the consent panel, read it and tick the box, or open my.lexpoint.io/auth/login with no partner code in the address to sign in without it.

Cause. The account’s assessment data was deleted. The screen reads Your profile has been removedYour assessment data in the app was erased and you were signed out — and it appears only after a deletion has actually run.

Fix. Your email address stays on file, and Sign up again on that screen starts a new account on the same address. What was deleted does not come back. If you did not request the deletion, contact Help & Support immediately with the date you last signed in successfully. See deleting your account.

Cause. Your session ended — it expired, or you signed out in another tab. Lexpoint does not strand you on a dead page: it sends you to sign in and remembers the page you were trying to reach, carrying that destination through the whole flow, including the six-digit challenge.

A session survives closing the tab and restarting the browser, so being asked repeatedly within a single day is not normal. If it keeps happening, note whether you are switching between browsers, profiles, or private windows — each is a separate session — before opening a ticket.

Open a ticket at my.lexpoint.io/app/tickets — from a device where you can still sign in, or by replying to any Lexpoint email — with:

  • The email address on the account.
  • Which method you used: Continue with Google or Send Magic Link.
  • The exact on-screen message, copied word for word.
  • The full address bar contents when it failed, including anything after ?error=.
  • The date and time you tried, and your time zone.

Frequently asked questions

I forgot my Lexpoint password.

There is no Lexpoint password. A client account signs in with Google or with a one-time link emailed to your address, and the sign-in screen has no password field — so there is nothing to reset.

My magic link sent me to the sign-up page. Has my account been deleted?

No. The link had already been used or was no longer valid, so no session was created and Lexpoint fell back to the sign-up screen. Return to the sign-in screen and send a fresh link.

Why does Lexpoint reject a code my authenticator app is showing right now?

A one-time code is derived from the clock on the device generating it. If that clock has drifted, every code it produces is rejected. Turn on automatic date and time on that device and try the next code.