Switch between multiple Google accounts without losing track

Two Google accounts is a normal working condition. A work address for mail, calendar and shared documents, and a personal one that owns the phone, the photos and a few subscriptions. Google supports being signed in to both at the same time, and the avatar menu in the top right corner moves between them in two clicks. The trouble starts once that becomes a dozen moves a day. A document opens under the wrong identity, a calendar invite lands in the account nobody watches, and an export arrives in a Drive that the rest of the team cannot reach. The switching mechanism is not broken. It is being asked to carry a decision that it was never designed to hold.

What switching actually changes

Signing in to a second account does not replace the first one. Both sessions stay live in the same browser, and the avatar menu chooses which one the next page loads under. Google describes the arrangement plainly.

If you have more than one Google Account, you can sign in to multiple accounts at once. That way, you can switch between accounts without signing out and back in again. Source: support.google.com

The important word is browser. The set of signed-in accounts belongs to one browser profile on one machine. Safari on the same Mac holds a different set. A second Chrome profile holds a different set again. That is why an account that is clearly signed in somewhere shows a login screen somewhere else, and why removing an account from the sign-in list has to be repeated in every browser where it was used.

What switching does not do is move the page in front of you. Choosing another account from the menu reloads the current product under that account, or opens a new tab for it. Anything unsaved in the old tab stays in the old tab, under the old account. Two tabs of the same product, opened under different accounts, will keep working independently for as long as both sessions remain valid.

Where the number in the URL comes from

Open Gmail with two accounts signed in and the address becomes something like mail.google.com/mail/u/0/ or /u/1/. Drive, Calendar and Groups use the same pattern.

That number is a position in the list of accounts signed in to this browser, not an identifier for the account itself. The account signed in first is u/0, the next is u/1, and so on in the order they were added.

The consequence is the single most common cause of a link opening under the wrong identity. A bookmark saved as /u/1/ points at whatever account currently sits second in the list. Sign out of everything and sign back in with the personal account first, and the bookmark that used to open the work inbox now opens the personal one, with no visible error at all. Nothing is wrong with the link. The list underneath it moved.

Two habits remove most of the pain. Bookmark the address that includes the account rather than the index, using the form mail.google.com/mail/u/[email protected]/, which resolves to the right session regardless of order. And when a shared link arrives from a colleague, check the account shown in the top right before assuming that an access error is a permissions problem. A page that says access is needed very often means the browser answered with the wrong session.

The default account decides more than it looks like

One of the signed-in accounts is the default, and it is usually invisible until it causes something strange.

In many cases, your default account is the one you signed in with first. On mobile devices, your default account can vary depending on your device's operating system and the apps you use. Source: support.google.com

The same help page states that when Google cannot tell which account a new window belongs to, settings from the default account may be applied, and that this reaches as far as country specific behaviour in the Play store. In day to day work it shows up as a new window opening under the wrong account, a search behaving as though it belongs to a different identity, and links clicked from outside the browser landing in the default session.

There is no setting that names a default directly. The order of sign-in is what sets it, so changing it means signing out of all accounts and signing back in with the intended one first. That is a five minute job, and it is worth doing once if the account used most often is not currently first. It is also worth doing after any full sign-out, because that is exactly when the order silently changes and every /u/N bookmark shifts with it.

Four ways to hold more than one account open

Multi sign-in is one option among several, and they differ in what they isolate.

Approach	Sessions isolated	Extensions and bookmarks	Cost of switching
Multi sign-in in one browser	No, shared cookie jar	Shared across accounts	Two clicks, one page reload
A second Chrome profile	Yes, separate data directory	Separate per profile	New window, then find it again
A different browser per account	Yes	Separate per browser	App switch, different interface
A window per app and account	Yes	Separate per window	Direct, no menu step

