Troubleshoot sign-in and verification
Use the correct account, browser and enrolled security method.
Last reviewed
- Who can use this
- Owner, Admin, Finance, Viewer within their assigned sites
On this page
Use the sign-in page for your own Brightstone account. An account's Google sign-in and its advertising/GA4 reporting authorizations are separate.
Password or Google sign-in
Check the email address and intended Google profile. Use the password reset option if needed; creating another workspace does not restore access to an existing one. Complete redirects and return to the intended dashboard rather than repeatedly starting new sign-ins.
Security prompts
Choose an enrolled method offered by the account and finish its authenticator/passkey prompt. A timed-out or canceled native prompt is not a successful verification. If you use a recovery code, keep it private.
Recognized-device trust can expire or be revoked. Another browser profile, private browsing, cleared cookies, an email/password change or an unusual sign-in context can require fresh verification. An installed PWA and a normal browser can have separate storage.
If access is still blocked
Try the same account in a supported normal browser and check that required cookies/redirects are allowed. Avoid clearing all storage until you understand that this can remove trusted-device state. Use the verified support route if no enrolled or recovery method works. Support cannot safely bypass security based on a public message, and you should never send passwords, verification codes, session cookies or recovery codes.
If these steps do not resolve your question, contact Brightstone support. Never include passwords, tokens or recovery codes.
Contact support →