Living with more than one Gmail account

Three Gmail accounts is not unusual. A personal address that has been in use since school, a work address on Google Workspace, and a third one attached to a side project or a client who insisted on their own domain. Google supports all three being signed in at once, which sounds like the problem is solved. Then a reply goes out from the wrong address, a shared link opens someone else's inbox, and a notification arrives with no indication of which account it came from.

None of that is a mistake by the person using it. It is the predictable result of how multiple sign in works, and the fix depends on knowing exactly where the design stops helping.

The account switcher stacks accounts, it does not separate them

Signing into a second Google Account in the same browser adds it to the switcher in the top right corner. Behind that, Google assigns each signed in account a number and puts it in the address: mail.google.com/mail/u/0/ for the first, /u/1/ for the second, /u/2/ for the third.

That number is a position in a list, not a name. It is assigned in the order the accounts were signed in, on that browser, on that machine. Two consequences follow, and both of them are the source of the classic complaints about having multiple Gmail accounts.

The first is that the number moves. Sign out of the account sitting at /u/1 and the one that was at /u/2 slides down to take its place. Every bookmark, every saved link, and every muscle memory shortcut that pointed at /u/2 now opens a different mailbox. Nothing warns about this.

The second is that the number is local. A link copied out of the address bar carries /u/1 in it, and /u/1 means something entirely different on a colleague's machine. Sending a Google Docs or Gmail link with the index in it is why the recipient sees a permission error while the sender sees the document perfectly. Stripping the /u/N/ segment out of a link before sharing it fixes that particular problem every time.

There is one more behaviour worth knowing. Signing out of a single account in the switcher signs out of all the accounts in that browser at once. There is no way to leave two signed in and drop the third.

Where multiple sign in quietly gives up

Gmail, Drive, and Calendar handle several accounts reasonably well in one browser. The rest of the Google product surface is uneven, and the failure is silent rather than loud.

Some products do not implement multiple sign in at all and simply act on whichever account holds position zero. A link is opened, the page loads, and it loads under the wrong identity without any prompt. Third party sites that offer sign in with Google are a common version of this, since the sign in flow tends to reach for the default account rather than the one currently in view.

Anything that runs outside a browser tab has the same issue in stronger form. Desktop notifications from Gmail in the browser come from the browser, so they arrive with the browser's identity attached, not the account's. A notification that says a new message arrived does not say which of the three inboxes it landed in. Clicking it usually opens the tab that was already there, which may be a different account than the one that received the mail.

This is the point where the browser tab stops being a workable container for a Gmail account, and where the choice of separation actually matters.

Four shapes, and what each one costs

There are four common arrangements. They are not equally good, but each is genuinely the right answer for someone.

	Same window, account switcher	Separate browser profiles	Separate windows per account	One inbox, mail pulled in
Accounts stay signed in together	Yes	Yes	Yes	One account only
Wrong sender address risk	High	Low	Low	Moderate
/u/N index problems	Yes	No	No	Not applicable
Notifications identify the account	No	No	Yes	Not applicable
Separate Dock icon per account	No	No	Yes	No
Extensions and settings shared	Yes	No	Depends on the tool	Yes
Setup effort	None	Ten minutes	Ten minutes	Thirty minutes

The switcher costs nothing and works until roughly the second account. Browser profiles are the standard escalation and they solve the identity problem completely, at the price of every profile being another window of the same application, sharing one Dock icon and one name in Command Tab. A window per account is the arrangement that makes notifications legible, because the notification then belongs to something with its own name and its own icon.

Folding several accounts into one inbox

The other direction is worth taking seriously. Instead of separating the accounts more cleanly, reduce how many need to be open at all.

Gmail can collect mail from other accounts. In Settings, under Accounts and Import, Check mail from other accounts fetches by POP from up to five other addresses and drops the results into the current inbox. Paired with Send mail as, which lets a verified address be chosen in the From field of any reply, one Gmail window can genuinely stand in for several mailboxes.

That arrangement has three specific costs, and they decide whether it fits.

Fetching by POP is a poll, not a push, so mail arrives on Gmail's own schedule rather than instantly. For an address that receives a newsletter and an occasional invoice, that is fine. For anything where a five minute delay matters, it is not.

