Moving between several Slack workspaces

The short answer is yes. One person can belong to as many Slack workspaces as they get invited to, sign in to all of them in the desktop app at the same time, and move between them with a keystroke. That part has worked for years and takes about ten minutes to set up. The question that actually brings people to a search box is the one underneath it: after the third or fourth workspace, why does the day feel shredded, and which part of the setup is causing it.

Three different things share the same phrase

Before changing anything, it helps to know which of these is being asked about, because the fix for each one is different.

The first is membership in unrelated workspaces. A staff job and a client, a day job and a side project, a company and a community. Each workspace is its own island with its own members, channels, and permissions. This is what most people mean and it needs no administrator involvement beyond an invitation.

The second is a shared channel between two organisations. Instead of joining the other company's workspace, both sides meet inside one channel that appears in each of their own sidebars. Nothing is added to the workspace switcher. For a consultant with eight clients, this keeps the count of workspaces flat while the count of relationships grows.

The third is an organisation that runs several workspaces under one roof, with identity and administration handled centrally. That arrangement belongs to Slack's enterprise tier and is decided by whoever owns the contract, not by an individual member.

Sorting out which of the three applies saves the conversation with an administrator that would otherwise go nowhere.

What stays separate, and what quietly merges

A Slack account is created per workspace. The same email address can be used across many of them, but each one holds its own account record. That single design decision explains most of what follows.

Separate per workspace:

• Display name, profile photo, title, and pronouns
• Status and its expiry
• Notification preferences, keyword triggers, and do not disturb hours
• Channel membership, sidebar order, and saved items
• Installed apps and the permissions granted to them
• Message history, and on the free plan the window of history that remains visible

Shared across all of them, because they live one level up in the operating system:

• The desktop application itself, its theme, and its startup behaviour
• The macOS notification permission, which is granted per application and not per workspace
• One Dock icon and one badge for every unread count combined
• One application in Command Tab and one entry in Mission Control

The split is real inside the app and invisible outside it. Four workspaces produce four sets of preferences and exactly one icon. When a badge appears there is no way to know whose it is without switching, and switching is the thing that costs attention.

Getting around without losing the thread

Everything in the switcher rail on the far left responds to the keyboard, which matters more as the count grows.

• Command and a number jumps straight to the workspace in that position in the rail
• Command, Shift, and the right bracket moves to the next workspace, the left bracket to the previous one
• Command and K opens the jump box for channels and people
• Command and slash lists every shortcut currently available

The number keys follow the visual order of the rail, and that order is draggable. Putting the two workspaces that carry real work at the top means the fingers travel less, every day, for as long as the job lasts. Leaving the order as whatever sequence the invitations arrived in is the most common reason the shortcuts never become automatic.

Search deserves a warning of its own. It runs inside the workspace that is currently open. Memory does not store which workspace a document appeared in, only that it appeared, so the first search often fails and the failure looks like the file is gone. The reliable habit is to think of the person who sent it, switch to the workspace where that person exists, and search there.

Notifications break before anything else does

The setup that collapses is almost always the one where notification settings were left at the default in every workspace. Defaults are tuned for someone who is a member of one. Multiply them by five and the volume passes the point where any of them get read, at which point the genuinely urgent message is treated exactly like the rest.

A workable rule is to give each workspace a different weight, decided once:

Workspace type	Desktop notifications	Keywords	Do not disturb	Mobile push
Main employer	Direct messages and mentions	Two or three project names	Working hours	On
Active client	Direct messages and mentions	Client project name only	Working hours	On
Dormant client	Direct messages only	None	All day	Off
Community	Nothing	None	All day	Off

Do not disturb hours are set per workspace, which is useful when a client sits in a different time zone. The macOS side has no such granularity. The system grants notification permission to the application, so a rule like "silence one workspace at the system level and leave the others audible" cannot be expressed there. Either the app's own settings carry that distinction, or the containers themselves have to be separated.

Closing the ones that no longer earn a place

