One email address across several Slack workspaces

The same address is in five Slack workspaces. The employer, two clients, a community, and one left over from a project that ended eighteen months ago. The sidebar rail holds all of them, the Dock badge shows a number that could mean anything, and answering the wrong person in the wrong workspace has already happened at least once.

The first thing to establish is that none of this is a misconfiguration. Slack allows one email address to belong to as many workspaces as it likes, and that is the intended design. The friction comes from what that design implies, which is that five workspaces are five separate accounts that happen to share a login address, and almost nothing is shared between them.

One address, several accounts

A Slack account belongs to a workspace, not to a person. Signing up for a second workspace with an address already in use creates a second account. The address is the same, the identity is not.

That has consequences people discover one at a time:

• The display name, full name, title, pronouns and profile photo are stored per workspace. Changing the photo in one changes nothing anywhere else.
• Notification preferences, keyword highlights and Do Not Disturb schedules are per workspace. A quiet hours schedule set once has to be set again for every membership.
• Status, including the emoji and the expiry, is per workspace. A status saying "on holiday" only says it where it was typed.
• Saved items, drafts, reminders and the sidebar arrangement are per workspace.
• Two factor authentication is enforced per workspace, so one workspace can require it while another does not.

What is shared is the sign in path. Slack looks up which workspaces an address belongs to, which is how the desktop application can add another one without a fresh password, and how a magic link email can land in the right place.

Finding every workspace the address is already in

Before rearranging anything, it is worth knowing the full list. Slack has a lookup that emails every workspace associated with an address, reached from the sign in page under the option to find workspaces. It asks for the address, sends a message, and the message contains the complete set including the ones long forgotten.

This is also the fastest way to answer a question that comes up during offboarding and account cleanup, which is whether an address is still a member somewhere it should not be. Membership does not lapse on its own. A workspace from a finished project keeps the account active, keeps sending notifications, and keeps that address in the member list until somebody removes it.

What the browser does differently from the app

Slack gives each workspace its own subdomain, in the form workspacename.slack.com. That detail is the reason the browser handles several workspaces better than several accounts of most other services.

Because cookies are scoped per subdomain, two Slack workspaces open in two browser tabs do not collide. Both stay signed in indefinitely. There is no session negotiation, no numbered account index, and no risk that refreshing one tab silently switches it to another workspace. Anyone who has fought with two accounts on a service that keeps one session per browser will find Slack unusually cooperative here.

Approach	Holds every workspace	Distinct notification identity	Own Cmd+Tab slot	Restores the arrangement
Slack desktop app	Yes	No, one application	No, one entry	Yes, the rail persists
Browser tabs	Yes	No, one browser	No	Only if the tabs survive
Browser profile per workspace	Yes	No, one browser	No	Partly
One isolated window per workspace	Yes	Yes	Yes	Yes

The table makes the pattern visible. Almost every arrangement holds the workspaces perfectly well. What varies is whether the operating system can tell them apart, and that is where the real cost sits.

The identity problem in the Dock

The desktop application is the arrangement most people already use, and it is good at the thing it was built for. The workspace rail on the left holds every membership, Cmd plus a number jumps directly to a workspace, and unread state is visible per workspace inside the window.

What it cannot do is expose that distinction to macOS. Slack is one application with one bundle identifier, so:

• The Dock badge aggregates. A number appears, and finding out which workspace produced it means opening the application first.
• Notification banners say Slack. The workspace name appears in the body of the banner if the notification is long enough to include it, and disappears if it is not.
• Cmd+Tab has one Slack entry. Reaching a specific workspace is a Cmd+Tab followed by a rail click, which is two steps where one was expected.
• Quitting quits everything. There is no way to close the finished client workspace while keeping the employer's open.

For two workspaces this is a minor annoyance. For five it stops being minor, because the badge stops carrying information. A number that could be any of five sources is not a signal, it is a prompt to go and look, and that lookup happens dozens of times a day.

Notification settings help less than expected

The standard advice is to turn notifications down in the workspaces that matter least. It does help, and it should be done. Per workspace settings allow all messages, direct messages and keywords only, or nothing, plus separate schedules.

