An identity provider (IdP) is the system that holds your company's list of people, checks their passwords and second factors, and vouches for them to your other tools. When you log in to Slack "with SSO", Slack does not check who you are. It asks the identity provider, and believes the answer.
If your company runs on Google Workspace or Microsoft 365, you already have one. Whether you need a second, dedicated one is a different question, and for most small teams the answer is not yet.
The definition
An identity provider does three jobs.
It stores identities. It keeps a directory of people: name, work email, password, second factors, groups such as "Sales" or "Engineering", and whether the account is active or suspended.
It authenticates them. It runs the login page, checks the password, asks for the second factor, and applies whatever rules you set: MFA required, certain devices only, certain countries blocked.
It vouches for them. After a successful login it sends a signed statement to the tool that asked, saying who the person is. That statement is a SAML assertion or an OpenID Connect ID token, depending on the protocol; what SAML is and what OIDC is cover each.
The third job is what makes single sign-on possible. A login is checked once, in one place, and accepted everywhere that trusts the identity provider. What SSO is explains the idea from the employee's side.
So what is the difference between an IdP and SSO? The identity provider is the system that checks who someone is. SSO is the arrangement that lets your tools accept its word instead of their own passwords. You need an identity provider to do SSO, but you also need tools, and tool plans, that accept it. When people say "SSO IdP", they mean the identity provider in that arrangement.
Identity provider vs service provider
SSO always involves two roles, and the jargon is unhelpfully similar:
| Identity provider (IdP) | Service provider (SP) | |
|---|---|---|
| What it is | The system that knows who your people are | The tool people want to use |
| Examples | Google Workspace, Entra ID, Okta, JumpCloud | Slack, GitHub, Figma, HubSpot, Jira |
| In a login it | Checks the password and MFA, signs a note | Checks the note's signature, opens a session |
| Holds passwords? | Yes | Not for SSO users |
| Set up | Once for the company | Once per tool, linked to the identity provider |
The same company can be both. Google is a service provider when you use Google Docs, and an identity provider when Google Workspace logs you in to Figma. OpenID Connect calls the two sides "OpenID provider" and "relying party"; same idea, different words. How SSO works follows one login between the two, step by step.
You probably have one already: Google Workspace or Microsoft 365
Most small businesses buy email and documents from Google or Microsoft, and both come with a directory that can act as an identity provider.
Google Workspace stores your users, enforces 2-Step Verification, and can log people in to other tools in two ways. Any tool with "Sign in with Google" uses it through OpenID Connect, with no setup on your side. And an admin can add a tool as a SAML app in the Admin console, so that Google becomes the tool's SSO identity provider. Google's custom SAML app help page, as we read it on 27 October 2026, says a super administrator does this under Apps, then Web and mobile apps, and can turn each app on for everyone, for organizational units or for groups. That last part is useful: it lets you say "only Engineering gets GitHub" in one place. Google Workspace SSO goes through the setup.
Microsoft 365 comes with Microsoft Entra ID (formerly Azure Active Directory). Microsoft's Entra pricing page, as we read it on 27 October 2026, describes Entra ID Free as included with Microsoft 365 or Azure subscriptions and lists SSO among its features. Entra ID P1, which adds Conditional Access (rules about who may sign in from where and on what device), is $7 per user a month paid yearly on its own, and the page says it is included in Microsoft 365 Business Premium.
Before shopping for anything, check how well the one you have is set up. Is 2-Step Verification enforced for everyone, not just available? How many people are super admins? Each one is a key to every connected tool. Which SAML apps already exist, and when do their certificates expire? Google's SAML certificate page gives its certificates a five-year lifetime and lists each one's expiry date under Security, then Authentication, then SSO with SAML applications. An app set up years ago by someone who has since left is exactly the kind that stops working one Monday morning.
So the identity provider is usually not the thing you are missing. What is missing is a tool plan that will accept it, which is where the SSO tax comes in.
Dedicated identity providers: Okta, JumpCloud, Entra ID
Dedicated identity providers do the same core job with more of everything: bigger catalogs of pre-built app connections, more detailed login rules, provisioning into tools, reporting. Prices below are from each vendor's own pricing page, read on 27 October 2026.
| Identity provider | Entry price for SSO | Billing and minimums | Source |
|---|---|---|---|
| Okta | Starter suite, $6 per user a month (Essentials $17) | Billed annually; $1,500 annual contract minimum | okta.com/pricing |
| JumpCloud | SSO package, $11 per user a month ($13 billed monthly) | Monthly or annual; 30-day free trial | jumpcloud.com/pricing |
| Microsoft Entra ID | Free with Microsoft 365; P1 $7, P2 $10 per user a month | P1 and P2 paid yearly | Entra pricing |
The table hides three things.
Okta's minimum. At $6 a user, the $1,500 yearly minimum covers about 20 people, so a team of 8 pays the same as a team of 20. Okta's Starter includes SSO and MFA; Lifecycle Management, the part that creates and removes accounts in your tools, is an add-on on Starter and included from Essentials. Okta pricing works through it.
JumpCloud's packaging. Its SSO package is described as "SSO & MFA access to resources plus Password Manager". It also sells SSO on its own, à la carte, at $3 per user a month billed annually. JumpCloud pricing has the full list.
Entra's catch. Entra ID Free covers SSO, but the controls most companies want with it, such as Conditional Access, start at P1. Microsoft Entra ID pricing covers when P1 is worth it.
None of these changes what your tools charge. A dedicated identity provider can sign people in to Slack only if your Slack plan accepts SSO.
What an IdP can and cannot do for your tools
Start with what it can do. It gives you one login, with MFA, everywhere it is connected, which is the biggest practical security gain for most companies. It stops new logins instantly: suspend someone and no connected tool will let them start a new session. It centralizes rules and logs, so you set who may sign in, from what, in one place, and keep a record of who signed in where. And it can provision accounts, if the identity provider supports it on your plan and the tool supports SCIM on yours. SCIM vs SAML explains why that is two conditions, not one.
Now what it cannot do. It cannot reach tools that do not support SSO, or that support it only on a plan you do not have; those keep their own passwords. It cannot end sessions that are already open in most tools, because the tool runs its own session after login. It cannot remove accounts without provisioning. A suspended user's accounts and paid seats stay in every tool until something deletes them. And it cannot tell you what you pay for. It knows logins, not invoices or empty seats.
That second list is why a company can own a perfectly good identity provider and still have a former employee in four tools.
Choosing one as a small business
Work through four questions, in this order.
What do you already pay for? If it is Google Workspace or Microsoft 365, start there. Turn on and enforce MFA for everyone. That alone is most of the security value, and SSO vs MFA explains why it comes first.
Do your important tools offer "Sign in with Google" or "Sign in with Microsoft" on your current plans? Use it. It is SSO in practice, if not enforced, and costs nothing.
Does anyone require enforced SSO? A customer contract or an auditor asking for login through an identity provider means you need it for the systems in scope, and the tool plans that allow it.
Only then: do you need a dedicated identity provider? Usually when you have both Google and Microsoft accounts to unify, devices to manage, or many tools whose SSO setups Google does not handle well. Okta alternatives compares the options.
Two sketches make it concrete. A 6-person agency on Google Workspace, with a dozen tools and no enterprise customers, has its identity provider already. It should enforce 2-Step Verification, use "Sign in with Google" everywhere it is offered, and spend nothing more on identity this year. A 45-person software company with a customer contract that names SSO, a few Windows laptops and contractors on outside email addresses has a real case for looking at a dedicated identity provider. Even then, the bigger bill will be the tool upgrades, not the identity provider.
If your real problem is that nobody is sure who still has access to what, a new identity provider will not solve it on its own. That is an accounts problem, not a login problem.
Where SmashSSO fits
SmashSSO is not an identity provider. It does not run a login page, store passwords or issue assertions, and people keep logging in to each tool the way they do now.
It uses the directory you already have. It reads your people from Google Workspace with read-only access, shows who has an account in each tool and with what role, and flags accounts that match nobody in your directory. Access bundles by role add people to every tool they need, and when someone is suspended in Google Workspace, it alerts you and shows where they still have access, so you can remove them. 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 already signed in as an admin; that browser has to be open, and agent runs can fail when a tool redesigns its screens.
It needs Google Workspace as the directory and has no SOC 2 report. It costs a flat fee from $199 a month billed annually, however many people and tools (pricing). If you need enforced login, you need an identity provider and the tool plans that accept it.