Sign in & first access
Google or email sign-in for @aquasani.net staff. Covers first login, the welcome tour, and common sign-in errors.
These documents are available before and after sign-in. Sign in for full app access — in-app links open after you sign in.
Happy path
- Open the login page and choose Google or email.
- Use your @aquasani.net account — personal Gmail addresses are not accepted.
- Land on the dashboard; complete or skip the first-time tour.
- If you see an error, note the exact message before trying again.
T1 — Quick fixes T1 · Self-serve
“Use your @aquasani.net account” after Google sign-in
Why: Signed in with a personal Gmail or an email not on the staff allowlist.
Try: Sign out of Google in the browser (or use a private window), then sign in again with your work @aquasani.net account.
Success: You reach the dashboard without the not_authorized message.
Redirect loop or blank page after sign-in
Why: Stale cookies or an interrupted OAuth callback.
Try: Clear site cookies for this app, close the tab, open /login in a fresh tab, and try again.
Success: Dashboard loads and the URL stays on aquasani.net (not stuck on /login).
First-time tour keeps appearing
Why: Tour completion did not save (rare — usually offline at finish).
Try: Finish the tour while online, or tap Skip — it should not replay on next login.
Success: After logout and login, no tour overlay.
“Account not found” with email sign-in
Why: Email not provisioned yet or typo in address.
Try: Double-check spelling. Try Google sign-in if your account uses SSO. Contact an admin to confirm you are on the team list.
Success: Login succeeds or admin confirms account is active.
T2 — Guided steps T2 · Guided
- Confirm the email on their Google account matches @aquasani.net.
- In Settings (after sign-in) → Team, verify they are Active and role is assigned.
- Check staff allowlist if they were recently added.
- Have them try an incognito window to rule out extensions.
T3 — Escalate T3 · Escalate
Correct @aquasani.net account still blocked after admin confirms allowlist
May be auth callback or Supabase trigger misconfiguration.
Include: email used, timestamp, browser, screenshot of error
FAQs
Do I need a password if I use Google?
No — Google is the preferred method. Email/password is optional if your account has one set.
Will the welcome tour show every time?
No. It runs once on first login and is stored on your profile.
Can I use my phone to sign in?
Yes. Use the same @aquasani.net Google account. If OAuth fails on mobile, try email sign-in or a fresh browser tab.
Edge cases
- User opens Support from login before signing in (T1): Support documents work before sign-in; in-app links require authentication. Guide them through sign-in.
Was this article helpful?
Last updated July 10, 2026
Still stuck? Ask the Support AI on the main Support page.