Virtual Cabinet does not currently offer SCIM-based user provisioning. Stepwork automates Virtual Cabinet provisioning with 98% accuracy — no API required.
No SCIM support Complexity Vector: Document access provisioning depends on manual administrative control
You’re not wrong—Virtual Cabinet doesn’t natively support SCIM, forcing admins into manual user management. This creates inefficiencies in access control, which is why teams use Stepwork to automate Virtual Cabinet flows with 98% accuracy without needing an API.
Virtual Cabinet supports SAML sign-on. Stepwork authenticates through your existing identity provider — the same way your employees do.
No. Virtual Cabinet does not currently offer SCIM-based user provisioning, leaving IT teams to manage user lifecycle changes manually.
Stepwork automates Virtual Cabinet 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 Virtual Cabinet 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.
See how Stepwork provisions users in Virtual Cabinet with 98% accuracy — in a 15-minute demo.
Book a DemoThe primary risk is manual work. Additional risks include manual onboarding, manual offboarding, role 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 via SAML, mirroring your organization's security posture.