Skip to main content

1. “We’re Having Trouble Logging You In”

This is the most common generic login error. Try these fixes in order:
1

Clear browser cache and cookies

Clear cache and cookies for your Unbound domain (either gateway.getunbound.ai or your organization’s custom domain), then try again.
2

Try incognito / private browsing

Open an incognito or private browser window and attempt to log in. This rules out extension or cache conflicts.
3

Verify the correct URL

Make sure you’re using the right portal URL:
  • Direct customers: https://gateway.getunbound.ai/
  • Enterprise customers: Your organization’s custom domain (ask your admin if you’re not sure)
4

Try a different browser

If the above doesn’t work, try Chrome, Firefox, or Edge to rule out browser-specific issues.

2. Login Error After Email Domain Change

Scenario: Your company changed email domains and you can’t log in. Why this happens: Your Unbound account is linked to your old email address, so your new one isn’t recognized. How to fix: An email address can’t be edited in place. Contact your organization administrator and ask them to:
  • Invite you on the new email domain from Settings → Console Access → Add Users, then suspend the old account from Policies → Users → Individuals → Change Status — that suspends rather than deletes, and suspending disables that account’s sign-in
If your organization syncs users from Okta, that sync brings over name, manager, department, title, suspension and Okta group membership (as Okta-owned user groups), but it does not create accounts on a new domain. Your admin invites you directly in Unbound.

3. “Organization Doesn’t Exist” Error

Why this happens: Your account hasn’t been provisioned in Unbound yet. How to fix: Ask your organization administrator to:
  1. Go to Settings → Console Access in the Unbound dashboard
  2. Click Add Users
  3. Enter your email address and assign appropriate permissions
  4. Or, if your organization syncs from Okta, confirm your Okta account is active — a suspended Okta user is deactivated in Unbound

4. “The Email or Password Provided Is Incorrect” (Okta SSO)

Why this happens: The Okta integration hasn’t fully provisioned your account. How to fix:
  • Ensure the Unbound application is assigned to you in your Okta admin console
  • Ask your IT admin to confirm your Okta account is active — an Okta account marked SUSPENDED deactivates the matching Unbound user, and reactivating in Okta does not automatically reactivate in Unbound
  • Try logging out of Okta completely (all sessions) and logging back in
  • Clear your browser’s Okta cookies and re-authenticate

5. OAuth/SSO “invalid_grant” or “invalid_rapt” Error

Why this happens: Your OAuth authentication session has expired, been revoked, or requires re-authentication. How to fix:
1

Log out completely

Sign out from all Unbound sessions.
2

Clear browser cookies

Clear cookies specifically for the Unbound domain.
3

Re-authenticate from scratch

Don’t use any saved or cached sessions.
4

Check your identity provider

If using Google SSO, verify your Google account session is still valid and hasn’t been revoked by your admin. If your org recently changed SSO settings, you may need to re-authorize the Unbound application.

6. “Unable to Login” With No Specific Error

Work through this checklist:
  • Clear browser cache and cookies for the Unbound domain
  • Try a different browser (Chrome, Firefox, Edge)
  • Verify you’re using the correct email address
  • Check with your admin — has your account been created/provisioned?
  • Check your network — are you behind a VPN or firewall that might block the login?
  • Disable browser extensions — ad blockers or privacy extensions can interfere with SSO flows

7. “You Don’t Have Access” After Signing In

Scenario: You sign in, but instead of the dashboard you see a full-page You Don’t Have Access card — Need access? Contact your organization admin — with your email beneath it. Why this happens: Only a role with at least one area at View can use the console. A Member, whose role has none, is monitored and governed by your policies, but has no console access. How to fix:
  • Ask your admin to give you a role under Settings → Console Access → Add Users
  • Once they have, choose Access just granted? Refresh this page on the card
  • Or Sign out and sign in with a different account
Your AI coding tools keep working meanwhile; this only affects the dashboard. See Access Restricted.

When to Escalate to Support

Contact support if:
  • You’ve tried all steps above and still can’t log in
  • You see a server error (500) or the page won’t load at all
  • Your admin has verified your account exists but you still can’t access it
Please include in your support message:
  • Your email address
  • A screenshot of the error message
  • Which login method you’re using (email/password, Okta SSO, Google SSO)
  • Your organization name

CLI Authentication

Browser login, scoped tokens, and --api-key with a token from Settings → API Tokens

Find Your API Key

Locate your API key to use with tools and the CLI