Troubleshooting Noibu Login and SSO Errors

Last updated: October 15, 2026

Most Noibu sign-in issues happen when someone uses a different sign-in method than the one their company has set up.

This guide helps you find the right method, fix the most common login and SSO errors, and know what to send support if you're still stuck.

Start with Identify your login method below before trying anything else. Using the wrong method produces errors that don't name the real cause.

Identify your login method

The Noibu sign-in page offers three ways in: Sign in with Google, email and password, and Sign in with SSO. Only one of them is right for your company.

The three sign-in paths

Your company's setup

How to sign in

What happens with another method

Your company requires SSO (Okta, Azure AD or another OAuth2 provider)

Sign in with SSO

Email and password, and Sign in with Google, won't get you into your company's Noibu account.

No SSO, and your Noibu email address is a Google account (for example, Google Workspace)

Sign in with Google

Email and password also works.

No SSO, and your email address isn't a Google account

Email and password

Sign in with Google fails, because it only works for a Noibu account that uses the same Google email address.

Check these 3 things first

  1. Does your company require SSO (Okta, Azure AD or similar)? If yes, Sign in with SSO is your only working option. Email and password fails even when the password is correct. Sign in with Google is not the same as SSO, so it won't work either.

  2. Is your Noibu email address a Google account? If yes, and your company doesn't require SSO, Sign in with Google works.

  3. Have you accepted your invitation and set a password? An invitation email doesn't create your login on its own. Click Accept invitation on the sign-in page (or the link in your invitation email) and set a password. You need to do this even if you'll sign in with SSO afterwards. If you skip it, SSO sign-in fails.

Important: To join your team, use Accept invitation, not the Create free account tab.

If your sign-in method worked before and recently stopped, your company has likely turned on SSO enforcement. Confirm with your IT team.

Signing in with enterprise SSO

  1. Go to console.noibu.com.

  2. Click Sign in with SSO. Don't enter your email and password, and don't use Sign in with Google.

  3. In Company domain, enter a domain your company has set up in Noibu, for example www.yourstore.com.

  4. Click Continue to SSO and sign in with your identity provider.

SSO configuration for IT teams

Set this up before you roll Noibu out to users. Several of the errors in this guide trace back to gaps in this configuration.

How Noibu SSO works

  • Noibu SSO is built on OAuth2 / OIDC, not SAML, so there's no SAML metadata URL.

  • SSO settings are in Settings → General / Term Usage → General. This is where you'll find Require OAuth2 Authentication, the OAuth2 fields (OAuth2 Issuer, OAuth2 ClientID, OAuth2 JWT Claim and OAuth2 Grant Type) and Verify / Update.

  • SSO enforcement applies to the whole company. Individual users can't be exempted.

  • SCIM provisioning isn't supported on any plan. Invite users from Settings → Teammates.

  • SSO sign-in asks for a company domain because one Noibu account can belong to more than one company. The domain tells Noibu which company's SSO to use.

Required configuration

  • Assign each user to the Noibu application in your identity provider.

  • Make sure the email addresses match. Noibu reads the user's email from the claim set in OAuth2 JWT Claim. That email must match the email address on the user's Noibu account, or sign-in fails.

  • Set up the Noibu MCP, if you use it. Set OAuth2 Grant Type to Authorization Code + PKCE, because the MCP doesn't support Implicit. Add https://mcp.noibu.com/sso/callback to your provider's Allowed Sign-In Redirect URLs. This only works once SSO is enabled for your company in the Noibu console. See SSO Authentication for Noibu MCP.

Troubleshooting by symptom

OAuth2 error after the SSO redirect

This error appears after you've signed in with your identity provider and are sent back to Noibu. Check these in order:

  1. You haven't accepted your invitation yet. Click Accept invitation on the sign-in page and set a password, using the exact email address your invitation was sent to.

  2. Your email addresses don't match. The email your identity provider sends to Noibu must match the email on your Noibu account. If they differ, ask the teammate who invited you to re-invite you at the address your provider uses.

  3. Your identity provider setup is missing something. Ask your IT team to confirm that you're assigned to the Noibu app and that your profile returns the email address on your Noibu account.

"Something went wrong" page after signing in

  • This most often means you used the wrong login method. If your company requires SSO, signing in with email and password lands you on this page even when your password is correct. Go back to Identify your login method and use Sign in with SSO.

  • Resetting your password won't fix this if your company requires SSO.

Sign-in page keeps loading or freezes

Work through these in order and stop as soon as you're in:

  1. Open Noibu in a new browser tab.

  2. Hard refresh the page with Ctrl+Shift+R (Windows) or Cmd+Shift+R (Mac).

  3. Clear cache and cookies for noibu.com, then sign in again.

  4. Try an incognito or private window.

  5. Try Chrome. Sign-in hangs have been reported in Safari and Edge.

  6. Turn off ad blockers, VPNs and strict privacy or security filters. These can block parts of the sign-in page.

Signed in but the screen is blank

Sign-in worked, but the page content didn't load. This usually happens when your browser is holding on to old data from an earlier session.

  1. Open Noibu in a new tab and hard refresh.

  2. If the screen is still blank in a new tab, an incognito window and a second browser, contact support.

Invitation or password reset email never arrives

  1. Check spam, junk and any corporate quarantine.

  2. Confirm the address with the teammate who invited you. Make sure the email went to the correct address.

  3. Ask the teammate who invited you to remove you and add you again. This sends a fresh invitation. If you already set a password before, use Forgot your password? on the sign-in page instead.

  4. Contact support if nothing arrives. If email to your address bounced in the past, our system may have stopped sending to it. Support can clear the block.

Password rejected or Accept invitation stays greyed out

  • Passwords need at least 12 characters, at least one number and at least one special character.

  • If Accept invitation is greyed out, make sure every field is filled in, both password fields match, the password meets the rules above and the terms and conditions box is ticked.

  • If everything is filled in correctly and the button is still greyed out, ask the teammate who invited you for a new invitation.

If you've been locked out after several attempts, see Why am I locked out of Noibu?

This is an access issue, not a login issue. Noibu has two access levels, Full Access and Sessions Only. Your account may be set to Sessions Only, or may not include the area you were linked to.

A Sessions Only user can't upgrade their own access. Ask a teammate with Full Access to update it. See Adding and Removing Teammates.

When to contact support

If none of the fixes above work, submit a ticket to support@noibu.com. Include these in your first message so we can help without going back and forth:

  • The email address you're signing in with, and your company name

  • Which method you used: Sign in with SSO, Sign in with Google, or email and password

  • Your browser and version, and whether Chrome behaves differently

  • Whether an incognito window works, and whether you're on a VPN or corporate network

  • A screenshot of the exact error. If the failure happens on your identity provider's screen rather than Noibu's, send that screenshot.

  • A short Loom or screen recording of the sign-in attempt, with your browser's Console and Network tabs open and Preserve log ticked, so the redirect doesn't clear the errors