More than one Google account on a Mac, without the mix-ups

Holding more than one Google account is normal now. A personal address, a work address on Google Workspace, an address for a side project, sometimes a client's domain on top of that. Google supports being signed into all of them at once, and for the first week that feels like the problem is solved. The trouble arrives later, in small doses: a calendar invitation that opens as the wrong person, a shared document that says access is required even though access exists, a link from a chat message that lands in an account with no permission to see it.

None of that is a bug. It is the predictable result of how multiple sign-in is built, and once the mechanism is clear the fix stops being a matter of being more careful. Being careful is not a strategy that survives a busy Tuesday.

What multiple sign-in actually does

Google's account help states the capability plainly: with more than one Google account, it is possible to sign in to multiple accounts at once. Switching between them happens through the profile image in the top right. What is easy to miss is the sentence about which account is in charge.

In many cases, your default account is the one you signed in with first. Source: support.google.com

The default account is not a preference set once in a settings screen. It is a property of the browser session, decided by sign-in order, and it persists until the session is cleared. Every time a link is opened without an account already attached to it, the default is where it goes. That single fact explains most wrong-account incidents on a Mac.

The second fact worth knowing is visible in the address bar. Google web apps carry an account index in the URL, written as /u/0, /u/1 and so on. The number is a position in the signed-in list, not a permanent identifier for an account. Bookmarking a Gmail URL containing /u/1 works until the sign-in order changes, at which point the same bookmark opens a different mailbox. This is why bookmarks are an unreliable way to pin a second account.

The help page also notes that settings do not travel between accounts, which surprises people who expect a single consistent experience across all of them.

When you sign in to multiple accounts, account settings usually aren't shared between accounts. Source: support.google.com

Where multiple sign-in stops being enough

The mechanism has three failure modes, and they turn up in a predictable order.

The first is inbound links. A link arriving from a chat client, a desktop mail app, or a calendar notification has no account context. It opens in the default. If the resource belongs to another account, the result is an access request screen, and clicking through the account switcher reloads the page. It takes ten seconds and happens dozens of times a day, which is the shape of a cost that never announces itself.

The second is products that behave differently under multiple sign-in. Google's own documentation gives an example of settings from the default account being applied in ambiguous situations, and notes that content in Google Play can follow the default account's country when the signed-in accounts belong to different countries. The general rule is that anything ambiguous resolves toward the default rather than toward the account being looked at.

The third is administrative. A Google Workspace account is governed by its organisation, and an administrator can restrict what happens when it sits alongside personal accounts in the same browser session. Anyone whose employer manages the account should expect the browser session to be part of what is managed.

None of these are solved by remembering which account is which. They are solved by making sure the wrong account is not in the session at all.

Chrome profiles, and their honest limit

The real boundary in Chrome is the profile. A profile has its own cookie store, so each one can hold a different Google account as its only signed-in account. Links opened from within a profile stay inside it. Extensions, history, and saved passwords are separate. Each profile opens in a separate window with its own icon, which makes the correct window identifiable at a glance.

This is a genuine separation, and Google's documentation is careful not to oversell it.

Only share your device with people you trust. If someone has your device, they can switch to any other Chrome profile on it. Source: support.google.com

Profiles keep information apart. They do not lock it. That distinction matters for anyone handling client data on a shared or portable machine, because a profile is not a substitute for a login on the Mac itself.

The practical weakness of profiles is different: switching costs a window change, and every profile window carries a full browser interface, complete with its own tab strip that fills up on its own. Two profiles are comfortable. Four profiles means four browser windows, each with its own accumulation of tabs, and the tidiness that motivated the setup starts to erode.

Safari profiles as the lighter version

Safari has the same idea with less ceremony. Apple describes the purpose as keeping personal browsing separate from work, school, and other browsing by creating a profile for each part of life, and each profile carries its own tab groups, history, and extensions.

