# Routing options

Pass routing hints from trusted application context when you already know the enterprise tenant.

| Hint           | Current behavior                                                               |
| -------------- | ------------------------------------------------------------------------------ |
| `connection`   | Selects that connection in the environment; a supplied organization must agree |
| `organization` | Selects among that organization's connections                                  |
| `domain`       | Resolves an organization through its verified domain                           |
| `login_hint`   | Uses the work email's domain when no stronger hint supplies the organization   |
| No hint        | Displays the hosted work-email page                                            |

A connection hint takes precedence, then organization, then domain, then the login hint's domain. Hints route the request; they do not authorize a user in your application or bypass the verified-domain rule. Check the returned organization against the tenant that started the attempt. Do not accept a browser's hint as proof of tenant membership.

## Organizations with several identity providers

Within the organization, the broker considers active, tested connections. A unique exact `routing_domains` match is selected automatically. If several connections match, the broker displays a picker containing those matches. If none matches, it offers the active, tested connections; one candidate is selected automatically and several candidates produce a picker.

The picker preserves the validated client, exact redirect URI, caller's S256 PKCE challenge, state and organization. Selecting a connection checks its current eligibility again. The picker does not extend a ticket's lifetime. It supports at most 100 choices and refuses an oversized set rather than silently hiding connections. Explicit connection routing remains available when your application already knows which connection to use.

The hosted picker is a neutral page, not a custom branded login experience. A connection's display name is cosmetic; identity and tenant checks use its identifiers.

The Node SDK accepts `organization`, `connection`, `domain` and `loginHint` in `sso.getAuthorizationUrl(...)`. Its camel-case `loginHint` becomes the broker's `login_hint` query parameter.

See [IdP-initiated sign-in](/sso/idp-initiated/) for unsolicited SAML and its separate confirmation flow.
