enterprise plan

Single Sign-On (SSO)

Configure SAML 2.0 or OpenID Connect, with an Entra ID preset and group-to-role mapping.
Updated

What It Does

Single Sign-On settings configure a connection to the identity provider you already run, so that access can follow your directory rather than a separate list of people once the connection is set up. An administrator turns SSO on for the organization, adds an OIDC or SAML connection (the Entra ID preset fills in the usual OIDC values) and registers the callback address with the identity provider. Each connection decides what a new user gets: a default role, Reader unless you choose otherwise, and the email domains that may use it. Group mappings translate the groups in your directory into a platform role, or into a role on specific projects through groups the platform keeps in step with the claim. In additive mode a mapping only grants access; in authoritative mode, access that came from a group is removed when the group no longer appears in the claim. Password sign-in stays available alongside SSO. There is no SCIM provisioning or automatic deprovisioning, so deactivate a leaver's account in the platform as well as in your directory.

Single sign-on configuration: an SSO connection to the company identity provider over SAML 2.0, OpenID Connect or the Microsoft Entra ID preset (Okta and other OIDC providers can be configured too); the qa-team group is mapped to the Contributor role and new users are provisioned with that role in Shift-Left API

Overview

SSO configuration (OpenID Connect, SAML 2.0 and a Microsoft Entra ID preset) with group-to-role mapping is available to Enterprise administrators, and in the 15-day Trial. An administrator adds one or more connections to your identity provider and decides, per connection, the default role a new user receives, the email domains allowed to use it, and how identity-provider groups map to a platform role or to access on specific projects. OIDC tokens are checked against the provider's published keys with a pinned algorithm list, audience, issuer and nonce, and the provider must have verified the user's email. Client secrets and SP private keys are encrypted at rest and never shown again after you save them. Ask us to walk through the sign-in flow on your own installation before you roll SSO out to your team.

Key Capabilities

OpenID Connect and SAML 2.0 connections, with a Microsoft Entra ID preset
Any standards-compliant OIDC provider; group mapping needs a groups claim (Google Workspace does not send one)
Per connection: default role for new users and allowed email domains
Map identity-provider groups to a platform role or to a role on specific projects
Additive or authoritative mapping; authoritative removes group access when the claim disappears
Client secrets and SP keys encrypted at rest; connection changes are audited

How It Works

  1. 1

    An administrator opens Settings → Access & Identity → Single Sign-On and turns SSO on

  2. 2

    Add an OIDC or SAML connection, or start from the Entra ID preset

  3. 3

    Set the default role, allowed email domains and mapping mode

  4. 4

    Map identity-provider groups to a platform role or to project access

  5. 5

    Register the connection’s callback address with your identity provider

Available on

enterprise Plan & Above

Upgrade to the enterprise plan to unlock this feature.

Available on Enterprise plan, and in the 15-day Trial
See pricing →

Built for regulated teams

Teams in regulated industries rely on this capability to ship API changes with an audit trail.

Try SSO Today

Start your 15-day free trial — no credit card required.