Skip to content

Blog

What is SSO? Single sign-on in plain English

What is SSO? Single sign-on means one login for all your work tools. How it works, what it costs, what it does not do, and who actually needs it.

· 10 min read

What is SSO? SSO stands for single sign-on: your people log in once, to one account, and that account signs them in to all their work tools. Instead of a separate password for Slack, GitHub, Figma and Notion, they have one login, usually their Google Workspace or Microsoft account, or one run by a dedicated provider such as Okta.

That is the whole idea. The rest of this post covers what it looks like day to day, the pieces that make it work, what it costs, and the jobs people assume it does that it does not.

SSO in one sentence, and what the letters stand for

Single sign-on lets a person prove who they are once, to one trusted service, and have every other tool accept that proof instead of asking for its own password.

The letters are literal. "Single" because there is one account and one login. "Sign-on" is just another word for logging in. So when someone asks what SSO means, the honest answer is "one login for everything that is connected to it". The last four words matter, and most of this post is about them.

The trusted service is called the identity provider. The tools that accept its word are called service providers. The language they use to talk to each other is a protocol, almost always SAML or OpenID Connect (OIDC).

What it looks like for an employee

Someone opens Slack. Instead of a password box, they see "Sign in with SSO" or are sent straight to a company login page. If they already signed in to the identity provider this morning, they are bounced back into Slack without typing anything. If not, they enter their one password and their second factor, once, and from then on every connected tool opens without asking.

For them, SSO means one password to remember and fewer login screens. It also means one place to reset that password, and one set of MFA prompts instead of a different authenticator code for every tool. When it works well, they barely notice it. When the identity provider is down, they notice it everywhere at once.

What it looks like for whoever runs IT

For the person who manages access, SSO gives three things.

One place to set login rules. MFA, password strength, which devices and countries can sign in. You set them once in the identity provider and they apply to every connected tool, instead of hunting for the security page in each admin console.

One switch for future logins. Disable a person in the identity provider and they cannot start a new session in any SSO-connected tool. That is real, and it is the feature most people buy SSO for.

One log of who signed in where. When something looks wrong, you can see which tools an account touched and when, from one screen.

It also brings one new risk: the identity provider becomes the key to everything. If that account is taken over, every connected tool is open. That is why SSO and MFA are bought together, and why SSO vs MFA is a "both" answer rather than a choice.

The pieces: identity provider, service provider, protocol

Identity provider (IdP). The service that holds your list of people and checks their passwords. Google Workspace, Microsoft Entra ID, Okta, JumpCloud and OneLogin are all identity providers. If your company runs on Google Workspace, you already have one. What an identity provider is covers whether you need a second one, and Okta pricing shows what a dedicated one costs.

Service provider (SP). Any tool your people log in to: Slack, Zoom, HubSpot, Jira. The tool has to support SSO, and usually only does so on certain plans.

Protocol. The agreed way for the two to exchange "this is Ana, she has signed in". Workplace tools mostly use SAML, an XML-based standard from 2005 (what SAML is). Newer apps often use OpenID Connect, built on OAuth (SAML vs OIDC). Your people never see the difference. OAuth, often mentioned alongside them, does a different job: it lets one app use another's data (SAML vs OAuth).

Put together, a login runs like this. The tool sends the person's browser to the identity provider. The identity provider checks the password and second factor, then sends the browser back with a signed message naming the person. The tool checks the signature and opens a session. The tool never sees the password. How SSO works traces that round trip step by step, including the parts that fail.

Is "Sign in with Google" SSO?

In practice, yes. When a tool offers a "Sign in with Google" or "Sign in with Microsoft" button, your people log in with their work account and the tool accepts Google's or Microsoft's word for who they are. That runs on OpenID Connect, and it gives you one password, your MFA rules, and no separate password per tool. Many tools offer it on every plan, free.

What it usually lacks is enforcement. The tool still lets people create an ordinary email-and-password account alongside it. You cannot require that everyone at your domain logs in through Google, and you cannot stop someone who set a password last year from using it after they leave. Requiring login through your identity provider for the whole company is the setting tools keep for the plan with "real" SSO. That is the gap between SSO as a convenience and SSO as a control, and it is the gap vendors charge for.

Is SSO more secure than passwords?

Usually, yes, for three plain reasons. People protect one strong password and one set of MFA factors instead of dozens of reused ones. Login rules are set in one place, so there is no tool quietly running without MFA. And disabling one account blocks new logins everywhere it is connected.

The trade-off is concentration. A phished identity provider account opens every connected tool at once, so that account needs the strongest MFA you can get, ideally a passkey or security key. Without MFA on the identity provider, SSO makes a stolen password worth more, not less.

What SSO does not do

This is the part sales pages skip, and it is the part that matters most to a small company.

It does not remove anyone from a tool. Disabling someone in the identity provider stops new logins. Their Slack account still exists, still holds a paid seat, and still shows up in channel member lists. Removing the account is a separate feature called provisioning, usually through SCIM (what SCIM is), often on an even more expensive plan. Creating accounts for new people is the other half, user provisioning.

It does not end sessions that are already open. Many tools keep a signed-in browser or mobile app working until its own session expires, which can be days or weeks. The identity provider is not asked again until then.

