Overview
This article covers OAuth and SSO failures* in Ottili ONE — what happens when signing in with an external account ("Continue with Google", "Continue with Microsoft" or "Sign in with Ottili") fails or loops.
Everything happens in the Ottili ONE dashboard at [dashboard.ottili.one](https://dashboard.ottili.one). The public website (ottili.one) points to that dashboard for every authentication step.
Feature note:* Google/Microsoft OAuth and Ottili SSO are available where your workspace has enabled them*. What the Live, Beta, Private Beta, In Development, Planned and Concept status labels mean is described in [Understand feature status labels](/docs/understand-feature-status-labels). A provider may therefore carry the status Live, Beta or Private Beta depending on your workspace — the troubleshooting below applies regardless.
Prerequisites
Before you start troubleshooting, check these points:
- You are on [dashboard.ottili.one/login](https://dashboard.ottili.one/login).
- You know the email address your account is registered with.
- You know which provider your company has enabled for sign-in — if unsure, ask your administrator, see [Company and team](/docs/company-and-team).
Common OAuth and SSO failures
Sign-in cancelled
You closed the provider window or cancelled the flow in the provider.
What to do:
1. Return to the [login page](https://dashboard.ottili.one/login).
2. Click Continue with Google* / Continue with Microsoft* / Sign in with Ottili* again.
3. Complete the provider dialog this time.
Security check failed (state mismatch)
The OAuth handshake expired or was interrupted (for example by navigating away or an expired cookie). The message often contains "state mismatch", "invalid state" or "security check failed".
What to do:
1. Fully reload the [login page](https://dashboard.ottili.one/login) (Ctrl/Cmd + R).
2. Close any open provider windows.
3. Start the login again and complete it in one flow without switching pages in between.
Provider temporarily unavailable
The provider (Google, Microsoft or Ottili SSO) is temporarily disabled for this dashboard, or the provider's service is not responding.
What to do:
- Use email and password* on the [login page](https://dashboard.ottili.one/login) as a temporary fallback.
- For known outages, check the [status page](https://status.ottili.one).
- If the provider is disabled permanently, confirm with your administrator which sign-in methods your workspace allows — see [Account and login](/docs/account-and-login).
Wrong provider (Google instead of Microsoft)
You try to sign in with the password field although the account is linked via Google/Microsoft — or the other way around.
What to do:
1. Check which provider the account was originally created with.
2. Use exactly that provider button, not the password field.
3. Does the account belong to a different company? Ask your administrator whether you should join via an invitation — see [Company and team](/docs/company-and-team).
Email addresses do not match
The provider account uses a different email address than your Ottili ONE account. Sign-in is rejected because the identities do not line up.
What to do:
1. Sign in to the provider (Google/Microsoft) with exactly the address linked to your Ottili ONE account.
2. If the address in the provider differs, ask your administrator to review the workspace linkage — see [Roles and permissions](/docs/roles-and-permissions).
3. If needed, sign in with email and password* and contact support.
Ottili SSO not configured (workspace side)
"Sign in with Ottili" does not appear, or fails with a configuration error. This usually means SSO is not yet enabled or not correctly configured in your workspace.
What to do:
- Ask your administrator whether Ottili SSO is enabled for your company.
- SSO is available where your workspace has enabled it*; until then use email/password or another enabled provider.
- More on how feature visibility depends on the status label in [Understand feature status labels](/docs/understand-feature-status-labels).
Fall back to email and password
If OAuth/SSO keeps failing, the regular login gets you back in.
What to do:
1. Open [dashboard.ottili.one/login](https://dashboard.ottili.one/login).
2. Sign in with the email registered to your account and your password.
3. Use Forgot password* if the password no longer works.
Status labels for OAuth and SSO providers
OAuth and SSO providers can carry different statuses depending on your workspace. The labels mean:
- Live* – generally available and fully supported.
- Beta* – publicly available in a pre-release state; may still change.
- Private Beta* – available only to an invited group.
- In Development* – actively being built, not yet available.
- Planned* – scheduled but not yet started.
- Concept* – early idea under consideration.
A provider in Beta or Private Beta may still change (paths, fields or limits). Details on all labels and where you see them are in [Understand feature status labels](/docs/understand-feature-status-labels).
When to contact support
Contact support when:
- OAuth/SSO keeps failing despite the correct provider and a verified email,
- the provider is shown as unavailable permanently,
- an email linkage does not match and you cannot resolve it yourself,
- you suspect SSO is misconfigured in your workspace.
Open support at [ottili.one/support](https://ottili.one/support) and provide your workspace domain, the surface, the exact message, the provider used and the timestamp. For known outages, check the [status page](https://status.ottili.one) first. Report security incidents via [Report a vulnerability](/docs/vulnerability-reporting).
Related articles
- [Login and session failures](/docs/login-and-session-failures)
- [Account and login](/docs/account-and-login)
- [Troubleshoot first sign-in](/docs/troubleshoot-first-login)
- [Verify your email](/docs/verify-your-email)
- [Missing product access](/docs/missing-product-access)
- [Understand feature status labels](/docs/understand-feature-status-labels)
- [Roles and permissions](/docs/roles-and-permissions)
- [Public API authentication](/docs/public-api-authentication)
- [Privacy controls](/docs/privacy-controls)
Was this article helpful?