Google Workspace SSO costs nothing on Google's side: Workspace can be the identity provider for your other tools, and Google doesn't charge extra for it. You add each tool as a SAML app in the Google Admin console, and your people sign in to it with their Google account.
What Google can't do is make your tools accept that login on the plan you have. Most tools keep SAML single sign-on for a pricier plan, and Google's automatic account creation in other tools is capped at 3 apps on Business Starter. Both limits are below, with what Google's own help pages say, as we read them on 27 October 2026.
Google as an identity provider
An identity provider (IdP) is the service that holds your people's accounts and vouches for them when they log in somewhere else. If your company already runs on Google Workspace, Google already holds those accounts. Making it the IdP for a tool means the tool stops asking for its own password and sends people to Google instead.
The standard that carries that message is SAML, short for Security Assertion Markup Language: the tool asks Google who this person is, Google answers with a signed message, and the tool lets them in. What is SAML? covers the mechanics.
Two things often get mixed up with this. The first is the "Sign in with Google" button. Many tools show it on every plan. It uses OpenID Connect, and the tool, not you, decides who may use it. People can usually still log in with a password instead, and you cannot switch the tool on or off for a team from Google. SAML vs OIDC explains why the two behave differently.
The second is Google as the service provider. Google also works the other way round: Workspace accepts SSO from a third-party IdP such as Okta or Microsoft Entra ID, over SAML or OIDC, if your company's logins live there. This post is about the first direction, Google logging people in to everything else.
A SAML app is different from the button. An admin sets it up, decides which people or teams get it, and the tool can be configured to require it. That is what people mean by Google Workspace SAML, and it is the only version that gives you control.
Adding a SAML app in the Admin console
Google's custom SAML app help page gives the steps. In short:
Sign in as a super administrator. Only super admins can add SAML apps. Then go to Apps, then Web and mobile apps, then Add app. Pick the tool from Google's catalog of pre-integrated apps if it is there, or choose Add custom SAML app.
Swap details with the tool. Copy Google's SSO URL, Entity ID and certificate into the tool's SSO settings, or download the metadata file that holds all three. Then paste the tool's details into Google: the ACS URL, which is where the tool receives the login message and must start with https://, and the tool's own Entity ID.
Set what Google sends. The Name ID defaults to the person's primary email, which is what most tools expect. People must sign in to the tool with the same email they use in Google, so check that existing accounts match before you switch. Map attributes and groups if the tool wants a name, a department or a group in the login message. By default Google signs only the assertion inside the response, not the whole response; some tools ask for both, and there is a checkbox for it.
Turn it on and test. Under User access, switch the app on for everyone or for chosen organizational units. Google warns that changes can take up to 24 hours, though they usually happen sooner. Then test both ways in: from Google, with Test SAML login in the Admin console, and from the tool, by opening its SSO URL, which should send you to Google's sign-in page and back.
The page lists a few hard limits: 75 groups per custom SAML app, and 10,000 attributes across all apps. A small company won't hit either.
Keeping it working: the certificate
There is one maintenance job that catches small companies out. Google's certificate help page says the X.509 certificates behind SAML apps have a five-year lifetime. If one expires before you rotate it, people "won't be able to use SSO to sign in to any SAML applications that use that certificate".
Rotation is two-sided. Google recommends adding a second certificate with a new five-year life before the old one runs out, then moving apps across, a few at a time if you like, since both stay valid. After you assign the new certificate in the Admin console, you also have to update each tool's SSO settings with it, or sign-in fails. Only super admins can see the expiry status and act on it, and a new certificate can take up to 24 hours to reach your apps. Put the expiry date in a calendar now; five years is long enough for the person who set it up to have left.
Which plans include it
Is Google SSO free? On Google's side, yes. Google's pricing page doesn't list SAML apps as a paid feature on any edition, and its help article on custom SAML apps doesn't restrict them to an edition. Even Cloud Identity Free, Google's free identity product, includes Google as the IdP for SAML apps, according to Google's editions comparison.
Where the editions differ is automated user provisioning, Google creating and removing accounts in the tool for you. Google's help page on it sets these limits:
| Edition | Apps with automated provisioning |
|---|---|
| Business Starter, Frontline Starter | Up to 3 |
| Business Standard, Business Plus, Frontline Standard, Frontline Plus, Enterprise | Up to 100 |
| Cloud Identity Free | None |
| Cloud Identity Premium | Included |
Three apps is not many. On Business Starter, pick the three tools where a forgotten leaver would hurt most.
Limits: provisioning and the tools' own SSO plans
Provisioning only reaches some tools. Google provisions into apps on its supported list: the help page gives guides for tools such as Slack, Asana, Atlassian Cloud, Figma, HubSpot, Notion, Zendesk, Dropbox and Amazon Web Services (AWS SSO walks through that one). You set up SSO for the app first, then turn on provisioning.
Does Google Workspace support SCIM? Google's page doesn't name the protocol it uses. On the receiving side, AWS's documentation says Google syncs users into IAM Identity Center with SCIM 2.0, the standard for this job. What is SCIM? explains it.
It isn't instant. Google says users are synced "every few hours", and only active, suspended and deleted users are included; archived users are not.
The tool has to accept SAML, and that is the expensive part. Google can only log people in to a tool that supports SSO, and most tools keep it on a higher plan. GitHub only offers SAML on Enterprise; Zoom only from Business; Slack from Business+, at $15 per user a month billed annually on Slack's own enterprise page. That upgrade is the SSO tax, and Google's free IdP does nothing about it. For a 20-person team, two of those tools, with prices we checked today against the calculator's:
| Tool | Plan without SSO | Cheapest plan with SSO | Extra a year, 20 people |
|---|---|---|---|
| GitHub | Team · $4 a seat | Enterprise · $21 a seat | $4,080 |
| Zoom | Pro · $14.16 a seat | Business · $18.33 a seat | $1,000.80 |
| Total SSO tax a year | $5,080.80 | ||
So "Google SSO is free" is true on Google's side and misleading as a whole. The login costs nothing; the tools' plans that accept it do. Slack SSO and GitHub Enterprise pricing work through two of the biggest of those upgrades.
When Google is enough
Google as your IdP is the cheapest real SSO there is, and for a lot of small companies it is all they need. It is enough when everyone already has a Google Workspace account, and the tools you want SSO for are in Google's catalog or accept a custom SAML app. It is enough when you are happy to manage access by organizational unit or group in Google. And it is enough when you need automated provisioning for 3 tools or fewer on Business Starter, or up to 100 on a higher edition.
You will want a dedicated identity provider such as Okta or Microsoft Entra ID when you need login rules that Google's Admin console doesn't offer, or provisioning into tools that aren't on Google's list. Those cost money per person: Okta pricing has the numbers. And it is worth being clear that moving to Okta doesn't remove the tool-side bill; every tool still has to be on its SSO plan.
What to do this week
If you have decided Google is your IdP, the order is simple. First, list your tools and mark which ones accept SAML on the plan you pay for today; those are your free wins. Set those up one at a time, test them with a colleague who isn't an admin, and only then switch the tool to require SSO.
Next, pick your provisioning apps if you are on Business Starter, and spend all three slots on tools that hold customer data or money. Finally, write down the certificate expiry date and who will rotate it. Everything else on your list is a pricing question, not a Google question.
Where SmashSSO fits
SmashSSO is not SSO and doesn't replace Google as your identity provider. It does the job most small companies actually want SSO for: adding and removing people across their tools, from one place, without the tools' Enterprise plans.
It reads your people from Google Workspace with read-only directory 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 invite a new hire to every tool they need. When someone is suspended in Google, it alerts you and shows where they still have access, which is the gap the 3-app provisioning limit leaves on Business Starter. Changes run through a tool's member API where you have added a token, otherwise through an agent in your own Chrome, in tabs where you are already signed in as an admin; that browser has to be open, and agent runs are slower than an API and can fail when a tool redesigns its screens. Any step that would add a paid seat waits for your approval.
If an auditor or a customer contract requires enforced SAML login, you need real SSO, and Google is a fine place to start. If what you need is that leavers lose access everywhere, SmashSSO costs a flat fee from $199 a month billed annually (pricing). How it works has the details.