GitBook does not currently offer SCIM-based user provisioning. Stepwork automates GitBook provisioning with 98% accuracy — no API required.
No SCIM; enterprise-only SSO Complexity Vector: Access is tied to org membership plus space-level permissions, so even with SSO the admin work becomes UI-driven permission hygiene across multiple spaces.
Avoid upgrading to Enterprise just to unlock SSO for docs access control. Stepwork automates the UI steps for space access cleanup and offboarding on your current tier…which is why teams use Stepwork to automate GitBook flows with 98% accuracy without needing an API.
GitBook supports SAML sign-on. Stepwork authenticates through your existing identity provider — the same way your employees do.
No. GitBook does not currently offer SCIM-based user provisioning, leaving IT teams to manage user lifecycle changes manually.
Stepwork automates GitBook provisioning through interface automation — the same way a human would, but with 98% accuracy and no API required. Record the flow once, and Stepwork runs it on demand or on a schedule.
Yes. Stepwork authenticates to GitBook through your existing identity provider (Okta, Microsoft Entra ID, 1Password, etc.) and completes MFA natively — including OTP, passkeys, and push notifications. No separate credentials or service accounts are needed.
The primary risk is sso is enterprise-only.. Additional risks include manual user invites persist., space access drifts., offboarding is ui-based.. Stepwork eliminates these risks by automating the entire provisioning workflow.
See how Stepwork provisions users in GitBook with 98% accuracy — in a 15-minute demo.
Book a DemoNo. Stepwork completes MFA exactly like a human user — supporting OTP, passkeys, push notifications, and other methods. It signs in through your existing identity provider via SAML, mirroring your organization's security posture.