Betterworks does not currently offer SCIM-based user provisioning. Stepwork automates Betterworks provisioning with 98% accuracy — no API required.
SCIM not supported (support.betterworks.com) Complexity Vector: Identity lifecycle actions require manual admin steps rather than standard SCIM endpoints
You’re not wrong—Betterworks supports SAML SSO, but it explicitly doesn’t support SCIM/JIT provisioning, so user lifecycle changes still require manual admin work. …which is why teams use Stepwork to automate Betterworks flows with 98% accuracy without needing an API.
Betterworks supports SAML sign-on. Stepwork authenticates through your existing identity provider — the same way your employees do.
No. Betterworks does not currently offer SCIM-based user provisioning, leaving IT teams to manage user lifecycle changes manually.
Stepwork automates Betterworks 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 Betterworks 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 without scim, admins can’t automate joiner/mover/leaver flows and must provision users manually.. Additional risks include manual onboarding;, offboarding delays;, access review overhead. Stepwork eliminates these risks by automating the entire provisioning workflow.
No. 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.
See how Stepwork provisions users in Betterworks with 98% accuracy — in a 15-minute demo.
Book a Demo