Connecting access to the identity provider
In Part 1 I talked about a tools policy, which gives each person their own key, approved models and budget, and the Portal, where each person sets up the tools their policy grants. An admin assigns a policy through an invitation, from the account roster or from the policy page.
In this post I want to cover single sign-on, the first of two steps that connect that access to the company's identity provider, such as Okta or Microsoft Entra ID. Companies hire, move people between teams and have people leave, and the identity provider already records each of those events. Single sign-on makes the identity provider the way people sign in to Multi-Router, so the company's sign-in controls apply to every session and a person removed there can no longer sign in. Part 3 covers the second step, directory sync, which sends people and groups from the identity provider and turns each group into an organization, a role and a tools policy.
How single sign-on works
Single sign-on (SSO) lets people sign in to Multi-Router with their company account in place of a separate Multi-Router password. Multi-Router connects to the identity provider over OpenID Connect. The identity provider decides who can sign in, so the company's own controls, such as multi-factor authentication and app assignments, apply to every Multi-Router session. SSO covers both the dashboard and the Portal.
The account has one SSO connection, tied to one email domain, such as example.com. A sign-in follows four steps:
- The person enters their work email on the Multi-Router sign-in page.
- Multi-Router recognizes the email domain and shows Continue with SSO, with the name of the identity provider, such as Your team uses Okta.
- The person signs in at the identity provider, which sends them back to Multi-Router.
- Multi-Router checks the identity provider's response and opens the dashboard in the organization the connection provisions into, or the Portal when the person started there.
Route every LLM
through one endpoint.
Fallbacks, weighted splits, per-model keys and live traffic — behind a single router you control.
Single sign-on
Account owner? Sign in with password
Setting up a connection
An admin sets up the connection on the Single Sign-On (SSO) page, under Authentication (SSO) in Account Settings.
Setting it up takes an OpenID Connect web app in the identity provider, with the redirect URI
https://dashboard.multi-router.ai/sso/callback and an ID token that includes the email
claim, and access to DNS for the email domain. The connection has these fields:
| Field | Description |
|---|---|
| Identity provider | The provider, shown to people on the sign-in step. |
| Email domain | The domain whose people sign in through SSO. A domain belongs to one Multi-Router account. |
| Also allow subdomain emails | Includes subdomains such as eng.example.com, for companies that control every subdomain. |
| Issuer / Discovery URL | The identity provider's issuer. Multi-Router reads the provider's endpoints and signing keys from it. |
| Client ID | The client ID of the Multi-Router app in the identity provider. |
| Client secret | The client secret of that app, stored encrypted. |
| New-user access | Auto-provision or Invite-only. |
| Default role for new users | Member or Admin, the account role for people added by Auto-provision. |
| Provision users into | The organization people are added to and land in when they sign in. |
| Require SSO for everyone | Turns off password and social sign-in for the domain. |
Account Settings
Single Sign-On (SSO)
Let your team sign in through your company identity provider. One connection per organization.
/sso/callback.- ✓Discovery document: issuer verified; authorization + token endpoints found
- ✓Signing keys (JWKS): 2 signing key(s) available
Domain verification and testing
Domain verification proves that the company owns the email domain, so only the domain's owner can route its people
through an identity provider. After the first save, the page shows a TXT record named
_multi-router-verify.example.com to add at the domain's DNS host, and Verify domain checks for it. SSO
sign-in starts once the domain is verified and the connection is on, and until then people sign in as before.
Changing the email domain creates a new record, and SSO sign-in pauses until the new domain is verified.
Test connection checks the issuer before or after saving. It fetches the provider's discovery document and its signing keys, and shows Connection looks good when both pass. The client ID, client secret and redirect URI are checked during a real sign-in, so the last step of setup is a sign-in from a private browser window. The troubleshooting page in the docs lists each setup and sign-in error with its cause and fix.
Identity providers
Multi-Router works with any identity provider that supports OpenID Connect sign-in with the authorization code flow. The docs have a setup page for each of these, covering the app to create, the issuer to enter and the control that decides who can sign in:
| Identity provider | App in the identity provider | Issuer | Who can sign in |
|---|---|---|---|
| Okta | An OIDC web app with the authorization code grant. | https://example.okta.com/oauth2/default, or https://example.okta.com for the org authorization server. | The people and groups assigned to the app. |
| Microsoft Entra ID | An app registration with a web redirect URI and the optional email claim. | https://login.microsoftonline.com/<tenant-id>/v2.0 | The users and groups assigned to the enterprise application, with Assignment required set to Yes. |
| Google Workspace | An OAuth client in a Google Cloud project, with an internal consent screen. | https://accounts.google.com | Every account in the Workspace organization, narrowed with Invite-only. |
| Ping Identity | An OIDC web app in PingOne, with Client Secret Post authentication. | https://auth.pingone.com/<environment-id>/as, with the regional domain outside North America. | PingOne's application access settings, such as required groups. |
| JumpCloud | A custom application with OIDC sign-on. | https://oauth.id.jumpcloud.com/ | The user groups bound to the application. |
| Other OpenID Connect providers | A web application with a client secret, such as in Keycloak, Auth0 or Authentik. | The issuer value in the provider's discovery document. | The provider's own app access controls. |
The issuer entered in Multi-Router must match the issuer value in the provider's discovery document
exactly, including any trailing slash. Entra ID client secrets expire, after 6 months by default and at most 24, so
the admin adds a new secret in Entra and enters it in Multi-Router before the old one expires.
New people and the first sign-in
The connection's new-user access setting decides what happens when someone signs in through SSO for the first time. With Auto-provision, anyone the identity provider signs in from the domain is added to Multi-Router in the organization under Provision users into, with the default role. With Invite-only, only people already invited can sign in, and their invitation is accepted on their first sign-in. Auto-provision with the Member role suits most companies, with the identity provider's app assignments deciding who can sign in. The Admin default role makes every new person an admin of the whole account, every organization and its SSO settings included.
On the first sign-in, Multi-Router matches the person to the account by email:
| Situation | Result |
|---|---|
| A person with the same email already has access in the connection's organization | The SSO identity is linked to them, and they keep their name, history and access. |
| A person with the same email has no access there, with Auto-provision | They are added to the organization. |
| A pending invitation | The invitation is accepted with its role and organizations. |
| No person exists, with Auto-provision | A person is created with the default role. |
| No person exists, with Invite-only | The sign-in is refused, with a message to ask an admin for an invitation. |
| The person is suspended or offboarded | The sign-in is refused. |
Once a person has signed in, their page in the dashboard shows Sign-in: SSO linked. A person who starts the sign-in from the Portal returns to the Portal, and one who starts from the dashboard returns to the dashboard.
Marco Ruiz
activemembermarco@example.com
OperatorManaged agentsPortal
Access
EditAI agents
Policies
Activity
Lifecycle events, newest page first.
Identity
- marco@example.com
- Account role
- member
- Sign-in
- SSO linked
- Person ID
- per_6Jd3Xv9PmL
- User ID
- usr_4Rb8Nq2KtV
- Created
- Nov 2, 2026
- Updated
- Nov 2, 2026
Budget
Requiring SSO
Require SSO for everyone makes the identity provider the only way people of the email domain sign in. It turns off password sign-in and social sign-in, such as Google or GitHub, for every email in the domain, so the company's sign-in policies apply to every session. A password sign-in attempt for the domain then returns Your organization requires single sign-on. Invited people of the domain accept their invitation by signing in through SSO.
The account owner keeps password sign-in while SSO is required, so the account stays reachable when the identity provider is unavailable or misconfigured. A company usually turns it on in four steps: it sets up the connection with Require SSO off and verifies the domain, signs in with a test person to check their organization and role, tells people that sign-in is moving to the identity provider, and then turns on Require SSO.
Sessions and sign-in links
A session started through SSO lasts 8 hours, after which the person signs in again, and the profile menu shows an SSO badge for it. Sessions that started before Require SSO was turned on continue until they expire. Removing a person's assignment in the identity provider stops their new sign-ins, so with Require SSO on, a person who leaves loses access to the dashboard and the Portal within 8 hours.
A sign-in can also start from https://dashboard.multi-router.ai/sso/start?domain=example.com, which goes
straight to the identity provider for the domain. It suits a bookmark, an intranet link or a Multi-Router tile in
Okta's app dashboard, set as the app's Initiate login URI.
Next: directory sync
Single sign-on decides who can sign in. It leaves each person's keys and routers working until an admin retires them, and each person's organization and tools policy are still assigned by hand. In Part 3 of this series I'll cover directory sync, which sends people and groups from the identity provider over SCIM, assigns organizations, roles and tools policies from directory groups, and suspends a person's tools the moment the identity provider deactivates them. The Single Sign-On docs cover each identity provider and setting in detail.