Skip to content

Blog

How to remove someone from Slack

How to remove a user from Slack on every plan: who can deactivate members, the exact steps, guests and Slack Connect, and what happens to their messages.

· 9 min read

To remove a user from Slack, a Workspace Owner or Admin deactivates their account: click Admin in the sidebar, choose Workspace settings, then People, open the three-dots menu next to the person, and select Deactivate account. That works on the Free, Pro and Business+ plans. On Enterprise plans you remove them from a workspace, or deactivate them for the whole organization from Organization settings.

Slack does not delete people, and that is on purpose. Their messages and files stay; they lose the ability to sign in. The steps, permissions and consequences below come from Slack's own help center, read on 27 October 2026 and linked at each point. Slack's interface changes from time to time; if a label in your workspace differs, the linked article is the reference.

Who can deactivate members

Slack's roles are layered, and you can only deactivate people below you. Per Slack's article Deactivate a member's account, it works like this.

On Free, Pro and Business+, Workspace Admins can deactivate members and guests. Workspace Owners can also deactivate Admins, and the Primary Owner can also deactivate Owners. Nobody can deactivate the Primary Owner; that person has to transfer the role to someone else first.

On Enterprise plans, Org Admins and Org Owners can deactivate members, guests, and Workspace Admins and Owners. People with the Security Admin or Users Admin system role can deactivate anyone at the org level except the Org Primary Owner.

The awkward case is a leaver who is the Primary Owner, which in small companies is often whoever created the workspace. The current Primary Owner has to transfer ownership before they go. If they have already left, Slack says it may be able to help for a workspace owned by a company, on a request from a senior staff member, but it does not guarantee it. Sort this out during the notice period. For a dismissal, it's one of the things to plan in advance; the employee termination checklist covers the order.

