Single Sign-On

Security teams want one place to grant and revoke access, and users want one less password. Single sign-on connects Introw to your identity provider with SAML or OIDC, for both your internal team and your partner portal.

​

The problem it solves

Standalone logins are a security and admin burden on both sides of the partnership:

​

Impact

A partner’s security team can veto your portal. Portal SSO turns that from an exception request into a standard integration, which is often what decides whether their people ever log in.

​

See it work

​

How it works

Single sign-on lets people log in to Introw through your identity provider using SAML or OIDC. Internal SSO covers your own team’s access to Introw, and portal SSO covers how partners sign in to the portal. In both cases, your identity provider becomes the source of truth for who can access what, and you map the identity attributes that identify each user. When you turn on SSO, sign-in follows your existing policies, so onboarding and offboarding a user happens in the same place you manage the rest of your stack, no separate password to provision or revoke. Configure SAML or OIDC once for your team and, where partners require it, for the portal. Sign-in then follows your identity provider for everyone, so access is centralized, auditable, and consistent with the rest of your security posture.

​

Going deeper

Works with