Enterprise SSO means letting your people log in to a tool through your company's own identity provider, almost always using SAML, and on most tools it means buying the top plan to get it. The login is the same single sign-on any company would use. The word "enterprise" is about who the vendor expects to pay for it.
That is the short answer. Below: the two things vendors mean by the term, what gets bundled with it, why it sits at the top of the price list, what it costs a 20-person team, and what a small team can do instead of upgrading.
What vendors mean by it
You will see "enterprise SSO" used in two ways.
On a tool's pricing page, it means your staff sign in through your identity provider (the service that holds your people and checks their passwords: Google Workspace, Microsoft Entra ID, Okta, JumpCloud) instead of with a password stored in the tool. The tool and the identity provider talk through a standard protocol, usually SAML, sometimes OpenID Connect (SAML vs OIDC). The admin can then require that everyone on the company's email domain signs in that way.
That is different from the "Sign in with Google" button many tools offer on every plan. That button logs a person in with their Google account, but the company usually cannot require it or switch off the tool's own passwords, so anyone can still sign in another way. Enterprise SSO is the enforced, company-controlled version.
On a developer platform's pricing page, it means something else: a feature you add to your own product so that your business customers can log in to it through their identity provider. Auth0 and similar services price this per connection (Auth0 pricing covers why that is not workforce SSO). If you are building software, that is the meaning that applies to you. The rest of this post is about the first meaning: buying tools for your own team.
Is enterprise SSO different from SSO? Technically, no. The protocols are the same ones described in what SSO is. The difference is commercial: "enterprise" tells you which plan it is on.
What the plan bundles with it
Vendors rarely sell SSO alone. It comes as part of a security and admin bundle, which is how the jump in price gets justified. Three examples, from each vendor's own pricing page as we read them on 27 October 2026:
| Tool | Plan where SAML SSO starts | Bundled on that plan or above |
|---|---|---|
| Slack | Business+ | SCIM provisioning and data exports for all messages also start on Business+; audit logs are Enterprise+ only |
| Notion | Business | Business adds domain verification and private teamspaces; SCIM, the audit log, SIEM connections and granular admin roles are Enterprise only |
| GitHub | Enterprise ($21 per user a month, Team is $4) | SCIM and Enterprise Managed Users, the audit log API, data residency, and the SOC 1 and SOC 2 Type 2 reports |
The pattern is consistent. SSO sits next to SCIM (the standard that creates and removes accounts automatically, explained here), audit logs, data export and admin controls. Sometimes SCIM is on the same plan as SSO, as at Slack. Sometimes it is a tier higher, as at Notion, so you can pay for enterprise SSO and still remove leavers by hand. Slack SSO and Notion's Business plan go through each of those in detail.
Some of the bundle is genuinely useful to a 20-person company. Most of it was designed for a company with a security team and a compliance department.
Why it sits at the top
SSO is cheap to offer and expensive to buy because it is the clearest signal of a big customer. Large companies cannot buy a tool without it: their security policy requires it, their auditors check for it, and their IT team will not manage hundreds of separate logins. Small companies mostly want it for convenience and can live without it. Put SSO on the top plan and every big customer self-selects into the top price.
The feature does not cost more to run for a large customer than a small one. Once it is built, a SAML connection for 10 people and for 10,000 is the same connection. The price is about who is buying. Why SaaS vendors put SSO on the Enterprise plan goes into the economics in more depth.
The pressure that pushes small companies toward that top plan usually comes from outside. A customer's security questionnaire asks whether you use SSO. An auditor asks how you control access to systems with customer data. Neither one, read closely, usually demands enterprise SSO in every tool you own; they care about the systems in scope and about being able to show who has access. Do you need SSO for SOC 2? looks at what an audit actually asks for, so you can upgrade the tools it names and not the rest.
What it costs
The price shows up in three common ways. The most common is a per-seat upgrade: GitHub's move from Team at $4 to Enterprise at $21 per user a month adds $17 a seat, or $4,080 a year for 20 people, and GitHub Enterprise pricing asks whether that jump pays for itself. Rarer, and easier to swallow, is a flat add-on: a fixed monthly fee for SSO on top of the plan you have. The worst is "contact sales", where the SSO plan has no public price and you find out after a call.
Per-seat upgrades are the ones that add up. For a 20-person team on five common tools, with everyone on a paid seat, the calculator's figures look like this:
| 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 |
| GitHub | Team · $4 a seat | Enterprise · $21 a seat | $4,080 |
| Figma | Professional · $16 a seat | Organization · $55 a seat | $9,360 |
| Notion | Plus · $10 a seat | Business · $20 a seat | $2,400 |
| Zoom | Pro · $14.16 a seat | Business · $18.33 a seat | $1,000.80 |
| Total SSO tax a year | $18,700.80 | ||
That is about $18,700 a year in upgrades for a login button on five tools, before any identity provider. Every new hire makes it bigger, because the gap is charged per seat. Then there is the identity provider on top, unless you use the one in your Google Workspace or Microsoft 365. The SSO tax post explains the pattern, the calculator does the sum for your own tools, and the SSO wall of shame lists the vendors whose markup is steepest.
Questions to ask before you upgrade
Pricing pages say "SSO" and leave the details to the help center. Before you move every seat up a plan, get answers to a few questions, in writing if it is a sales call.
Is it SAML, OIDC, or only certain identity providers? Some tools support a short list of named providers rather than any SAML identity provider. Check that yours is on it, especially if it is Google Workspace.
Can you enforce it? Optional SSO, where people can still use a password, gives you much less. Ask whether an admin can require SSO for everyone on your domain and switch password login off.
Is SCIM on the same plan? If it is a tier higher, you are paying for login and still removing people by hand. Ask whether accounts are created on first login, which is just-in-time provisioning, and whether anything deactivates them when people leave.
What happens to guests and contractors? People outside your domain usually cannot use your SSO. Find out how the tool handles them, and whether they need a seat on the expensive plan too.
Will they put it on your current plan? It costs nothing to ask, and the answer tells you how firm the line is.
Can you get SSO without an Enterprise plan?
Sometimes. A few vendors include SSO on cheap or free plans, and they deserve the credit. Cloudflare says dashboard SSO is available free on all plans, Free included, provided you set up a Cloudflare Zero Trust organization (which has a free tier) and an identity provider (Cloudflare docs). Tailscale signs every user in through an identity provider by design, and its pricing page says SCIM user and group provisioning is on all paid plans, starting with Standard at $8 per user a month (Tailscale pricing). PagerDuty includes SSO on Professional, its cheapest paid incident management plan, at $21 per user a month billed annually; the free plan does not have it (PagerDuty pricing).
All as read on 27 October 2026. The calculator keeps a longer list of tools that include SSO on cheap plans, and free SSO covers what you can get for nothing.
Alternatives for small teams
If a tool you rely on keeps SSO on the top plan, you have more options than paying.
Ask. On an annual contract, ask for SSO on your current plan. Some vendors will say yes for a tool you are committing to.
Use the free version of the login. Where a tool offers "Sign in with Google" on your plan, turn it on and ask people to use it. You lose enforcement, but you get most of the password benefit.
Enforce MFA in the tool itself. Most tools let an admin require it on any plan.
Pay for SSO only where it is required. If a customer contract names three systems, buy enterprise SSO for those three and stop. How to implement SSO covers rolling it out to a short list without lockouts.
Solve the job you wanted it for. For most small teams, that job is adding and removing people across every tool. SSO does not do that by itself, and the plan that adds SCIM is often more expensive still.
Where SmashSSO fits
SmashSSO is not SSO, enterprise or otherwise. It does not touch how anyone logs in. It handles the access side, on the plans you already pay for.
It reads your people from Google Workspace and shows who has an account in each tool and with what role. Access bundles by role, such as "Engineer" or "Sales", invite a new person to every tool in the bundle with the right role; role changes and removals work the same way. Any step that would add a paid seat pauses for your approval, and every change is recorded in an audit log. Changes run through a tool's member API where you have added a token, or through an agent in your own Chrome where you are signed in as an admin; that agent needs the browser open, and some tools' terms restrict automated use.
It is a flat fee from $199 a month billed annually (pricing), with no tool upgrades. If a contract or an auditor requires enforced login through an identity provider, buy enterprise SSO for the systems in scope; SmashSSO is not a substitute for that.