Blockworks does not currently offer SCIM-based user provisioning. Stepwork automates Blockworks provisioning with 98% accuracy — no API required.
Blockworks lacks SCIM and enterprise SSO, preventing standard provisioning or automated offboarding. Complexity Vector: Access is managed through multiple browser-only admin surfaces tied to subscriptions and content permissions. Stepwork automates these human workflows without requiring internal APIs.
You are correct; Blockworks does not natively support SCIM. This means standard Blockworks integrations cannot provision users, forcing IT to rely on manual spreadsheets and delayed access cleanup, which is why teams use Stepwork to automate Blockworks flows with 98% accuracy without needing an API.
No. Blockworks does not currently offer SCIM-based user provisioning, leaving IT teams to manage user lifecycle changes manually.
Stepwork automates Blockworks 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 Blockworks 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 access control, no sso, no lifecycle automation. Stepwork eliminates these risks by automating the entire provisioning workflow.
See how Stepwork provisions users in Blockworks 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, mirroring your organization's security posture.