Two Google accounts on one computer, without the mix-ups

Two Google accounts and one machine is now the ordinary case, not the exception. The reason it still generates so much searching is that the phrase hides a choice nobody makes deliberately: the separation between the accounts can be drawn in four different places, and each one produces a different set of daily annoyances. Picking the boundary on purpose, rather than inheriting whichever one happened first, is most of the work.

Where the boundary can sit

Google itself allows more than one account to be signed in at once, and the account switcher exists for exactly that. But signing in twice is only the first of four arrangements, and it is the weakest one for anything that runs outside a web page.

The four are worth naming plainly. The accounts can be layered inside a single browser session, which is Google's own multi login. They can be split into separate browser profiles, each with its own cookies and extensions. They can be split at the level of the operating system, with two macOS user accounts on the same Mac. Or the split can be drawn per application, so that each web app has its own window and its own session, regardless of which browser profile is behind it.

Boundary	Separates	Cost
Google multi login	Sessions inside one browser	Nothing separates outside the browser
Browser profiles	Cookies, extensions, history	Switching means changing windows
macOS user accounts	Everything on the machine	Only one is usable at a time
Per app windows	Each web app, individually	Needs a browser built for it

Reading down that table, the pattern is that stronger separation costs more to cross. Multi login is free to cross and separates almost nothing on the desktop. A second macOS user account separates everything, including the files, and cannot be crossed at all without logging out or switching users. Most people need something between the two, which is why the middle rows are where the real decision lives.

What sits outside the browser

The part that surprises people is how much of Google is no longer in the browser at all, and therefore is not covered by any browser side arrangement.

Drive for desktop is the clearest case. It runs as a background application, puts a single icon in the macOS menu bar, and syncs files into Finder. Its documentation states that up to four accounts can be connected at once, each appearing inside that one menu bar item. That is generous, but note what it means: the account boundary here belongs to the sync client, not to the browser, and it has to be configured separately.

The same applies to anything else with a desktop presence. Notifications from a calendar, a mail client set up with both addresses, a password manager filling credentials, a meeting application launching from a link. None of them consult which browser profile is in front. They have their own idea of which account is current, and that idea is usually the one that was set up first.

This is the practical reason that a carefully separated browser still produces cross contamination. A file saved to the wrong Drive, a reminder for a client meeting appearing during personal time, a login form filled with the work address. The browser was doing its job. The boundary simply did not extend as far as the desktop.

The way through is to audit the desktop side once, listing every background application that holds a Google login, and decide for each one whether it should hold one account or both. It is a short list for most people, and it stays fixed for months.

One detail is worth writing down during that audit: which account each application will use when it has no reason to ask. Sync clients pick the first one connected. Mail clients send from whichever address is marked as the default. Calendar alerts fire for every connected account at once unless one is muted. These defaults are set silently at installation time and almost never revisited, which is why an arrangement that felt correct in January produces odd behaviour by June.

The parts that follow the machine, not the account

Some things on a computer are owned by the machine or by the operating system user, and no account arrangement inside a browser touches them. Knowing which ones they are prevents a lot of wasted configuration.

Downloads are the standard example. Two browser profiles can be perfectly separated in every other respect and still write into the same Downloads folder, side by side and in the order they arrived. A client contract and a personal receipt end up as neighbours, and the file names are the only clue as to which account produced which. Setting a different download location per profile, or at least being prompted for the location each time, is a two minute change that stops this at the source.

The default browser is another. macOS holds one default for the whole user account, so every link clicked in a mail client, a chat application, or a document goes to that one browser first. Which profile inside it receives the link is then decided by the browser, and typically that is the profile whose window was used most recently. This is the mechanism behind the most common complaint in this whole area: a shared document link opening under the wrong identity, with an access request page as the result.

Credentials sit in a third position. Passwords saved into a Google account travel with that account, so they follow it to any signed in browser. Passwords saved into the macOS keychain belong to the operating system user instead, which means both browser profiles can reach them and a second person using the same macOS account can reach them too. Keeping work credentials in one store and personal credentials in another is a decision worth making explicitly, because the defaults will mix them.

A shared machine is a different problem

There are two very different readers behind this search, and the advice diverges sharply.

The first has two of their own accounts, work and personal, on a machine only they use. For this person, the risk is confusion, not exposure. Sending from the wrong address is embarrassing and recoverable. The correct answer is the lightest boundary that makes the current identity visible at a glance.

The second shares the computer with a partner, a housemate, or a family member. Here the risk is genuine exposure: browsing history, autofilled addresses, saved payment details, and a signed in mail client that anyone who walks past can read. No browser profile solves this, because profiles are a filing arrangement rather than a lock. Anyone can open the profile menu and select the other one.

For that case the operating system already has the right tool. macOS supports multiple user accounts, and an administrator can turn on fast user switching so that more than one person can be logged in at the same time and swap between sessions from the menu bar or Control Center. Each user gets separate files, separate keychains, and separate application state. The cost is that only one session is in the foreground at a time, so this is a boundary between people, not a boundary between two roles of the same person.

Mixing the two up produces the common bad outcome: a household sharing one macOS user account and trying to keep things apart with browser profiles, which achieves privacy from nobody.

When one of the two is a work account

If either account comes from an employer or a client, a third layer appears that has nothing to do with convenience.

Anything created in that account belongs to the organisation. Documents, calendar entries, and the third party connections approved during those sessions all sit inside a domain an administrator controls, and they leave when the engagement does. A personal note written while signed in to the work account is not a misplaced file. It is a file inside somebody else's account.

Administrators can also shape what the browser is allowed to do. Whether another account may be added alongside the managed one, whether a dedicated profile is enforced, which extensions are permitted, whether sync is available: all of these can be pushed as policy. When a setting shows a note about being managed by an organisation, it is not changeable locally, and finding that out before building an arrangement on top of it saves an afternoon.

There is also a quieter point about personal machines. Connecting a work account to a personal computer can bring device level management with it, depending on how the organisation is configured. It is worth asking what is enrolled before signing in, rather than after. The answer decides whether the work account belongs in a browser profile on the everyday machine or in a separate macOS user account that can be handed back cleanly.

The failure that keeps happening

Even with a sensible boundary, one class of mistake survives: acting under the wrong identity because nothing on screen said which one was active.

The signals are small by design. An avatar in a corner, a colour theme if one was set, an address in the corner of a compose window. None of them are in the path of attention when moving quickly, and none of them appear in the macOS application switcher, which sees one browser regardless of how many accounts are inside it.

Two habits reduce this more than any setting. The first is to give each profile a genuinely different look, not a subtle one: a distinct theme colour and a different avatar, chosen so the difference is visible at the edge of vision. The second is to check the identity before the action rather than after, specifically at three moments: before sending a message, before uploading a file, and before approving an access request.

Beyond habits, the structural fix is to stop asking one application to hold both identities. Some people run two different browsers. Others move to a browser designed around several accounts at once, where the separation is a first class feature rather than a setting. The common thread is that the identity becomes visible at the window level, where attention already is.

What to change first

Draw the boundary once, on purpose. If the machine is shared with another person, use a second macOS user account and stop there. If it is one person with two roles, put the split at the window level so the active identity is visible without clicking, and make the two look obviously different. Then spend ten minutes on the desktop applications that hold a Google login, because that is where the leaks actually happen. For the window level arrangement, SpaceDeck is built around keeping each app and account in its own space.