Rolling Out AI Company-Wide with Single Sign-On - Part 2

Single sign-on makes the company's identity provider the way people sign in to Multi-Router, so the company's sign-in controls apply to every session in the dashboard and the Portal.

Rahul Singh, Founder, Multi-Router 8 min read

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:

  1. The person enters their work email on the Multi-Router sign-in page.
  2. Multi-Router recognizes the email domain and shows Continue with SSO, with the name of the identity provider, such as Your team uses Okta.
  3. The person signs in at the identity provider, which sends them back to Multi-Router.
  4. 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.
multi-router.ai
One API · every model

Route every LLM
through one endpoint.

Fallbacks, weighted splits, per-model keys and live traffic — behind a single router you control.

Trusted for production LLM traffic
Back

Single sign-on

dana@example.comEdit
Your team uses Okta
You'll finish signing in with your company provider.
Continue with SSO

Account owner? Sign in with password

The Multi-Router sign-in page after dana@example.com entered their work email: the Single sign-on step names Okta as the company's identity provider and offers Continue with SSO.

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 providerThe provider, shown to people on the sign-in step.
Email domainThe domain whose people sign in through SSO. A domain belongs to one Multi-Router account.
Also allow subdomain emailsIncludes subdomains such as eng.example.com, for companies that control every subdomain.
Issuer / Discovery URLThe identity provider's issuer. Multi-Router reads the provider's endpoints and signing keys from it.
Client IDThe client ID of the Multi-Router app in the identity provider.
Client secretThe client secret of that app, stored encrypted.
New-user accessAuto-provision or Invite-only.
Default role for new usersMember or Admin, the account role for people added by Auto-provision.
Provision users intoThe organization people are added to and land in when they sign in.
Require SSO for everyoneTurns off password and social sign-in for the domain.
example-co · acc_7Tq2Wd9KxP

Account Settings

Single Sign-On (SSO)

Let your team sign in through your company identity provider. One connection per organization.

Okta
example.com · OpenID Connect
Active
Identity provider
Oktavia OpenID Connect
Okta also supports SAML 2.0 (coming soon). Protocol is inferred from your provider.
Email domain
Users with this email domain will sign in via SSO.
✓ Domain ownership verified
Okta connection details
Issuer / Discovery URL
We auto-discover endpoints + signing keys. Redirect URI: /sso/callback.
Client ID
Client secret
✓ Configured
New-user access
Auto-provisionInvite-only
Anyone your IdP authenticates from example.com is created and added to your organization automatically.
Default role for new users
MemberAdmin
Members use routers, prompts, keys and traffic — they can’t manage members, billing, or SSO.
Provision users into
SSO users are added to this organization and land here when they sign in.
Require SSO for everyone
Disables password & social login for example.com. A break-glass admin login always stays available.
✓ Connection looks good
  • ✓Discovery document: issuer verified; authorization + token endpoints found
  • ✓Signing keys (JWKS): 2 signing key(s) available
Checks the issuer's discovery document + signing keys. Client ID/secret and the redirect URI are verified during an actual sign-in.
Test connectionEdit
A saved Okta connection for example.com: the verified domain, the connection details, new-user access and a passing connection test.

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
OktaAn 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 IDAn app registration with a web redirect URI and the optional email claim.https://login.microsoftonline.com/<tenant-id>/v2.0The users and groups assigned to the enterprise application, with Assignment required set to Yes.
Google WorkspaceAn OAuth client in a Google Cloud project, with an internal consent screen.https://accounts.google.comEvery account in the Workspace organization, narrowed with Invite-only.
Ping IdentityAn 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.
JumpCloudA custom application with OIDC sign-on.https://oauth.id.jumpcloud.com/The user groups bound to the application.
Other OpenID Connect providersA 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 organizationThe 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-provisionThey are added to the organization.
A pending invitationThe invitation is accepted with its role and organizations.
No person exists, with Auto-provisionA person is created with the default role.
No person exists, with Invite-onlyThe sign-in is refused, with a message to ask an admin for an invitation.
The person is suspended or offboardedThe 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.

M

Marco Ruiz

activemember

marco@example.com

OperatorManaged agentsPortal

Account roster Suspend Offboard
Access
Operator + agents
Organizations
1 of 2
Agents active
1 of 1
Spend this period
$41.75 / $200
Lifecycle
active
Sign-in
SSO linked

Access

Edit
Operator access
On · role member
OrganizationsEngineering· member
Managed agents
On·Portal
Engineering· Standard Engineering

AI agents

Claude CodeactiveEngineering · key …7Qx2 · issued Nov 2, 2026
Set up 12 days ago · router rt_9Hk3Ws7PzQ
$41.75 of $200 this month · $158 left
Rotate keySetup helpTrafficRetire

Policies

Engineering
Standard Engineering
Revision 3 · Claude Code
$200 per agent per month

Activity

Lifecycle events, newest page first.

activeNov 2, 2026
Actor: usr_4Rb8Nq2KtV

Identity

Email
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

Claude CodeMonthly · resets Dec 1
$41.75 of $200$158 left
The person page for an engineer who signed in through SSO: Sign-in shows SSO linked, with their access in Engineering, Claude Code on the Standard Engineering policy and its 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.

Start for free

Create a router, set your SDK base URL to Multi-Router and see the cost of every request.