Federated SSO is single sign-on that crosses an organizational boundary: one organization checks who you are, and a separate organization's system accepts that check instead of asking for its own password. If your company logs in to Slack or Zoom through Google Workspace or Okta, that is federation: your identity provider vouches for you, and a tool run by another company trusts it.
So most workplace SSO today is federated SSO, whether or not anyone calls it that. Here is what the word means, how the trust works, what setting it up looks like, and why it matters less to a small business than the jargon suggests.
Federation in plain terms
Think of a passport. Your own country checks who you are and issues the document. Another country's border officer has never met you, but accepts the passport because their government trusts yours to have done the checking. Nobody at the border keeps a file on you in advance.
Federated identity works the same way, with three pieces. The identity provider (IdP) is the issuing country. It holds your account, checks your password and MFA, and issues a signed statement that you have signed in. Google Workspace, Microsoft Entra ID, Okta and JumpCloud are identity providers (what an identity provider is). The service provider (SP) is the border. It is the tool you want to use, run by someone else. It does not check your password; it checks that the statement is genuine and came from an identity provider it trusts. Federated identity is the arrangement as a whole: your identity lives in one place and is accepted in many, across organizations that have agreed to trust each other.
Federated SSO is the login experience that arrangement produces: one sign-in, accepted by systems you do not run. Federated identity management is the admin work around it: deciding which tools trust your identity provider, which people may use each one, and keeping the trust current.
Federated SSO vs SSO
The terms overlap, which is why they confuse people. The useful distinction is where the boundary sits.
| SSO inside one organization | Federated SSO | |
|---|---|---|
| Who runs the login | The same organization that runs the apps | One organization; the apps belong to others |
| Example | One Google login opening Gmail, Drive and Calendar | Your Google Workspace login opening Slack, run by Slack |
| How trust is set up | Built in: it is all one system | Configured per tool: metadata, certificates, an agreed protocol |
| Typical protocols | Whatever the vendor uses internally; Kerberos on an office network | SAML 2.0, OpenID Connect, older WS-Federation |
Every federated login is a kind of single sign-on. Not every single sign-on is federated. When a SaaS pricing page says "SSO", it means the federated kind: your identity provider, their tool. What SSO is covers the basics, and the types of SSO sorts the variants.
Is SAML federation? SAML is one of the protocols federation runs on, and the most common one in business software. SAML 2.0 was approved as an OASIS standard in March 2005, and federation was its point: letting a login in one security domain be accepted in another (what SAML is). OpenID Connect 1.0, finalized by the OpenID Foundation in 2014, does the same job on top of OAuth 2.0 and is the protocol behind most "Sign in with Google" buttons (SAML vs OIDC). Microsoft's older WS-Federation protocol is still met in Microsoft-heavy setups, often through Active Directory Federation Services (AD FS), its on-premises federation server.
Trust between identity providers and tools
The trust in federation is set up once per tool, by hand or from a preset, and then used on every login. For SAML it involves four things.
It starts with exchanging metadata. Each side publishes an XML file describing itself: a unique name (the entity ID), the addresses that send and receive login messages, and its certificates. Next comes sharing a signing certificate. The identity provider signs every login message with a private key; the tool holds the matching public certificate and rejects any message that does not verify. This is the heart of the trust. Then the two sides are agreeing on attributes: which field identifies the person (usually email), and what else gets sent, such as name, groups or role. Finally there is agreeing on the domain. The tool links the trust to your verified email domain, so only your identity provider can sign in people at your company.
OpenID Connect does the equivalent with a client ID, a client secret and a discovery URL, and is generally simpler to set up by hand.
Two practical consequences. Certificates expire, and when one does, that tool's logins stop until someone uploads a new one. And the trust covers login only: the identity provider says who someone is at the moment they sign in, and nothing more. It does not create their account ahead of time, and it does not remove the account when they leave.
What setting up federation looks like
With Google Workspace as the identity provider, the work is mostly copying values between two admin screens. Google's guide to setting up a custom SAML app, as we read it on 27 October 2026, has a super administrator add the app under Apps, then Web and mobile apps, then Add custom SAML app. Google then shows its side of the trust: an SSO URL, an entity ID and a certificate to download, which go into the tool's SSO settings. The tool supplies its side, an ACS URL (the address that receives the login message, which must start with https://) and its own entity ID, which go back into Google. You map attributes such as email and name, switch the app on for everyone or for chosen organizational units or groups, and test with Google's "Test SAML login" button. Google notes that the switch-on can take up to 24 hours, though it is usually quicker.
The certificate is the part to diary. Google's guide to maintaining SAML certificates, read the same day, gives them a five-year lifetime and says that if one expires before you rotate it, people cannot sign in to the apps that use it until it is replaced. Its advice is to add a second certificate before the first expires, move apps over one at a time, and update each tool's side as you go. Google Workspace as your identity provider covers the rest of that setup.
When a federated login fails
Most broken federated logins come down to a handful of causes, and knowing them saves a support ticket. The person is not assigned to the app. In Google Workspace the app is switched on per organizational unit or group, so someone outside them gets an error, not a login. The email does not match. The tool matches the login to an account by email, so a person whose account was created under an old address can end up locked out or with a duplicate. A value was pasted wrong. One wrong character in the ACS URL or entity ID breaks every login to that tool, which is why presets beat hand-copying. The certificate expired or was rotated on one side only. Both sides must hold the same current certificate. When a login fails for one person, check the assignment and the email; when it fails for everyone, check the URLs and the certificate.
Examples you may already use
The most common example is your company's SSO to SaaS tools: Google Workspace or Okta as identity provider, and Slack, GitHub or Figma as service providers.
Guest access between companies is the next. Microsoft Entra ID's business-to-business guest feature lets a partner's staff use their own organization's login to reach your resources, without a second account to manage. Microsoft's Entra licensing page, read on 27 October 2026, says Entra External ID's core features are free for the first 50,000 monthly active users, which covers any small company's partners many times over.
Social and consumer sign-in counts too. "Sign in with Google" or "Sign in with Apple" on a website is federation between Google or Apple and that site, using OpenID Connect.
And there are research and education federations. Universities join national federations, such as InCommon in the United States, so that a student's home login works in shared services and journal sites run by others.
What it means for a small business
Less than the term implies.
You already have a federation-capable identity provider if you use Google Workspace or Microsoft 365. Both can act as SAML identity providers for many tools; check what your edition includes, and Microsoft Entra ID pricing covers the Microsoft side.
The limit is not federation, it is the tool's plan. Most tools only accept a federated login from your identity provider on their Business or Enterprise plan. That price gap is the SSO tax.
You do not need a federation between companies unless partners or customers need to log in to your systems with their own accounts. That is rare below 50 people, and Entra ID's guest access covers the common Microsoft case.
Federation does not manage access. It decides whether a login is accepted. Who should have an account, with what role, and whether it is removed when they leave, is a separate job (user provisioning, deprovisioning).
Do small businesses need federation? If you want enforced SSO, you are using it; there is nothing extra to buy. If you do not need enforced SSO, you probably do not need to think about federation at all.
Where SmashSSO fits
SmashSSO is not SSO, federated or otherwise, and it creates no trust between your identity provider and your tools. People keep logging in the way they do now.
What it handles is the part federation leaves out: who has an account in each tool. It reads your people from Google Workspace, shows an access grid of every tool's accounts and roles, and flags accounts that match nobody in your directory. It invites, changes and removes people through each tool's member API where you have added a token, or through an agent in your own Chrome, in tabs where you are already signed in as an admin. The agent needs that browser open and can fail when a tool redesigns its screens; a failed run says so.
It costs a flat fee from $199 a month billed annually (pricing). If you need enforced, federated login for an audit or a customer contract, you need real SSO for those systems, and how to implement SSO is the place to start.