Blog / How the internet works /

Single sign-on for small teams

A new person joins your team on Monday. By Wednesday, they’ve asked for access to the email system, the project tool, the design app, the website admin, the analytics, the invoicing software and the shared drive. Seven logins, seven invitations, seven things to remember to switch off when they leave.

Multiply that by a few hires and a few departures, and you can see why access management becomes the quiet mess in most small businesses. Single sign-on, or SSO, exists to fix exactly that.

But SSO has a reputation as an enterprise thing, with big price tags and acronyms. Is it for a team of five? Sometimes yes, sometimes not yet. Let’s sort out what it is and when it earns its place.

What single sign-on means

With SSO, you log in once, to one trusted identity provider, and that login lets you into other apps. The apps don’t each store their own password for you. They trust the identity provider’s word that you are who you say you are.

You’ve already used a consumer version. “Sign in with Google” or “Sign in with Apple” on a third-party site is the same idea. I explained the mechanics in how login with Google works.

For teams, the identity provider is usually the company’s own account system: Google Workspace, Microsoft 365, or a dedicated service such as Okta or similar. Staff sign into that, and each connected app lets them straight in.

Why it helps a team

1. Fewer passwords

If people have one strong login, protected by two-factor, instead of twenty weak or reused ones, the biggest everyday risk, password reuse, shrinks a lot.

2. One place to switch people off

This is the big one. When someone leaves, you disable their account in one place and they lose access to everything connected. Without SSO, you have to remember every tool, and almost everyone forgets one. That forgotten login is how ex-employees keep access for months.

3. One place to enforce two-factor

Rather than relying on each app’s own settings, you can require strong authentication at the identity provider. Two-factor authentication: SMS, apps and passkeys compared covers the options.

4. Easier onboarding

Add a person to the right group, and they get the right apps. It’s faster, and it makes it easier to give people only what they need.

5. A clearer picture of what you use

Connecting apps to SSO forces you to list them. That inventory alone is valuable. Many teams discover subscriptions and accounts nobody remembered.

The catches

It’s worth being honest about the downsides.

  • Single point of failure. If the identity provider has problems, or someone takes over that account, the consequences spread widely. Protect the admin accounts fiercely.
  • Not every app supports it. Many tools only offer SSO on their higher-priced plans, which is sometimes called the “SSO tax”. For small teams, this is the main reason SSO feels expensive.
  • Setup takes time. Each app needs configuring, and it’s easy to get partly done and call it finished.
  • It doesn’t fix bad habits. A weak login on the identity provider is a weak front door to everything.

Does a small team need it?

A rough guide:

Team situation What I’d do
1 to 3 people, few tools A good password manager plus two-factor everywhere is probably enough
4 to 15 people, a dozen tools, some turnover Use the sign-in option you already pay for (Google or Microsoft) wherever apps support it
More than that, or regulated data A proper identity provider with groups, policies and logs

For most small teams, the sensible middle path is this: you probably already have Google Workspace or Microsoft 365 for email. Use that account as your login wherever a tool offers “Sign in with Google” or “Sign in with Microsoft” for business accounts. You get a decent share of the benefit at no extra cost.

A practical way to start

  1. List your apps. Write down every tool your team logs into, who uses it, and who the account owner is. This echoes the thinking in website accounts to hand over when a developer leaves.
  2. Choose your identity provider, ideally the one that already holds everyone’s work email.
  3. Turn on two-factor for every account there, and make it mandatory. Prefer an authenticator app or a passkey to SMS. Passkeys explained: the end of passwords? covers the newer approach.
  4. Protect the admin accounts with the strongest method you have, and keep at least two admins, so one person’s absence doesn’t lock you out.
  5. Connect apps in priority order: first those holding money or customer data, then the website and hosting, then the rest.
  6. For apps that can’t connect, keep their logins in a shared password vault with named access, as in password managers and shared logins for client websites.
  7. Write an offboarding checklist. Disable the identity account, remove vault access, check the non-SSO apps, and transfer ownership of files and subscriptions.

What about the website itself?

Your WordPress or Shopify admin may support SSO, either natively or through a plugin or app. It’s worth checking, but be careful: adding a login plugin is adding code to your admin area, so choose well-maintained ones and test with a spare admin account so you can’t lock yourself out. For small sites, strong passwords, two-factor and a limited number of admin users usually give most of the safety benefit. I wrote about this in two-factor login for website admins.

Common mistakes

  • Using shared logins like team@company.com for convenience. They break accountability and make offboarding messy.
  • Only one admin, so nobody can recover if they’re ill or leave.
  • Treating SSO as a replacement for two-factor. It’s the doorway, so lock it.
  • Forgetting contractors and agencies. Give them accounts that expire, and review them regularly.
  • Letting personal accounts own business tools. If a tool was signed up for with someone’s personal email, SSO won’t help you when they leave.

Key takeaways

  • SSO means one trusted login opens many apps.
  • The big wins are fewer passwords and easy, complete offboarding.
  • Small teams can start with Google or Microsoft sign-in rather than a dedicated platform.
  • Protect the identity account hard; it’s now the master key.
  • Keep a shared vault and a leaving checklist for tools SSO can’t reach.

Choose one person who left or changed role in the last year and check whether they still have access to anything. If you find something, you’ve just seen why this matters.