The default sender becomes a live risk. With four From addresses available in one window, replying from the wrong one is a matter of not reading a dropdown. Setting each fetched address to reply from the same address the mail was sent to reduces this considerably, and it is a setting worth checking rather than assuming.

Filters and labels do the work that separate inboxes used to do for free. Mail from all the addresses lands in one stream, so a label per address, applied automatically on arrival, is not optional decoration. Without it the consolidation trades an account switching problem for a triage problem.

Gmail delegation is a fourth option that gets overlooked. Where the accounts are separate people or separate roles rather than separate identities of the same person, granting delegate access lets one account read and reply on behalf of another, with the sent messages recorded as being sent on behalf of the account that owns them.

Some of these accounts do not need to exist

Before arranging anything, it is worth checking whether every address on the list actually requires its own account. A share of them usually do not.

Gmail ignores dots in the local part of a consumer address. Mail sent to [email protected] and [email protected] arrives in the same inbox, which means an address written with dots on a business card is not a separate account and never was. Gmail also supports plus addressing, so [email protected] delivers to the same place while carrying a tag that a filter can act on. Signing up for services with a tagged address gives a per service label at no cost and makes it obvious later which service leaked an address.

On Google Workspace, an administrator can attach alias addresses to an existing account. Mail to the alias lands in the same mailbox, and the alias can be selected in the From field, so a role address such as billing@ does not need a separate login, a separate password, or a separate window. Accounts created purely to hold a second address are the ones most often worth collapsing.

The distinction that matters is ownership. An alias is another door into the same mailbox, so anyone with the account has it. A separate account is a separate mailbox with its own history, its own Drive, and its own permissions, which is what is needed when the address will one day be handed to someone else, or when it has to survive the current person leaving.

Running this check first usually removes one or two entries from the list, and every entry removed is a window, a set of notification rules, and a daily decision that never has to be made.

Notifications decide more than the layout does

The strongest argument for any particular arrangement is not tidiness. It is which one makes it possible to ignore an inbox on purpose.

Two Gmail accounts in one browser produce notifications that all look identical, which forces a check to find out what arrived. That check is the expensive part. It is not the thirty seconds spent reading, it is the interruption of whatever was in progress at the time.

Separation that carries through to the operating system fixes this at the source. When an account has its own window and its own application entry, macOS can be told to allow notifications from the work account and silence the personal one during the day, then reverse it in the evening. That is a setting in System Settings, applied once, and it removes a whole class of interruption without any discipline being required.

The same reasoning explains why muting is hard in a single browser window. There is one notification permission for the browser, so the choice is all accounts or none.

Matching the arrangement to how the accounts are used

A short test sorts most situations. For each account, answer whether mail sent from it needs to look like it came from that address, and whether mail arriving at it needs attention within the hour.

Accounts that need neither belong in the consolidated inbox. An address that receives receipts and delivery notices does not need its own window, its own icon, or its own notification rules. It needs a label.

Accounts that need both belong in their own container. A work account and a client account both send mail that must carry the correct address and both receive mail that has to be seen promptly. Those are the accounts that earn separate windows and separate notification settings, and they are usually the two that were causing the trouble in the first place.

Accounts that need one but not the other sit in the middle, and the answer there depends on volume. An address that must send correctly but rarely receives anything works well as a Send mail as entry on the main account.

A browser built to keep each web application in its own window applies the same logic to everything else that has accumulated alongside the mail. Slack, a calendar, a project tool, and a client dashboard have the same problem as the second Gmail account, which is that they are all tabs in a window whose identity is the browser's rather than their own. The Workspaces page covers how the sessions are held apart, Supported apps lists the services already set up to run this way, and Compared with Shift is the useful reference for anyone who reached this question after looking at the established tools in the category.

What to change first

Start by writing down each Gmail address and answering the two questions above, because that produces the arrangement rather than guessing at it. Then strip the /u/N/ segment out of any Gmail or Drive link before sharing it, which costs nothing and removes the most common daily annoyance. If two of the accounts turn out to need their own notification rules, that is the point at which a SpaceDeck style window per account is doing something the account switcher cannot.