If you were invited to a Yoodli organization or your company uses SSO to sign in, you may run into one of the errors below. This guide walks through the most common causes and fixes, based on the join and sign-in issues our support team sees most often.
"Invitation to [email] was not found" or "Your account cannot be found"
This almost always means the invite hasn't actually been accepted yet, or the email on the invite doesn't exactly match the email you're signing in with.
Having the invite link in your inbox isn't the same as having accepted it. Open the invite email and click Accept Invitation (or Join Organization) all the way through — don't just navigate to app.yoodli.ai and sign in directly.
Double-check the invite was sent to the exact email address you're using to sign in. A mismatch (e.g. a personal Gmail vs. your work email, or a typo) will produce this error.
If it still fails, ask your organization admin to resend the invite from Organization Settings > Invites using the exact email address, then try again from a fresh invite link.
"Sorry, you don't have access to this organization" or you're seeing the free/individual version instead of your org's plan
Both symptoms point to the same root cause: your account was never fully linked to the organization.
This happens when the invite link was opened but not completed, or when you signed up for a personal Yoodli account before your org invite was accepted — Yoodli doesn't automatically merge the two.
Ask your admin to confirm your status on the Members tab. If you show as "Invited" rather than "Active," have them resend the invite and complete the acceptance flow again.
If you already have a personal account under the same email, let your admin know — they may need to add you to the org directly rather than through a fresh invite.
Signing in through SSO gives an error, but only sometimes
The most common cause is starting sign-in from the wrong place. Yoodli's SSO is SP-initiated, meaning you must start the login at Yoodli, not from your identity provider.
Do: go directly to https://app.yoodli.ai and sign in from there.
Don't: launch Yoodli from an app tile inside Okta, Microsoft Entra, Google Workspace, or a similar identity provider dashboard. IdP-initiated launches currently fail with errors like "I don't have access permissions" or "Something went wrong."
If your team is used to launching Yoodli from an IdP tile, point them to app.yoodli.ai instead as the standard entry point until IdP-initiated login is supported.
SSO errors persist even in a fresh/incognito browser window
If the issue isn't the entry point above, it's likely a configuration issue on the identity provider side. Have your org admin verify, in Organization Settings > SSO:
The SSO connection shows as both Ready and Published — "Ready" alone is not enough for members to sign in.
The SAML NameID is mapped to a valid email address.
The signing certificate is correctly copied/base64-encoded with no truncation.
The SP Entity ID and ACS/callback URL in the IdP exactly match the values Yoodli provided — trailing slashes or http vs. https mismatches are a common culprit.
See SSO and Sign-in Options for full setup steps.
Invite or password reset emails never arrive
This is usually corporate email filtering, not a Yoodli delivery issue.
Check spam/junk folders first.
Ask your IT team to allowlist @yoodli.ai and @speak.yoodli.ai.
If nothing arrives after allowlisting, have your admin resend the invite rather than requesting a second password reset — repeated resets don't help if the original email never left the send queue.
Still stuck?
If none of the above resolves it, contact Yoodli support with: the exact error message, the email you're trying to sign in with, whether your org uses SSO, and whether you were signing in from app.yoodli.ai directly or from an IdP tile. This lets us skip straight to the likely fix instead of re-running basic troubleshooting.