If the leaver is an Owner or Admin but not the Primary Owner, you can demote them first under Change account type (see Change a member's role), or simply deactivate them if your role is above theirs.

Steps on Free, Pro and Business+

The steps are the same on all three plans.

Open the People list. Click Admin in the sidebar, select Workspace settings, then click People.

Deactivate. Click the three-dots icon next to the member, select Deactivate account, and confirm.

The person is removed from all channels and signed out, and they can't sign back in. Slack does not notify them. Deactivated accounts can be reactivated later from the same list, if someone comes back or you deactivated the wrong person. Reactivating makes them billable again, prorated for the rest of the billing period, under Slack's billing policy.

What Business+ adds is automation. Slack's plans and features page lists SAML single sign-on and SCIM provisioning on Business+ and Enterprise+, and on Free and Pro only for customers who have connected a Salesforce org to Slack. With SCIM, deactivating someone in your identity provider (Okta, Microsoft Entra ID and similar) deactivates them in Slack automatically; our post on what SCIM is explains the mechanism. Without it, someone does the steps above for every leaver. Slack SSO covers what the upgrade costs.

Steps on Enterprise plans

Slack's help center calls these "Enterprise plans"; you may know the structure as Enterprise Grid, where one organization holds several workspaces (Slack Enterprise Grid explains the plan and who needs it). You have two choices, and they do different things.

Remove from one workspace. The person stays in the organization and keeps any other workspaces. Click the workspace name in the sidebar, hover over Tools & settings and select Manage members. Then click the three-dots icon next to the member and select Remove from workspace.

Deactivate across the organization. This is the leaver case. Click the organization name in the sidebar, hover over Tools & settings and select Organization settings. Click People, then Members, tick the member's box and click Deactivate. You can tick several boxes at once.

For someone leaving the company, deactivate at the org level. Removing them from one workspace leaves them in the organization.

Before you deactivate: what to save

Deactivation keeps the person's messages, so there's usually nothing to rescue from Slack itself. Two cases are the exception.

You need a record of their conversations. Slack's export article says Owners and Admins on every plan can export public channel messages and file links. On Business+, Owners can apply to export private channels and direct messages too, with the Primary Owner's approval; on Enterprise you can also apply to export all data from a single user. Exports contain links to files, not the files themselves, and on Free the file links only go back 90 days. If a dispute is possible, ask your lawyer what to keep before you start.

Integrations run under their name. Some apps they installed may stop working when the account goes. Check which apps and workflows your team relies on were set up by the leaver, and reconnect them under someone who is staying before the last day. Our post on revoking access explains why tokens and integrations outlive a login.

Guests and Slack Connect

Guests and external people are where Slack access quietly outlives the work it was for.

Guests. Per Understand guest roles in Slack, guests are only available on paid plans, and come in two types. Multi-Channel Guests can access the channels you specify and are billed like regular members. Single-Channel Guests can access one channel and are free; you can have up to five for every paid active member.

To remove a guest, deactivate them exactly as you would a member: Admins can deactivate guests from the same People list. Better, stop guests outliving their work. Owners and Admins can set a time limit on a guest's account, after a set period or on a date, after which it deactivates. Slack reminds the guest and the admin who set it five days before, and the admin can extend it. For agencies and freelancers, set the limit to the contract's end date; contractor access management covers the rest of a contractor's tools.

Slack Connect. People from other companies in a shared channel are not your accounts. You cannot deactivate them; their own company does that. What you can do, per Slack's external people dashboard article, on Business+ and Enterprise, is one of two things.

Remove them from specific channels. Go to Admin, Workspace settings, People, then External people, find the person, click the three-dots icon and choose Remove from channels.

Disconnect them. The same menu has Disconnect. This removes them from all Slack Connect conversations your organization hosts, though your members can re-invite them while the two organizations stay connected.

The reverse case matters too. If your leaver was invited to another company's workspace as a guest, that account belongs to the other company, and nothing you do in your own Slack removes it. Ask them to.

What happens to their messages and files

Deactivation is not deletion. Slack's deactivation article is explicit: people "aren't notified when their accounts are deactivated, nor are their messages or files deleted." In practice, three things follow.

Messages and files stay in channels and direct messages, attributed to the person, so conversations still make sense afterwards.

Profile details stay too: name, display name, picture. Only a Primary Owner can delete profile information, only after the account is deactivated, and it cannot be undone. Even then, messages, canvases and files the person created are not removed.

Some apps they installed may stop working, as covered above.

Can you delete a Slack user? Not as such. You deactivate the account, and the Primary Owner can delete the profile information afterwards. The messages stay either way.

What it does to your bill

Under Slack's Fair Billing Policy, which applies to plans bought on Slack's website and paid by card or self-serve invoicing, a deactivated member stops being billable and the unused part of the billing period comes back as a credit the next day. Slack also treats anyone who has not used Slack for more than 28 days as inactive and credits their seat.

Credits go toward future bills; Slack says they are non-refundable and expire if your paid plan ends. Single-Channel Guests and bots are free, so removing them saves nothing, though it's still worth doing. And if every member became inactive, Slack would still bill you for one, unless you move to the free version. The policy covers plans bought on Slack's website; if you bought through Slack's sales team, check your contract.

Because of the 28-day rule, a forgotten leaver on a self-serve plan eventually stops costing money. That's the good news. The bad news is that they still have a working account the whole time, which is the point of deactivating them.

A five-person team and a fifty-person one

At five people, one admin deactivates leavers by hand, and that's fine. The risks are the Primary Owner leaving without transferring the role, and the freelancer added as a Multi-Channel Guest last year who's still billed and still reading channels.

At fifty, you'll have several admins, guests from agencies, and maybe Slack Connect channels with customers. The risk shifts to nobody owning the guest list. Put time limits on every guest, check the People list against your staff list monthly, and decide whether SCIM on Business+ is worth it to you. Anything left over is an orphaned account.

Where SmashSSO fits

Deactivating one person in Slack is four clicks. The work is remembering to do it, plus the same clicks in every other tool the person used. SmashSSO reads your people from Google Workspace and shows who has an account in Slack and each of your other tools, and with what role. When someone is suspended in Google Workspace, it alerts you and shows where they still have access, and you remove them from those tools from the same place, through a tool's member API where you have added a token, or an agent in your own Chrome where you are signed in as a Slack admin.

It does not need Business+ or SCIM, and it is not SSO. The Chrome agent needs that browser open, and it can fail when Slack redesigns its screens; a failed run says so and shows its last screenshot. Check Slack's terms on automated use for your plan. It costs a flat fee from $199 a month, billed annually (pricing). For the rest of a leaver's access, start with suspending them in Google (Google Workspace offboarding) and then work through the employee offboarding checklist.

FAQ

How do I remove someone from a Slack workspace?
On Free, Pro and Business+, a Workspace Owner or Admin clicks Admin in the sidebar, then Workspace settings, then People, opens the three-dots menu next to the person and selects Deactivate account. On Enterprise plans, deactivate them for the whole organization from Organization settings, People, Members.
Can I delete a Slack user?
Not as such. Slack deactivates accounts rather than deleting them. After deactivation, the Primary Owner can delete the person's profile information, but their messages, canvases and files stay.
What happens when you deactivate a Slack account?
The person is removed from all channels and signed out, can't sign back in, and isn't notified. Their messages and files stay where they were. On plans bought on Slack's website, the unused part of their paid seat comes back as a credit under Slack's Fair Billing Policy.
How do I remove a guest?
Deactivate them the same way as a member, from the People list in Workspace settings. To stop guests outliving their work, set a time limit on the guest's account so it deactivates automatically on a date.

Keep reading

Stop paying for a login button.

Sign in with Google Workspace, connect your tools, and see who has access to what in minutes.

Sign up with Google