Netlify's SSO Login No Longer Needs a Team ID

Netlify removed a login step that’s dogged every SSO-enabled team since it added SAML support: typing a Team ID before authenticating. As of Aug 12, 2026, entering an email address alone is enough. Netlify recognizes the domain and redirects straight to the configured identity provider (Netlify Changelog, Aug 2026).

What changed

The old flow put the burden on the person logging in: know your Team ID, enter it before Netlify would even ask which identity provider to redirect to. Miss it or forget it, and you were stuck at the login screen with no way forward (Netlify Changelog).

The new flow flips the order. Enter an email address, Netlify matches the domain to a team’s SSO configuration, and it redirects to whichever identity provider that team has set up — Okta, Entra ID, or any other SAML provider — for authentication. Land back in Netlify already signed in. Existing SAML setups don’t need reconfiguring; the domain-to-team mapping Netlify already stores was enough to make the switch (Netlify Docs, Log in to Netlify using organization SSO).

Why the Team ID was a problem

A Team ID isn’t something people memorize. It’s a string buried in team settings, and the people who most need to log in with it — new hires on their first day — are the people least likely to have gone looking for it. Every onboarding meant either a Slack message to a teammate or a support ticket to Netlify, just to get past the login screen.

That friction fell hardest on the accounts Netlify most wants to keep: SSO is an enterprise feature, gating it behind an internal lookup step undercuts the pitch that centralized identity makes access easier to manage, not harder.

Our take

This is a small fix, and Netlify is right not to oversell it. It shipped as a routine changelog entry, not a launch post. But it’s the kind of fix that only surfaces once a product has enough SSO customers generating enough “what’s my Team ID” tickets to notice the pattern. Domain-based IdP routing isn’t new; Okta, Google Workspace and most SAML providers have worked this way for years. The news is Netlify catching up to a UX baseline its enterprise customers already expected. The open question is whether Netlify extends the same domain-matching logic to other flows still gated behind a Team ID today, like CLI login or API token scoping.