How to implement SSO in a small company: list every tool and the plan it needs for SSO, pick an identity provider (often the Google Workspace or Microsoft 365 you already have), connect the most important tools one at a time, test with a second admin before you enforce, and plan offboarding separately, because SSO will not remove anyone. For a team of 5 to 50, the technical work is days, not months. The budget is the hard part.
Below is the SSO implementation plan, in order, with the traps that cause lockouts and surprise invoices.
Step 1: decide if you need it
Before any setup, be clear why you are doing this. Three reasons are common.
A customer, auditor or insurer requires it for systems that hold their data. Then you need real SSO, at least for those systems, and the requirement itself tells you which ones.
You want central login rules: MFA (a second factor on top of the password) and password policy set once, for every tool. That is a good reason, but much of it is available for free by enforcing MFA in Google Workspace or Microsoft 365 and using "Sign in with Google" where tools offer it.
You want leavers out of everything on the day they go. SSO only blocks future logins; the accounts stay. If this is your main reason, read SSO for small business first, because a cheaper tool may do the job better.
Write the reason down. It decides which tools are in scope, and it stops a project for three tools turning into an upgrade of thirty.
Step 2: inventory your tools and their SSO plans
Make a spreadsheet with one row per tool and these columns:
| Column | Why it matters |
|---|---|
| Tool and current plan | Your starting point |
| Seats | Most SSO upgrades are priced per seat |
| Cheapest plan with SAML | Where SSO actually starts; check the vendor's pricing page |
| Price difference | Per seat or flat, per year |
| SCIM on which plan | Automatic account removal; often a higher plan still |
| Data sensitivity | Customer data, money, code: these go first |
| In scope? | Yes if a requirement names it or the risk justifies it |
Expect surprises. GitHub, for example, lists Team at $4 per user a month and keeps SAML SSO for Enterprise at $21, per GitHub's pricing page as we read it on 27 October 2026. Some tools have no public price for their SSO plan at all. The SSO tax calculator has many common tools filled in, with sources. Shadow IT is worth a look here too: the tools nobody told you about are still tools, and an inventory that misses them will miss them again at offboarding.
Step 3: pick the identity provider
The identity provider is the service that holds your people, checks their password and MFA, and vouches for them to each tool (what an identity provider is). The options sort themselves by what you probably already have.
Google Workspace can act as a SAML identity provider for custom apps and a catalog of preset ones. Its automated user provisioning covers up to 3 apps on Business Starter and up to 100 on Business Standard and above, according to Google's help page on automated provisioning, and requires Google to be set up as the SSO identity provider for each app first. Google Workspace SSO covers it in full.
Microsoft Entra ID is already there if you run on Microsoft 365. Entra ID Free comes with Microsoft cloud subscriptions such as Microsoft 365, per Microsoft's licensing docs; P1 is $7 per user a month, paid yearly, per Microsoft's Entra pricing page on 27 October 2026. Microsoft Entra ID pricing covers what P1 adds.
A dedicated identity provider is the third route. Okta's Starter suite is $6 per user a month with a $1,500 yearly minimum, and Essentials, which includes provisioning, is $17 (Okta pricing; our Okta pricing breakdown). JumpCloud lists an SSO package at $11 per user a month billed annually (JumpCloud pricing).
For most small companies the right answer is the one your email already runs on. Move to a dedicated provider when you need features it lacks, not because a vendor said "enterprise".
Step 4: connect tools one at a time
Start with the tool that matters most and has the simplest setup. For each tool, the work runs in the same order.
Upgrade to the plan with SSO, if needed, and confirm the feature is switched on. Then verify your email domain in the tool; most require it before SSO.
Add the tool in the identity provider, from a preset if one exists. Presets save you from hand-copying URLs and certificates. With Google Workspace, a tool without a preset goes in as a custom SAML app, under Apps, then Web and mobile apps, per Google's custom SAML app guide as we read it on 27 October 2026.
Exchange the details. SAML needs the identity provider's sign-in URL, entity ID and signing certificate on the tool side, and the tool's URLs on the identity provider side (what SAML is explains each). OpenID Connect needs a client ID, secret and issuer URL.
Map the email attribute. The identity provider's email must match the email on each person's existing account, or the tool may create duplicates.
Assign a pilot group: yourself and one other admin. In Google Workspace, that means switching the app on only for a group or organizational unit you control; Google's guide says the change can take up to 24 hours, though it is usually quicker.
Test from a private browser window, both from the tool's login page and from the identity provider's app list. Google's admin console has a "Test SAML login" button for the second.
Can you roll out SSO tool by tool? Yes, and you should. There is no benefit to switching everything at once, and every reason not to.
Step 5: enforce, then handle exceptions
Testing works with SSO optional. Enforcement is the step that locks people out if anything is wrong.
Keep a way back in. Before enforcing, find out how the tool lets an owner recover if SSO breaks. Some keep a bypass for owners; some need a support ticket. Cloudflare, for one, recommends creating an API token in advance that can switch dashboard SSO off (Cloudflare docs). Know the route before you need it.
Enforce for everyone else, then switch off password login if the tool allows. A tool that still accepts passwords is a tool where SSO is a suggestion.
Write down the certificate expiry date. SAML signing certificates expire, and when one does, nobody can log in to that tool until it is renewed. Google's guide to maintaining SAML certificates, read the same day, gives its certificates a five-year lifetime and recommends adding a second one before the first expires, then moving apps over one at a time. Five years is long enough for whoever set it up to have left. Put the date in a shared calendar.
List the exceptions: contractors outside your domain, service accounts, guests. Each tool handles them differently; decide per tool, and write it down. Contractor access management covers the most common one.
Tell people. A two-line message ("Slack now signs in through Google from Monday; use the SSO button") saves a morning of confused messages.
What if a tool does not support SSO, or not on a plan you will pay for? Use "Sign in with Google" if the tool offers it, require MFA in the tool's own settings, and keep the login in a password manager. Then make sure it is on your offboarding list, because SSO will never cover it.
Step 6: plan offboarding, because SSO alone will not do it
When someone leaves, suspending them in the identity provider stops their next login to every SSO-connected tool. It does not remove their account, which keeps holding a paid seat. It does not end sessions already open in a browser or phone. And it does not touch tools outside SSO.
Removing accounts automatically needs SCIM, the provisioning standard (what SCIM is), which tools usually keep on the SSO plan or a higher one, and which your identity provider must support too. Do you need SCIM as well? If leavers matter to you and the tool charges per seat, yes, or some other reliable way to remove people. SCIM provisioning covers how it works and what it costs, and the employee offboarding checklist covers the manual version.
Step 7: budget
Add up three lines for a year.
The identity provider is zero if you use Google Workspace or Microsoft 365 as is; otherwise it is per user, with any minimum.
The tool upgrades are the price difference for each in-scope tool, times seats, times 12. One example: moving 20 people from GitHub Team to Enterprise adds $4,080 a year at today's list prices. For five common tools at 20 seats, 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 | ||
Time is the third line. An afternoon per tool for setup and testing is a reasonable plan for someone comfortable in admin settings. Budget more for the first one, and for any tool that needs a support ticket.
How long does it take to implement SSO? It varies, but for a small company connecting five tools, think in weeks of part-time work rather than months, and expect most of that time to go on plan upgrades, sales calls and domain verification. The SSO tax post shows why the upgrade line is usually the biggest.
Common SSO implementation mistakes
Connecting everything because you can. Once the identity provider is set up, adding tools feels free. It is not, if each one needs a higher plan. Stick to the scope from step 1.
Enforcing before the second admin has tested. If the only person who tested is the one who configured it, nobody knows whether it works for anyone else.
Ignoring the accounts that already exist. People who signed up with a personal email, or with a typo, will not match. Clean up each tool's member list before you enforce, not after the complaints.
Treating SSO as the offboarding plan. It blocks logins. It does not remove accounts, free seats or transfer files.
What to do this week
If you are starting from nothing, the first week is short. Write down the reason, in one sentence, and the tools it names. Build the inventory spreadsheet with the plan and price for each of those tools. Turn on MFA for everyone in your directory if it is not already on, because SSO without it concentrates risk. And pick one tool to pilot, ideally one with a preset in your identity provider. Everything else can wait until that one works.
Where SmashSSO fits
SmashSSO is not SSO and is not a step in this rollout. It does not sit in the login path. Where it helps is step 6, and in the tools you decided not to put behind SSO.
It reads your people from Google Workspace, shows who has an account in each tool and with what role, and adds or removes people through access bundles by role. When someone is suspended in Google Workspace, it alerts you and shows where they still have access. 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 can fail when a tool changes its screens. Paid-seat additions pause for approval, and every change is in the audit log.
It is a flat fee from $199 a month billed annually (pricing). If your reason in step 1 is an audit or contract that names SAML, implement SSO for those systems; SmashSSO is not a replacement. The what is SSO guide is the starting point for the rest of this cluster.