SSO and SAML Setup: Centralizing Your Organization's Access

Last updated: September 2, 2026

asset_7HPmVGDWbscJpjE2o5VA6nCi_DALL-E 3, A clean, modern digital workspace banner, overhead perspective. On a minimalist light-colored desk, abstract glowing digital nodes representing various identity providers ar.png

Introduction

Scenario supports Single Sign-On (SSO) via SAML 2.0 for organizations that want to simplify access management. When enabled, team members log in to Scenario using their company credentials: no separate Scenario password required.

Note: SSO is exclusively available on the Enterprise plan. Please contact your account manager to enable this feature for your organization.

Supported Identity Providers

Scenario's SAML 2.0 integration is compatible with most enterprise identity providers:

  • Okta

  • Microsoft Azure Active Directory (Entra ID)

  • Google Workspace

  • OneLogin

  • Custom Providers: Any identity provider that supports SAML 2.0 is likely compatible. If yours is not listed, contact support for a custom configuration.

Before You Begin

To ensure a smooth setup, you will need Admin access to both Scenario and your identity provider (IdP). Have these ready:

  1. Admin credentials for your IdP.

  2. The default Project ID where users will land.

What to Expect After Activation

  • Redirection: New and existing members will be redirected to your IdP login page.

  • Data Preservation: Existing members' projects, models, and assets remain intact after switching to SSO.

Frequently Asked Questions

Can I still use password-based login?

Admins retain password-based login as a fallback for troubleshooting. Standard members are required to use SSO.

Is SCIM supported?

SCIM for automated provisioning is currently on the roadmap. For now, manage memberships via the Members tab in Organization Settings.