Separate sign-in failure from feature permission
| Symptom | Check first | Next step |
|---|---|---|
| The Google Account sign-in page will not open | Browser, cookies, network, and Google sign-in service | Compare a private window and one other network |
| Google Account sign-in works but Gemini will not open | Gemini page message, browser session, and account environment | Keep the exact text and failed step |
| A personal account works; a work or school account does not | Workspace administrator policy, licensing, or feature rollout | Ask the organization administrator to check |
| The same account works in one browser only | Site data, extensions, cookies, and redirect settings | Compare a clean profile |
| Only the current network fails | DNS, proxy, IPv4/IPv6, and managed-network policy | Record the network environment before troubleshooting |
Restore one comparable Google sign-in session
Confirm the active account
A multi-account browser can use different Google Accounts in different tabs. Confirm the intended account and Gemini entry point, then record the page message.
Use a private window or clean profile
Reproduce with the same account to isolate old cookies, cache, extensions, or redirect blocking. Do not start by clearing every browser setting.
Review extensions and cookie settings
Test privacy settings and extensions that can block Google sign-in, cookies, scripts, or redirects one at a time, then restore necessary protection after diagnosis.
Separate personal and managed accounts
Work and school accounts can be administrator-controlled. When the page loads but a feature is missing, ask the administrator about organization Gemini settings, licensing, and availability.
Compare the network last
Only when the same account in a clean browser fails on one network should you record IPv4, IPv6, DNS, and network policy; this avoids attributing an account issue to an exit.
Why Workspace cases need an administrator
Managed-account feature availability can depend on organization settings, licensing, data-protection policy, or staged rollout. A personal account working on the same network does not establish that a work or school account should have the same Gemini feature; a managed-account restriction does not prove the network exit is wrong.
Give the administrator the account type, full message, time, browser comparison, and whether another network reproduces it. Do not share passwords, verification codes, or sensitive organization data.
Use the fewest variables to find a browser or network issue
- The same Google Account, Gemini entry point, and browser version
- Original browser versus a private window or clean profile
- Current network versus one known-stable network
- Whether the failure happens at Google sign-in, redirect, or after Gemini loads
- When only the network differs, IPv4, IPv6, region, ASN, DNS, and proxy state
When to use Google or organization support
When the same account shows the same message in a clean browser, another device, and stable networks, follow the page guidance through Google Help or the appropriate support channel. For a managed account, contact the Workspace administrator first because they can review organization-wide settings.
Sources and evidence limits
Sources below support the stated technical or policy boundary. Diagnostic comparisons in this guide remain observations, not account verdicts.
- Gemini Apps HelpGoogle · Official guidance
- Google Account HelpGoogle · Official guidance
- Google Workspace Admin HelpGoogle · Official guidance