The Google account switcher: why it sends you to the wrong account

A shared document opens as the personal account. A calendar invite lands in the wrong inbox. A form gets submitted from the account that has no access to the sheet it writes to. Each time, the fix is the same nine clicks: profile picture, pick the other account, wait for the page to reload, find the link again. The Google account switcher works exactly as designed, and it is still the wrong tool for anyone who lives in two accounts all day.

The reason is worth understanding before changing anything, because the switcher is not misbehaving. It is doing something narrower than most people assume it does, and Google documents the limits plainly. Once the shape of the limitation is clear, the choice between three or four possible fixes gets much easier.

What the switcher is designed to do

Google's own description of the feature is short. Signing in to more than one account at once means, in Google's words, that "you can switch between accounts without signing out and back in again." That is the whole promise. It is about avoiding a second sign-in, not about keeping two accounts genuinely apart.

The mechanics are unchanged for years. On a computer, select the profile image at the top right, choose Add account, and sign in. To move between them, select the profile image again and pick the account. Both accounts stay signed in inside the same browser at the same time.

The part that matters is the sentence Google attaches to the promise:

Your accounts have separate settings, but in some cases, settings from your default account might apply. Source: support.google.com

Separate settings, one shared browser session. That is the boundary. The accounts do not share a language preference or a set of sign-in steps, and Google is explicit that "account settings usually aren't shared between accounts." What they do share is the browser they live in, and that is where the wrong-account problems come from.

Signing out shows the same shared boundary from the other side. The menu offers Sign out or Sign out of all accounts, and removing an account from the sign-in page has to be repeated per browser: Google's instructions say to repeat the steps in every browser where a sign-in happened, naming Firefox and Safari as examples. Nothing about the arrangement is per-account. It is per-browser.

The default account decides more than it looks like it does

The default account is not a setting most people choose deliberately. Google states that "in many cases, your default account is the one you signed in with first," and on mobile it varies by operating system and by app.

That accidental designation then gets used as a tiebreaker. Google's help page explains that when several accounts are signed in at the same time, the service sometimes cannot determine which account is in use, and gives opening a new browser window as the example. In that situation Google may apply settings from the default account, naming Web and App Activity and Ads Personalization specifically.

The consequences reach past privacy settings. The same page points at the Play store:

Your account's payment info sets your Google Play country. If you are signed in to multiple accounts from different countries, Google Play might show content from your default account's country. Source: support.google.com

For anyone holding a work account in one country and a personal account in another, that is a real, documented mismatch rather than a bug to report. The advice Google gives is to switch to the correct account before browsing, which is another way of saying the switcher puts the burden of remembering on the person, every time.

This is the root of the frustration behind the search. The switcher is a convenience layer over a single browser session, and a single browser session has to guess. Guessing correctly most of the time is not the same as being predictable, and predictability is what someone running two accounts side by side actually needs.

Where the switcher breaks on a Mac

Three failure patterns show up repeatedly, and none of them is fixed by clicking more carefully.

Links opened from outside the browser

A link in a mail client, a chat app or a calendar notification has no idea which Google account should open it. It hands the URL to the default browser, the browser resolves it against whichever session it has, and the page loads as whoever that turns out to be. The request to switch accounts arrives after the page has already loaded, which means the work of finding the link again starts over.

Two accounts needed at the same time

Copying a range from one account's spreadsheet into another account's document is not a switching problem at all. It needs both accounts open simultaneously. The switcher cannot do this, because it is one session with several identities attached, not several sessions.

Extensions, notifications and sign-in prompts

Notifications belong to the browser, not to the account, so a notification arriving while the other account is in front is ambiguous. Password managers and extensions see one browsing context and offer credentials from all of it. Every sign-in prompt becomes a small decision.

None of these are solved by the switcher because none of them are what it was built for. The fix has to change the container, not the menu inside it.

Three ways to stop switching, compared

Three mechanisms are available on a current Mac, and they separate different things at different costs.

