Signing in
Pick the right account, recover from a sign-in that fails, and get into the right organization.
Signing in is routine until someone keeps two Google accounts, or belongs to several organizations, and lands somewhere unexpected. This page covers how BadgeOut helps people pick the right identity, and how to read the screens that appear when they don't. It's also the page to send a member who says they "can't get in".
Choose the right Google account
Selecting Sign in with Google always shows Google's account picker, even when the browser is already signed in to one account. That's deliberate: a work identity is often not the browser's default, and silently reusing the wrong account is how people end up locked out of an organization they belong to. Choose the account your BadgeOut membership lives on; for a member joining by invitation, that's the address the invitation was emailed to.
Signing in from an invitation email preselects the invited address in the picker, so accepting with the wrong account takes deliberate effort.
"You don't have access to this organization"
Opening an organization your signed-in account doesn't belong to shows the no-access screen. It isn't a dead end, and it won't navigate away on its own:
- It names the account you're signed in as, which is usually the whole explanation: right person, wrong identity.
- It lists every organization that account can reach, as a dropdown with a Continue button. Nothing is preselected; continuing is a deliberate choice.
- Sign in with a different account starts over with the account picker, for when the membership lives on your other identity.
A visit that ends here isn't remembered as your last-active organization, so going back to the homepage won't bounce you straight back to the denied screen.
When sign-in fails
Backing out of Google's consent screen, or a genuine sign-in failure, lands on a BadgeOut page that says what happened in plain language and offers Back to sign in. A cancelled sign-in is described as exactly that, not an error. When something really failed, the page keeps a short Error code at the bottom; include it if you contact support.