Sush does not currently offer SCIM-based user provisioning. Stepwork automates Sush provisioning with 98% accuracy — no API required.
No native SCIM support. Complexity Vector: Workspace-based user models lack lifecycle automation endpoints.
You are correct; Sush does not natively support SCIM. This means standard Sush integrations cannot provision users, forcing IT to rely on manual spreadsheets, which is why teams use Stepwork to automate Sush flows with 98% accuracy without needing an API.
No. Sush does not currently offer SCIM-based user provisioning, leaving IT teams to manage user lifecycle changes manually.
Stepwork automates Sush 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 Sush 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 no scim. Additional risks include manual invites, no enterprise sso, workspace access drift. 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, mirroring your organization's security posture.
See how Stepwork provisions users in Sush with 98% accuracy — in a 15-minute demo.
Book a Demo