Blaze does not currently offer SCIM-based user provisioning. Stepwork automates Blaze provisioning with 98% accuracy — no API required.
No SCIM; OAuth-only authentication. Complexity Vector: Access and permissions are managed per workspace and publishing channel in the UI, so standard provisioning cannot keep seats and publishing rights aligned automatically.
Paying for additional seats or higher plans doesn’t fix lifecycle gaps when access is still managed manually. Stepwork automates the UI steps for workspace access and cleanup on your current tier…which is why teams use Stepwork to automate Blaze flows with 98% accuracy without needing an API.
No. Blaze does not currently offer SCIM-based user provisioning, leaving IT teams to manage user lifecycle changes manually.
Stepwork automates Blaze 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 Blaze 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 lifecycle automation.. Additional risks include manual seat provisioning and cleanup., workspace access drifts as teams change., publishing permissions require ui checks.. Stepwork eliminates these risks by automating the entire provisioning workflow.
See how Stepwork provisions users in Blaze 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.