# Several identity providers for one company

19 October 2026. A company you sell to can now sign its people in through more than one identity provider, each email domain sent to its own, and a second connection in WorkOS no longer stops its single sign-on.

## Added

- **Authentication:** Several identity providers per company. Add a second connection to a company in your WorkOS dashboard, such as Microsoft Entra ID for a company it bought beside its own Okta, and each of its verified email domains is sent to its own: the one it had stays the default, your team in the console or the company's admins in your app (from @buildbase/sdk 1.0.0) send a domain to another, and where a domain has two, the sign-in page asks which. Each one is a connection on your own WorkOS bill.
- **Authentication:** Each identity provider on its own. Its state, its SAML certificate and its warnings are kept apart from the others', the console and the Single sign-on screen list each one with the domains it signs in, and a domain no active identity provider signs in is named. An identity provider's answer for an address on a domain it does not sign in is refused before anyone is looked up.
- **Webhooks:** A webhook event and workflow trigger, enterprise.sso_routing_updated, when which identity provider signs in each domain changes. The connection and certificate events now also say which identity provider, whether it is the default, the domains it signs in and the domains nobody can sign in at.

## Fixed

- **Authentication:** A company with a second connection in WorkOS could no longer sign in from your login page. Every sign-in now names its connection to WorkOS, never the company's organization.

Source: https://www.buildbase.app/changelog/several-identity-providers-per-company