Approach	What is actually separated	Cost	Where it breaks
Account switcher	Account settings only. One browser session, one default account	None. Built in	Both accounts cannot be used at once. Links resolve to the wrong account
Chrome profiles	Bookmarks, history, passwords and other settings per profile	One window per profile to keep track of	Profile windows look alike. Anyone with the Mac can switch profiles
Gmail delegation	Nothing is separated. One mailbox is read from another account	Setup by the mailbox owner, plus admin settings at work	Gmail mail only. Not Drive, not Calendar

Chrome profiles are the closest thing to real separation without extra software. Google describes the result directly: "With profiles, you can keep all your Chrome info separate, like bookmarks, history, passwords, and other settings." Each profile gets its own window, and a link opened while a profile window is in front usually stays in that profile.

Two documented caveats deserve attention before committing to profiles. The first is that profiles are a convenience, not a security boundary:

If someone has your device, they can switch to any other Chrome profile on it. If they open your Chrome profile, they can see info like what websites you visited. Source: support.google.com

The second is what removal does. Google warns that "after you remove a profile from Chrome, the profile's bookmarks, history, passwords, and other settings are erased from the computer." Profile cleanup is not reversible, so a profile per account works better than a profile per project.

What does not get separated

Chrome profiles separate what Chrome stores. They do not separate what macOS stores, so a downloaded file lands in the same Downloads folder regardless of which profile fetched it, and a file picker opened from either profile sees the same disk. Anything that leaves the browser leaves the separation behind, which is worth knowing before assuming a profile boundary covers a compliance requirement.

Delegation instead of switching, for mail only

For a mailbox that has to be watched rather than owned, Gmail delegation removes the switching entirely. The other account's mail appears inside the account already signed in.

The documented terms are specific. A personal Gmail account can add up to 10 delegates, and a work or school account up to 1,000. Google describes the role as someone "who can read, send, and delete emails in your account for you," and draws the line clearly: "A delegate can't chat with anyone or change your password." The list of what delegates do not get is longer than most people expect, covering Drive attachments, Tasks, autocomplete, Smart Compose and Gemini features.

Two details change how delegation feels in practice. Setup is not instant, since Google states that "it can take up to 24 hours before a delegate can use your account." And attribution is visible: "When a delegate sends a message from your account, their email address appears." Delegation is therefore honest by design, which is usually the point when an assistant or a colleague covers a mailbox.

Inside an organisation, the limits are set by an administrator. Google Workspace documentation states that "a single Gmail account supports up to 1,000 unique delegates," that "with typical use, 40 delegated users can access a Gmail account at the same time," and, importantly for anyone trying to delegate across company boundaries, that "users can only delegate access to another user in the same organization, regardless of their domain or their organizational unit." Delegating a client's mailbox to a contractor outside the organisation is not available.

Delegation is the right answer for mail and only for mail. Drive, Calendar, Analytics and Search Console all have their own sharing models, and none of them removes the need to be signed in as the right account.

When one window per account is the cheaper answer

At two accounts, profiles and the switcher are both tolerable. At four or five, with two mail accounts, two calendars, a chat tool and an admin console, the arithmetic changes. Every new account multiplies the number of windows that look identical, and the cost stops being clicks and becomes attention.

The alternative is to stop treating accounts as states of one browser and treat each service as its own window. A browser that keeps each web app in its own window gives every app its own cookie store, which means the work Gmail and the personal Gmail sit open at the same time, each in a window with its own name and icon, each reachable through Command-Tab like any other application. There is no default account to guess at, because there is no shared session to guess from.

The practical difference is that the wrong-account failure mode disappears rather than becoming less frequent. A link opened inside a window belongs to that window's session. Notifications arrive attached to a named window. Nothing carries settings over from an account that happened to sign in first. Organising this by job rather than by account is what workspaces are for, and the list of services that behave well in a dedicated window is worth checking against the supported apps before moving anything.

The trade-off is honest: this is another application to install and set up, where the switcher and Chrome profiles are already present. It earns that cost only when the switching is constant.

What to change first

Count the switches in a normal working day. Under five, add a second Chrome profile and keep the switcher for the rest. Above that, and especially when two accounts need to be visible at the same time, move the heaviest three services into their own windows and see what happens to the count, which is the shape SpaceDeck is built around.