One documented exception is worth planning around. If passwords are stored with iCloud Keychain, they are available in any profile created, so the credential list does not narrow when the profile changes. That is convenient for filling in a login and unhelpful for preventing the wrong one from being filled in.

The desktop applications make it worse

Most wrong-account incidents do not start in the browser. They start in a chat client, a native mail application, or a calendar reminder, and the link travels through macOS to whichever browser is set as the default. The application sending the link has no way to say which account it belongs to, and the browser receiving it has no way to ask. Whatever window is nearest gets the page.

This is why a profile setup that works perfectly while browsing falls apart the moment work arrives through notifications. The separation is real inside the browser and completely absent at the boundary. Anyone who spends the day being interrupted by links rather than typing addresses is living at that boundary, which explains why the same setup can be praised by one person and dismissed as useless by another doing similar work.

There are partial answers. Some link-routing utilities on macOS can send a URL to a chosen profile based on the domain, which works well for domains that map cleanly to one account and poorly for shared services like a document store used by every client. Keeping the profile that receives the most inbound links as the frontmost window during the working day is cruder but costs nothing. Neither is a real fix, because both are attempts to route around a piece of missing information rather than to supply it.

Reducing the number of accounts instead of managing them

Before building any separation, it is worth checking whether every account needs to exist as an account.

Gmail can send from an additional address, so an alias or a small side project often does not need a second sign-in at all. Mail from a second address can be routed into a main mailbox and replies sent under the original address, which collapses two accounts into one without losing the identity.

Google Workspace supports delegation, which lets one person read and reply in another mailbox from within their own. For anyone monitoring a shared address such as an enquiries inbox, delegation removes a sign-in entirely.

Shared drives change the same calculation for files. A document stored in a shared drive belongs to the organisation rather than to an individual account, so access no longer depends on which account happens to be signed in.

None of this helps when two accounts genuinely belong to different organisations with different permissions, which is the case that produces the hardest version of the problem. But it commonly removes one or two accounts from the list, and the difficulty of the whole situation scales with that number. Going from four accounts to two changes the setup that is needed, not just the effort of running it.

Four setups compared

Setup	Boundary	Wrong-account risk	Switching cost	Suits
Multiple sign-in in one browser	None, one shared session	High, everything follows the default	One menu, plus a reload	Two accounts, light use
Chrome profiles	A separate session per profile	Low within a profile	Changing window	Clear work and personal split
Safari profiles	A separate session per profile	Low within a profile	Changing window	Mac-only workflows
A window per application and account	An application, permanently	Low, each window is one identity	One keystroke	Several accounts used all day

The pattern in the table is that risk falls as the boundary hardens, while the cost moves from cognitive effort to setup effort. Multiple sign-in demands vigilance every day and no setup at all. The other rows demand a decision once and very little afterwards.

The setup that removes the decision

Three habits do most of the work regardless of which row is chosen.

Sign in to the account that receives the most inbound links first, so it becomes the default. If most links arrive from work chat, the work account should be the default, and the personal account should be the one requiring a deliberate switch.

Stop bookmarking URLs that contain an account index. Either bookmark from within the correct profile, where the plain address resolves correctly, or use a setup where the application itself belongs to an account.

Make identity visible before clicking. A profile icon, a window colour, a named workspace: anything that answers the question of which account this window is without needing to check the avatar in the corner.

The last habit is the one a browser built around one window per web application handles by default. Each service, and each account on that service, gets a persistent space with its own session, so the same mail service can hold three accounts side by side without any of them displacing another. Links opened inside a space stay in that space, which removes the default-account problem entirely rather than managing it. The Workspaces page describes how those spaces are arranged, the comparison with Rambox covers what differs between tools in this category, and pricing is worth checking before committing to any of them.

What to change first

Count how many times in one day a link opens as the wrong Google account. Under three, multiple sign-in with the right default is fine and nothing needs building. Above that, the session is doing too many jobs, and each account needs somewhere of its own to live, which is what SpaceDeck is for.