Multi sign-in is the cheapest to set up and the weakest boundary. Everything shares one cookie store, so a site that supports only one session at a time will still see one session. Separate Chrome profiles give a real boundary and cost a window each. A second browser works well for a hard split, such as a client account that must never touch anything else, and badly for anything switched often, because two different interfaces have to be learned.

The last row is the model used by a browser that keeps each web app in its own window. The unit stops being the account and becomes the application, which is the arrangement described under Workspaces and in the wider feature set.

A work account is not just another account

When one of the accounts belongs to an organisation, the switching question carries a second layer that a personal pair does not have.

Anything created while a Workspace account is loaded belongs to that organisation. Documents, calendar entries and the connections granted to third party tools sit inside a domain that an administrator controls, and they leave with the account when the contract or the job ends. A personal note written in the wrong session is not a private file that happens to be in the wrong place. It is a file in someone else's estate.

Administrators can also constrain the browser itself. Policy can restrict which accounts may be added alongside the managed one, require that the account runs in its own browser profile, control which extensions load, and turn synchronisation off. When a setting shows an organisation managed marker, the value is set upstream and cannot be changed locally, which is worth checking before spending time on a configuration that will be overwritten.

The practical rule that follows is about direction rather than security. Signing a personal account into a browser that is already carrying a managed one costs nothing to do and is awkward to undo. Keeping the managed account in a container of its own, whether that is a separate profile or a separate application window, keeps the boundary where the organisation drew it and removes the question of which session produced a given file.

The failures that send people looking for this

Three specific breakages account for most of the searching.

The first is a link opening in the wrong account. Clicking a Drive or Docs link from Slack, Mail or a calendar invite hands the URL to the default browser, which answers with whichever session it thinks applies. The reply is usually a request access screen, which reads like a permissions failure and is not one. Switching account on that screen normally resolves it, and the address bar afterwards shows which index was wrong.

The second is an export or an upload landing in the wrong Drive. Anything triggered from a page loaded under one account belongs to that account, including scheduled reports and third party tools connected during that session. Moving the file afterwards is possible. Re-authorising the connected tool is often not, without an administrator.

The third is signing out. The menu offers signing out of one account or all of them, and the second option is easy to hit by accident. Everything then has to be added back, in an order that determines the default and every URL index for the next few weeks.

Making the current account visible

Switching errors are recognition errors. The account in use is shown by a small avatar in a corner, at a size that reads well when looking for it and not at all when concentrating on something else.

Three changes make it visible without adding steps. Set a distinct profile photo on each Google account rather than the initial letter, since two accounts belonging to the same person otherwise show the same character in the same colour. Replace /u/N bookmarks with the address form that names the account. And keep one product per account rather than duplicating the whole set, so that the work calendar is only ever reachable in one place.

For anyone already running separate Chrome profiles, a distinct theme colour on each profile is readable from the edge of vision, which an avatar is not. That is a smaller intervention than it sounds, and it removes the class of mistake where an entire morning happens in the wrong identity before anything looks unusual.

When the account is not the thing that needs switching

There is a point where account switching stops being the real problem. It arrives when the switching is not between identities but between tasks, and the identity happens to come along.

The signal is simple. Count how often a switch is followed within a minute by a switch back. If that pattern repeats through the day, the work needs both accounts open at once, and a mechanism built to show one at a time is the wrong shape for it. No amount of tidying the account list changes that, because the constraint is one visible session per product in one window.

What does change it is separating by application and account at the window level, so that two inboxes, two calendars or two admin consoles can sit side by side and be reached by the same gesture used for any other app. Which services can be run that way is listed under supported apps, and the differences against other tools in this category are set out in the comparison with Wavebox.

What to change first

Fix the order before fixing the habits. Sign out of all accounts, sign back in with the account used most as the first one, and replace every /u/N bookmark with the form that names the address. That alone removes most wrong account errors for a two account setup. If the switching continues after that, and especially if it comes in pairs a minute apart, the unit that needs separating is the window rather than the account, which is the case SpaceDeck is built for.