LiquidityBook does not currently offer SCIM-based user provisioning. Stepwork automates LiquidityBook provisioning with 98% accuracy — no API required.
No public SCIM details. Complexity Vector: Trading entitlements and audit requirements create manual access governance work.
For trading systems, it’s stressful when user lifecycle and entitlements aren’t automated because access drift becomes an audit risk. Stepwork can standardize the repeatable admin workflows and capture proof, which is why teams use Stepwork to automate LiquidityBook flows with 98% accuracy without needing an API.
LiquidityBook supports SAML sign-on. Stepwork authenticates through your existing identity provider — the same way your employees do.
No. LiquidityBook does not currently offer SCIM-based user provisioning, leaving IT teams to manage user lifecycle changes manually.
Stepwork automates LiquidityBook 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 LiquidityBook 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.. Additional risks include sso setup is enterprise-led, entitlements are role-heavy, audit evidence is manual.. 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 LiquidityBook with 98% accuracy — in a 15-minute demo.
Book a Demo