BetaTesting supports SAML-based Single Sign-On (SSO) for Enterprise customers, allowing your team members to log in to BetaTesting using your company's identity provider (IdP). This eliminates the need for separate BetaTesting passwords and gives your IT team centralized control over access.
What is SSO?
Single Sign-On lets your employees authenticate through your company's existing identity provider - such as Okta, Microsoft Entra ID (Azure AD), OneLogin, or any provider that supports the SAML 2.0 standard - and be automatically signed in to BetaTesting.
Key Benefits
Centralized access control - Manage who can access BetaTesting directly from your identity provider
No separate passwords - Team members use their existing corporate credentials
Automatic account creation - New users are provisioned in BetaTesting automatically on first login (or via SCIM - see below)
Role mapping - Map your IdP groups to BetaTesting roles (Admin, Support, Read-Only, Tester) so permissions stay in sync
Deprovisioning - When you remove a user from the BetaTesting app in your IdP, they lose access to BetaTesting immediately
SSO + SCIM
BetaTesting also supports SCIM 2.0 (System for Cross-domain Identity Management) provisioning alongside SSO. SCIM allows your identity provider to automatically:
Create user accounts in BetaTesting when assigned in your IdP
Update user profiles when changes are made in your IdP
Deactivate accounts when users are unassigned or deprovisioned
Sync group memberships for automatic role assignment
SSO can be configured with or without SCIM. Without SCIM, user accounts are created on first login (just-in-time provisioning). With SCIM, accounts are pre-provisioned before the user ever logs in, giving you tighter control.
Supported Identity Providers
BetaTesting works with any identity provider that supports SAML 2.0, including:
Okta
Microsoft Entra ID (Azure AD)
OneLogin
Google Workspace
Ping Identity
JumpCloud
Auth0
Any other SAML 2.0-compliant provider
We have dedicated setup guides for Okta and a general guide for all other SAML providers.
How Setup Works
Setting up SSO is a collaborative process between your IT team and the BetaTesting team. Here's the high-level flow:
Step | Who | What Happens |
1 | You | Create a SAML application in your identity provider |
2 | You | Share your IdP metadata (SSO URL, certificate, issuer) with your BetaTesting account manager |
3 | BetaTesting | Configures the enterprise connection and provides you with the Assertion Consumer Service URL and Entity ID |
4 | You | Update your SAML app with the values BetaTesting provides |
5 | BetaTesting | Enables the SSO connection and configures allowed email domains and default roles |
6 | Both | Test SSO login to verify everything works |
7 | (Optional) Both | Configure SCIM provisioning and role mappings |
Prerequisites
Before getting started, make sure you have:
An Enterprise plan on BetaTesting
Administrator access to your company's identity provider
The email domain(s) your team uses (e.g.,
yourcompany.com) -- these will be restricted to SSO login
Getting Started
Contact your BetaTesting account manager to begin the SSO setup process. They will guide you through each step and securely exchange the required configuration details.
For provider-specific instructions, see:
For automated user provisioning, see: