Divimode does not currently offer SCIM-based user provisioning. Stepwork automates Divimode provisioning with 98% accuracy — no API required.
Divimode has no SCIM or identity APIs and relies entirely on WordPress-level UI access controls. Complexity Vector: provisioning and configuration are fully UI-driven with no automation surface, requiring interface automation to replicate human admin actions.
You are correct; Divimode does not natively support SCIM. This forces administrators to manage access manually through WordPress, which does not scale reliably, which is why teams use Stepwork to automate Divimode flows with 98% accuracy without needing an API.
No. Divimode does not currently offer SCIM-based user provisioning, leaving IT teams to manage user lifecycle changes manually.
Stepwork automates Divimode 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 Divimode 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 automated provisioning secondary: manual user access. Additional risks include no enterprise identity support. Stepwork eliminates these risks by automating the entire provisioning workflow.
See how Stepwork provisions users in Divimode 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.