It does not cover tools that do not support it, or that you have not paid to connect. Those keep their own passwords, and they are usually the tools nobody remembers at offboarding.

It does not tell you what you pay for. SSO knows who logged in. It does not know how many seats you bought, or which tools nobody has opened in months.

If the reason you are reading about SSO is that someone left and you were not sure they were out of everything, SSO alone will not fix that. Our employee offboarding checklist covers what actually has to happen.

What SSO costs

There are two bills.

The identity provider. It is free or already paid for if you use Google Workspace or Microsoft 365 and they cover the tools you need. Dedicated identity providers charge per user: Okta's Starter suite is $6 per user a month, billed annually, with a $1,500 yearly minimum.

The tool upgrades. Most tools only accept SSO on their Business or Enterprise plans, so connecting them means upgrading every seat, not just the admin's. This is called the SSO tax, and for a small company it is usually far bigger than the identity provider.

For a 20-person team on five common tools, the upgrades alone come to about $18,700 a year. The SSO tax calculator works out your number from each vendor's published prices. Notice what that money buys: the login enforcement described above, not the account removals most small companies were hoping for.

Who needs SSO

You need real single sign-on in three situations.

A customer, auditor or insurer requires it. Some enterprise contracts say your staff must log in to systems holding their data through an identity provider. A process document will not satisfy that clause. Buy SSO for the tools in scope and keep the evidence.

You are big enough that central login rules pay for themselves. Somewhere past 50 people, with many tools and frequent hiring, enforcing MFA and device rules in one place is worth the price, and someone's job can include owning the identity provider.

Your tools include it already. If most of your important tools offer SSO on the plan you already pay for, connecting them costs little. Do it.

The size question is worth being concrete about. A 5-person company has one admin, a dozen tools and maybe one leaver a year. Turning on MFA in Google Workspace and using "Sign in with Google" wherever it is offered gets them most of the benefit for nothing. A 50-person company hires and loses someone most months, runs forty or more tools, and has contractors coming and going. The login side starts to matter, but so does the account side, which SSO does not touch.

You probably do not need SSO when what you actually want is one place to add new people to every tool and remove leavers from every tool. That is access management, and SSO only does half of it, at a price set for much bigger companies. SSO for small business has the longer version of that decision.

Where SmashSSO fits

SmashSSO is not single sign-on. Your people keep logging in to each tool the way they do now, and nothing sits in front of their logins.

What it does is the access part: it reads your people from Google Workspace with read-only access, shows who already has an account in each tool and with what role, and then invites, changes and removes people for you. Tools where you have added a member API token are handled through the API; the rest are handled by an agent working in your own Chrome, in tabs where you are already signed in as an admin. That means your browser has to be open for those changes to run, agent runs can fail when a tool changes its screens, and a tool's terms may restrict automated use, which the FAQ covers plainly.

It costs a flat fee for the company, from $199 a month billed annually, with no tool upgrades (pricing). If an auditor needs enforced login through an identity provider, buy SSO for the tools in scope; SmashSSO does not replace that.

More on how SSO works

If you want the mechanics, start with how SSO works, one login step by step, then read about the protocols behind it. What SAML is explains the standard most workplace tools use, and SAML vs SSO untangles two words that get used as if they meant the same thing. What OIDC is covers the newer login standard behind "Sign in with Google", SAML vs OIDC compares the two, and SAML vs OAuth separates logging in from granting an app access to your data. Types of SSO puts all of them, plus the things that only call themselves SSO, on one page, and federated SSO and federated identity explains the older word for the same trust arrangement.

If your real problem is accounts rather than logins, read the provisioning posts next, because that is where SSO stops. What SCIM is explains the standard that creates and removes accounts, SCIM vs SAML shows why login and provisioning are sold separately, and how SCIM provisioning works and what it costs gets into setup and pricing. Just-in-time provisioning covers accounts created on first login, which handles joiners and never removes anyone.

To decide whether SSO is worth it, compare it with what you already have. What an identity provider is shows whether you own one already, SSO vs MFA and SSO vs a password manager cover the two tools most often confused with it, and SSO vs LDAP covers the old directory protocols it replaced. The benefits of SSO, and the risks nobody puts on the slide weighs it honestly, and what "enterprise SSO" means explains why the feature lives on the expensive plan. When you are ready to act, how to implement SSO in a small company is the practical order of work, and identity and access management for small businesses puts login, accounts and reviews in one picture.

FAQ

What does SSO stand for?
Single sign-on. A person logs in once, to one account run by an identity provider such as Google Workspace, Microsoft Entra ID or Okta, and every connected work tool accepts that login instead of asking for its own password.
Is "Sign in with Google" SSO?
In practice, yes: one Google account logs people in to the tool, using the OpenID Connect standard. What it usually lacks is enforcement. The tool still allows its own passwords, and requiring Google login for your whole domain is normally kept for the tool's SSO plan.
Is SSO more secure than passwords?
Usually, because people protect one strong password and MFA instead of dozens of reused ones, and login rules are set in one place. The trade-off is that the identity provider account becomes the key to everything, so it needs your strongest MFA.
Does SSO remove people from tools when they leave?
No. Disabling someone in the identity provider stops new logins, but their account stays in each tool, often holding a paid seat, and open sessions may keep working. Removing accounts needs provisioning, usually SCIM, or someone doing it by hand.

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