Run through these checks in order before raising a ticket. Most sign-in problems fall into one of the categories below.
Quick checks
-
Are you using the right URL?
BNDRY is at the URL your administrator gave you. It will end withbndry.app, and if your company uses single sign-on it will start with your company's name (for example,company.bndry.app). Bookmark the exact URL — typing a guess won't work. -
Are you using your work email?
Use the email address you sign in to your work email and apps with. Don't use a personal email. -
Have you been redirected to your company's login page?
If yes, that's expected. See Why am I being redirected to my company's login page? — your work password is the one you need. -
Are you clicking "Sign in with Google" when your account uses a username, password, and MFA?
"Sign in with Google" only works if your administrator has configured Google as your sign-in method. If they haven't, the button will appear to do nothing, send you to an error page, or sign you in to the wrong account. Use the email and password fields on the BNDRY sign-in page instead, then enter your MFA code when prompted. If you're not sure which method your account uses, ask your administrator. -
Is your password right?
If you don't use single sign-on, try resetting your password. See Resetting your password. -
Is your MFA code being rejected?
Check that your phone's clock is set to update automatically. TOTP codes are time-sensitive. If your clock is more than 30 seconds off, codes will fail. -
Have you been deactivated?
If you've changed roles or recently left an organisation, your administrator may have removed your access. Confirm with them. -
Is BNDRY itself up?
Check the BNDRY status page at status.bndry.net. If there's a known issue, you'll see it there.
Still stuck
If you've worked through everything above and still can't sign in, contact your BNDRY administrator. Include:
- The exact error message you saw (a screenshot helps)
- The time the error occurred, in your local time zone
- The browser and device you were using
Comments
0 comments
Article is closed for comments.