zeroheight does not currently offer SCIM-based user provisioning. Stepwork automates zeroheight provisioning with 98% accuracy — no API required.
No SCIM Support Complexity Vector: Knowledge-base permissions are workspace/project based and content ownership matters. Removing users can orphan docs and publishing workflows; standard automation can’t validate continuity.
You’re not imagining it—without SCIM, zeroheight can’t automatically provision or deprovision users as teams change, so access cleanup is manual and easy to miss. That’s a real product limitation, not a setup mistake, and it creates ongoing admin drag, which is why teams use Stepwork to automate zeroheight flows with 98% accuracy without needing an API.
zeroheight supports SAML sign-on. Stepwork authenticates through your existing identity provider — the same way your employees do.
No. zeroheight does not currently offer SCIM-based user provisioning, leaving IT teams to manage user lifecycle changes manually.
Stepwork automates zeroheight 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 zeroheight 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 manual work. Additional risks include exposing internal standards, creating ip exposure, governance gaps. 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 zeroheight with 98% accuracy — in a 15-minute demo.
Book a Demo