Fireblocks does not currently offer SCIM-based user provisioning. Stepwork automates Fireblocks provisioning with 98% accuracy — no API required.
No SCIM Support Complexity Vector: Crypto custody access is highly permissioned and key-specific. APIs enforce security but not lifecycle management, requiring UI automation to safely provision/deprovision users.
Automate the collection of access evidence from Fireblocks for audits: without SCIM, teams resort to manual export and logs, which is slow and error‑prone, which is why teams use Stepwork to automate Fireblocks flows with 98% accuracy without needing an API.
No. Fireblocks does not currently offer SCIM-based user provisioning, leaving IT teams to manage user lifecycle changes manually.
Stepwork automates Fireblocks 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 Fireblocks 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 complex api security, federated idp not available, lack of standardized provisioning. 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 Fireblocks with 98% accuracy — in a 15-minute demo.
Book a Demo