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, for both your internal team and your partner portal.

​

What it does

Single sign-on lets people log in to Introw through your identity provider using SAML. 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.

​

The problem it solves

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

• Access lives outside your identity provider → SAML makes your IdP the source of truth for sign-in.
• Offboarding a user means hunting down every tool → Revoke in your IdP and access to Introw ends.
• Partners juggle yet another password → Portal SSO lets partners use their own identity provider.
• Security review stalls the rollout → Standard SAML configuration meets existing policy.

​

From problem to solution

Configure SAML 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.

​

Use cases

​

Impact

• Trust and accuracy - Access follows your identity provider and security policy.
• Low total cost of ownership - Admins configure SSO directly, no engineering required.

​

Who it’s for

​

Works with

​

Going deeper