Slack SSO through SAML is only on Business+ and Enterprise+. Business+ costs $15 per user a month billed annually, against $7.25 for Pro, so SSO adds $7.75 per person a month: $1,860 a year for a 20-person team.
Those prices are on Slack's pricing page in US dollars, as we read it on 27 October 2026. Slack shows prices in your local currency, so you may see different figures. Below: which plans have SSO, what the jump costs at 10, 20 and 50 people, what else Business+ buys you, how SAML and SCIM work in Slack, the login controls Pro already has, and how to remove people without either.
Which Slack plans have SSO
Slack has four plans on its pricing page today: Free, Pro, Business+ and Enterprise+. The cards for Free and Pro list "SAML-based single sign-on" as a feature you don't get. Business+ has it. Enterprise+ adds "Multiple SAML configurations", for companies with more than one identity provider.
Slack's help article on SAML single sign-on says the same thing more plainly: SAML is "Available on the Business+ and Enterprise plans." There is one odd exception. The same article says Free and Pro workspaces can use SAML if they have connected a Salesforce org to Slack. If you don't run Salesforce, ignore it.
| Plan | Billed annually, per user a month | Billed monthly, per user a month | SAML SSO | SCIM |
|---|---|---|---|---|
| Free | $0 | $0 | No | No |
| Pro | $7.25 | $8.75 | No | No |
| Business+ | $15 | $18 | Yes | Yes |
| Enterprise+ | Contact sales | Contact sales | Yes | Yes |
Slack also runs a 50% discount for the first three months on monthly Pro and Business+ plans bought within seven days of creating a workspace. It doesn't apply to annual plans and it ends after three months, so leave it out of your budget.
If you are weighing the top plan rather than Business+, our post on Slack Enterprise Grid covers who needs it.
The price jump
The upgrade is per seat, so every new hire makes it bigger. From the calculator's figures:
| Tool | Plan without SSO | Cheapest plan with SSO | Extra a year, 20 people |
|---|---|---|---|
| Slack | Pro · $7.25 a seat | Business+ · $15 a seat | $1,860 |
| Total SSO tax a year | $1,860 | ||
At 10, 20 and 50 people, with everyone on a paid seat:
| Team size | Pro, a year | Business+, a year | Extra for SSO, annual billing | Extra for SSO, monthly billing |
|---|---|---|---|---|
| 10 | $870 | $1,800 | $930 | $1,110 |
| 20 | $1,740 | $3,600 | $1,860 | $2,220 |
| 50 | $4,350 | $9,000 | $4,650 | $5,550 |
The arithmetic: on annual billing, $15 minus $7.25 is $7.75 a person a month, times 12 months is $93 a person a year. On monthly billing, $18 minus $8.75 is $9.25, or $111 a person a year. Twenty people on annual billing: 20 × $93 = $1,860.
That more than doubles the Slack bill. If the login button is the only reason, you are paying the SSO tax, and Slack is rarely the only tool charging it.
What else Business+ gets you
To be fair to Slack, Business+ is not just Pro with a SAML checkbox. On the pricing page as we read it on 27 October 2026, the Business+ card lists "Advanced AI" where Pro has "Basic AI" (conversation summaries, AI search, daily recaps and file summaries among them), plus "SCIM user management", "EMM integration support" for managing Slack on company phones, and "Native data loss prevention". The comparison table also gives Business+ owners and admins "Data exports for all messages", which covers private channels and direct messages, not just public channels.
So the honest test is this. If you would buy Business+ for the AI features, the full exports or data loss prevention anyway, SSO and SCIM come free with it and the question is closed. If none of those matter to you, and the people asking for SSO are really asking "how do we make sure leavers lose Slack", there is a cheaper answer further down. A 5-person company that wants AI summaries has a different decision from a 50-person company that only wants the login, even though the per-seat price is the same for both.
Setting up SAML in Slack
If you do move to Business+, setup is short. A Workspace Owner or Org Owner does it, with someone who can create an app in your identity provider. Slack links a guide for Okta, Microsoft Entra ID, Google Workspace, JumpCloud, OneLogin and others; our post on using Google Workspace as your identity provider covers the Google side.
Start in the identity provider. Create the Slack app there and note its sign-in URL, issuer and certificate. Then switch to Slack. Open the admin settings, go to the security or SSO section and choose to configure SAML. Paste in the SAML 2.0 endpoint URL, the identity provider issuer and the full X.509 certificate. Test before you enforce. Choose whether responses and assertions are signed, run Slack's test, and only then turn SSO on and decide how strict to be.
That last choice matters. Slack offers three settings: SSO required for everyone, required for everyone except guests, or optional. If you work with guests from other companies, Slack itself recommends the middle option, so guests can still sign in with email and password.
People who are already signed in when you switch it on stay signed in. Members who must now use SSO get an email asking them to link their Slack account to the identity provider within 72 hours.
SCIM in Slack
SAML decides how people sign in. It doesn't create or remove accounts. That is SCIM's job (System for Cross-domain Identity Management, the standard identity providers use to push account changes into apps; our SCIM explainer has the detail, and SCIM vs SAML shows why the two get confused).
Slack's SCIM article puts it on the same plans as SAML: Business+ and Enterprise, or Free and Pro with a connected Salesforce org. With it, your identity provider can create and deactivate members, update their profile fields, create user groups, and add or remove people from those groups. As we read it on 27 October 2026, the article names Google Workspace, Microsoft Entra, Okta, OneLogin, PingFederate and PingOne as supported identity providers, with a custom script against Slack's SCIM API as the fallback. Owners and Admins set it up, and the identity provider asks for an API token that Slack issues through an OAuth flow; each provider's guide walks through that step.
There are two catches. On Business+, guests can't be provisioned directly; you create a member through SCIM and then change their role. And SCIM-created members become billable when they first sign in, with the charge prorated for the rest of the billing period, so a directory sync with stale accounts in it can cost you seats.
So yes, on Business+ your identity provider can deactivate leavers in Slack automatically. That is the real feature most small teams are after, and it is SCIM, not SAML, that does it.
Can you use Google sign-in without SAML?
Yes, and this is the part Slack's upgrade page doesn't advertise. Slack's Google Workspace single sign-on article describes two options. Google Auth, which uses OAuth (a different standard from SAML), is available on Pro and Business+. You turn it on under Admin, Workspace settings, Security, SSO & authentication, and members then sign in with their Google account. Google SAML, by contrast, needs Business+ or Enterprise.
The difference, in Slack's own comparison table: automatic user deactivation comes with Google SAML only. With Google Auth on Pro, nothing happens to the Slack account when someone leaves; deactivating it is still your job.
The login controls Pro already has
Pro also lets you force two-factor authentication. Slack's mandatory 2FA setting is "Available on all plans": Admin, Workspace settings, Security, then tick "Require members to have 2FA set up". You can restrict it to authenticator apps only. If you are unsure whether you need that or SSO, our post on SSO vs MFA sets out what each one protects against.
Slack's session duration setting is the other one, and it is also "Available on all plans", as we read it on 27 October 2026. A Workspace Owner or Admin opens Admin, Workspace settings, Security, and edits the desktop or mobile session duration. You can make people sign in again every time they close Slack, or after a set period. Slack warns members two hours before their session ends and again 15 minutes before. That matters for leavers: a shorter session means a former employee with the app still open on a personal laptop is thrown out sooner, even if you forget them for a while.
Google sign-in, forced 2FA and a sensible session length cover most of what a small company wants from SSO. What they don't cover is the leaver.
Removing people from Slack without SSO
On Free, Pro and Business+, a Workspace Admin or Owner deactivates a member in four clicks. First, click Admin in the sidebar and choose Workspace settings, then People. Next, find the person and click the three dots next to their name. Finally, choose Deactivate account and confirm.
They are signed out on every device, removed from all channels and can't sign back in. Their messages and files stay. Admins can deactivate members and guests; deactivating an admin takes an Owner, and an Owner takes the Primary Owner.
The billing side is gentler than most tools. Under Slack's Fair Billing Policy, a deactivated member becomes inactive immediately, and credit for the unused part of the billing period lands in your account the next day. Members who haven't used Slack in over 28 days are also treated as inactive and credited automatically. The credits only count against future Slack bills; they are not refunded.
That softens the cost of forgetting someone, but it doesn't fix the access problem: until you deactivate them, a former employee who still has the app open is still in your channels. Guests are the usual blind spot. A freelancer invited to two channels for a project in spring is still there in autumn unless someone removes them, and SAML set to "everyone except guests" won't stop them signing in. We go through the whole process, including guests, Slack Connect channels and apps a leaver installed, in how to remove someone from Slack, and the rest of a leaver's tools are in our employee offboarding checklist.
What to do this week
Open your Slack member list, sort by account type and look at guests and anyone you don't recognize. Turn on Google Auth if you haven't, require 2FA, and set a session length you can live with. Then price Business+ honestly: if you would use its AI, exports or data loss prevention, buy it and get SSO and SCIM thrown in. If you wouldn't, the SSO tax calculator will show you what the same upgrade costs across the rest of your tools before you commit to any of them.
Where SmashSSO fits
SmashSSO does the Slack part of joining and leaving from the same place as your other tools, on the plan you already pay for. It reads your people from Google Workspace, reads who is in your Slack workspace and with what role, and matches them by email; Slack accounts that match nobody in your directory are flagged. When someone is suspended in Google Workspace, SmashSSO alerts you and shows Slack among the tools they can still get into.
Invites, role changes and deactivations in Slack run through an agent in your own Chrome, in a tab where you are already signed in as a Slack admin. That browser has to be open, the agent is slower than an API, and a run can fail if Slack redesigns its admin screens; a failed run says so and shows its last screenshot. Inviting someone to a paid workspace adds a seat, so that step waits for your approval, and every change lands in an audit log.
It isn't SSO. If a customer or auditor requires that your team signs in to Slack through an identity provider, you need Business+. If what you need is Google sign-in and leavers out of Slack the day they go, Pro with Google Auth plus SmashSSO does that for a flat fee from $199 a month, billed annually, however many people and tools you have (pricing).