The limit is that this reduces volume without restoring identity. A quieter badge is still a badge whose source is unknown. Anyone whose problem is "which workspace was that" rather than "too many notifications" will tune the settings for an afternoon and end up in the same place.

Enterprise Grid is the exception worth knowing

There is one arrangement where several workspaces genuinely share an account. Enterprise Grid connects multiple workspaces under one organisation, and a member has a single identity across them with a shared profile and centrally managed policies.

This is a paid organisational tier, provisioned by an employer, and it applies only to workspaces inside that one organisation. It does nothing for the common case in this search, which is one person belonging to workspaces owned by several unrelated companies. Those remain separate accounts under any plan, because they belong to different organisations.

Slack Connect is a different feature that is sometimes confused with this. It shares a channel between two workspaces rather than merging accounts, which is often the better answer for a single ongoing client relationship. One shared channel inside the main workspace removes a membership entirely, and a membership removed is a switching cost that no longer exists.

Setting up the memberships that stay

For the workspaces that cannot be left, a few minutes of per workspace configuration removes most of the recurring friction. All of it has to be repeated in each workspace, because none of these settings are shared.

Set the display name to say which side you are on. In a client workspace, a display name carrying the company or role is more useful than the same name used everywhere else. It also makes screenshots and search results unambiguous months later.

Set a Do Not Disturb schedule per workspace. A client workspace in a different time zone should not be able to send a banner at midnight local time. The schedule is under notification preferences and it is the only per workspace control that reliably stops a notification before it reaches the operating system.

Set the notification level by workspace, not by channel. Direct messages and mentions only is the right default for anything that is not the main employer. Channel by channel tuning is more precise and it does not survive the workspace being reorganised, so it needs redoing every few months.

Use a different profile photo in each. This is the one change that makes a screenshot, a search result or a shared link immediately identifiable. It costs a minute per workspace and it is the single highest return item on this list.

The membership that cannot be left

Sometimes leaving is not available, because the account is the only route to a shared history or because an employer requires it. In that case the workspace can be muted almost completely: notifications off entirely, the workspace collapsed in the rail, and any mobile notification disabled separately, since mobile settings are stored independently from desktop settings.

That last detail catches people out. Turning notifications off on the Mac does nothing to the phone, and the phone will keep delivering the same interruptions from a workspace the reader believed was silenced.

The switching cost nobody counts

Adding a workspace is free. The cost arrives later, distributed across the day in pieces too small to notice individually.

Every ambiguous badge is a lookup. Every lookup is a context switch out of whatever was in progress. Someone in five workspaces performs that lookup often enough that it becomes the dominant interaction with the tool, and the natural response is to leave Slack in front all the time, which converts an occasional interruption into a permanent one.

The structural fix is to make the workspaces distinguishable before they reach attention, which means each one having its own window, its own icon and its own notification identity at the operating system level rather than only inside the application. A browser that keeps each web app in its own window does exactly this by opening every workspace as a separate window with an isolated session, so the badge that appears already carries the answer. Whether that is worth changing tools for depends on the number of memberships, and the feature list is the place to check it against the table above. For people whose memberships cluster into groups, one client in the morning and another in the afternoon, saving those groups as workspaces removes the switching decision entirely.

Before any of that, there is a cheaper move available to everyone: leave the workspaces that are finished. The project that ended, the community last read a year ago, the trial workspace created to test something. Each departure removes a badge source permanently and costs nothing.

Leaving is done from the workspace itself, under the account menu, and it is reversible only by a new invitation, so it is worth exporting or saving anything needed first. Data belongs to the workspace owner rather than to the member, which is another reason a finished membership is a liability rather than an archive. Anyone worried about losing a reference should save the specific messages that matter before leaving, because access ends immediately and the search history goes with it.

What to change first

Run the workspace lookup from the sign in page and leave everything that is genuinely over. Then set Do Not Disturb schedules per workspace on what remains, since those are the only per workspace controls Slack offers. If the badge is still ambiguous after that, the missing piece is identity rather than volume, and giving each workspace its own window is what supplies it, as SpaceDeck does.