Skip to main content
Common issues logging into the Komo admin portal — invite links, Google SSO, seat limits, and password resets — and how to resolve them.

​
Invite and activation

This happens when your Komo account was created via email + password — typically by accepting an invite with the “Sign in with password” option — and you later try to sign in with Google. The two identities are not automatically linked, so Google login refuses.To fix:
  1. Sign in with email and password as usual. (Reset the password first if you do not have it.)
  2. Once signed in, open My profile in the admin portal.
  3. In the Add connections section, click Connect next to Google (or Microsoft) and complete the OAuth flow.
  4. From now on, either sign-in method will work.
When accepting a Komo invite for the first time, click Sign in with Google on the invite acceptance screen rather than setting a password. This creates the account with Google already linked, so you do not have to link it afterwards.
Go to the portal login page and click Forgot password? — Komo will email you a reset link. If the email does not arrive within a few minutes, check spam and confirm you are using the email address associated with your Komo account.
Never send your Komo password over email, chat, or Slack. Komo staff will never ask for it. If someone asks you to email or DM a password, treat it as suspicious.

​
Workspace access

If you can log in but no longer see a workspace you previously had access to, the most likely cause is a seat limit on the workspace subscription. When a workspace is at its seat cap and a new admin is invited, an existing admin can be silently removed to make room.A Company Owner can check current seat usage under Company settings → Billing. If your seat was removed in error, ask a Company Owner to re-invite you.
Yes. A Company Owner can restrict which login methods are allowed for the whole company:
  1. Open Company settings → Company Members.
  2. Scroll to the Allowed Login Types panel.
  3. Toggle Email/Password, Google, or Microsoft on or off.
Changes take effect on next sign-in. Any admin who tries a disabled login method will be blocked.
Before disabling a login method, make sure every admin on your company has linked at least one of the remaining allowed methods under My profile → Add connections — otherwise they will be locked out.
The admin portal supports Google and Microsoft login via OAuth. Okta, Auth0, and generic SAML SSO for the admin portal are not currently available.If you need SSO for end users (the hub side, not the admin portal), Komo does support OAuth SSO integration with providers like Auth0 and Google via the OAuth Single Sign On integration. This is a separate product surface to admin login.
Two things to check:
  • Confirm you are on the correct data-region login page. Komo has separate portals for US1 (app.us1.komo.cloud) and AU1 (app.au1.komo.cloud). Your account exists in only one region.
  • If your account was originally created via Google SSO, resetting the password may not link a password login until you accept the reset flow all the way through. Try clicking the reset link again and following it end-to-end without opening any other Komo tabs.
If neither resolves it, contact [email protected] with the email address on the account.