The least considered way to reduce switching is to switch between fewer things. A finished engagement, a community joined once and never read, a test workspace created during an evaluation: each of these keeps a slot in the rail, shifts the number key assignments, and occasionally fires a notification about something that is no longer anyone's job.

There are three ways to retire one, and they are not interchangeable.

Signing out of a workspace leaves the account and the membership intact and simply removes it from the running app. Everything comes back on the next sign in, which makes this the reversible option.

Deactivating the account and leaving ends the membership. The history stays with the workspace, but personal access to it ends, and getting back in requires a new invitation.

Staying a member with notifications turned off keeps the archive reachable while removing the interruption. This is the right choice while invoices are still open or while a deliverable might still be questioned.

A workable sequence is to mute at the end of a project, then sign out once the final payment clears, and only leave outright when there is no plausible reason to read the history again. Leaving too early removes access to the record of what was agreed, which is exactly the thing that gets requested six months later.

After the count is trimmed, rebuild the rail order deliberately: daily at the top, weekly next, occasional at the bottom. That places the two workspaces that carry real work on the first two number keys, which is where the fingers go without thinking. The order is stored per machine, so anyone working across a laptop and a desktop should set the same order in both, otherwise the shortcuts mean different things depending on which keyboard is in front of them.

The other lever is the form of participation itself. If a relationship is one project and one conversation, a shared channel keeps it off the rail entirely, and asking for that at the start of an engagement costs one message.

The message that goes to the wrong company

Sending something to the wrong organisation is not carelessness. It is a predictable outcome of putting two organisations in the same rectangle of screen, in the same position, with the same layout, reachable by an identical keystroke.

The failure has a shape. Channel names repeat across workspaces, so nearly every one contains a general, a random, and a design. A keyboard switch happens faster than the eye registers the change of colour. Typing begins before the brain confirms which side of the wall it is standing on.

Three defences, in order of how much they help.

Change the sidebar theme per workspace so that colour, not text, carries the identity. Slack allows a different theme in each one and this is the cheapest signal available.

Fix the rail order and never reorder it again. Muscle memory attaches to position, and position that moves is worse than no shortcut at all.

Give each workspace its own window. Slack can open a channel in a separate window, and separate windows put the two organisations in different places on screen rather than in the same one at different times. The limit is that macOS still treats them as windows of one application, so Command Tab will not separate them and the Dock will not either.

When the problem is larger than Slack

Reconstruct an actual hour of work and the switching is not confined to one app. Mail, a document, a ticket, a chat model, a dashboard. Each one sits in a tab or an app of its own, each one raises notifications, and each switch charges the same attention tax as a workspace switch. Halving the cost inside Slack while leaving the rest untouched changes very little.

The alternative approach is not fewer tools. It is fixed places for them. Group the tools that belong to one context into one window, keep that window's contents stable, and switch context by switching window rather than by hunting through tabs. That is the idea behind Workspaces, and it maps onto Slack workspaces directly: the client workspace lives with the client's documents and tickets, not next to the internal standup.

A browser that keeps each web app in its own window is built on that model. Each service is registered as an app and runs in its own isolated area, which is also why two accounts on the same service can stay signed in side by side without one evicting the other. The list of services already handled is on Supported apps, and the practical differences between the products in this category, including price, platform support, and how notifications are handled, are laid out in Compared with Wavebox and Compared with Ferdium. Some of them are free and self-hosted, some are paid, and the honest trade is money against the time it takes to maintain the setup.

What to change first

Start with notifications, not with software. Open each workspace that is currently signed in and decide, one at a time, whether it earns a desktop alert, a keyword, or nothing at all. That single pass removes most of the switching before any tool is involved.

If the screen still runs everything together after that, the next step is separating the containers rather than tuning the settings inside one of them. The pricing and the common objections are set out on Pricing and FAQ, and a closer look at how SpaceDeck isolates each app is the place to check whether that separation is worth paying for.