Overview
Enterprise teams can connect their identity provider (Okta, Azure AD, OneLogin, Ping Identity) for SAML 2.0 single sign-on (via WorkOS SSO) and SCIM 2.0 automated user provisioning. The team is the SSO / SCIM organization boundary — one IdP integration manages one team’s membership.SSO and SCIM are Enterprise-plan only. The server re-checks the plan on every request: if the team’s subscription is not an active Enterprise plan, SSO configuration and all
/scim/v2/* calls are rejected with 403 enterprise_plan_required. A lapsed subscription disables provisioning immediately.SAML 2.0 Single Sign-On
SAML assertion verification is handled by WorkOS SSO. The dashboard SSO & SCIM page (/settings) surfaces the values you paste into your IdP and stores your IdP descriptor:
You enter your IdP’s metadata URL or Entity ID along with your corporate email domains. The descriptor is stored in
sso_configs and reconciled into WorkOS SSO out-of-band.
SCIM 2.0 Provisioning
SCIM lets your IdP create, update, and deactivate team members automatically. Point your IdP’s SCIM connector at:Supported resources
Provisioning and the zero-knowledge boundary
Deprovisioning (DELETE or PATCH active=false) revokes the member’s key grant — removing their ability to decrypt — and marks the membership inactive. The grant revocation is the security-critical step and happens first.
Tamper-Evident Audit Ledger Integration
Every provisioning event feeds the append-only SHA-256 tamper-evident audit ledger (audit_entries): member.add on provision, member.update on role change, and member.remove on deprovision, plus sso.config_update, scim.token_issue, and scim.token_revoke for configuration changes.