Divi Engine does not currently offer SCIM-based user provisioning. Stepwork automates Divi Engine provisioning with 98% accuracy — no API required.
WordPress logins, no SCIM. Complexity Vector: Permissions inherit WordPress roles and plugins.
You’re not wrong—WordPress ecosystems don’t provide SCIM-style lifecycle automation. Divi Engine relies on WordPress roles and plugins for access, which is why teams use Stepwork to automate Divi Engine flows with 98% accuracy without needing an API.
No. Divi Engine does not currently offer SCIM-based user provisioning, leaving IT teams to manage user lifecycle changes manually.
Stepwork automates Divi Engine 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 Divi Engine 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 Divi Engine with 98% accuracy — in a 15-minute demo.
Book a DemoThe primary risk is no scim support.. Additional risks include wordpress-based access, manual role mapping, offboarding handled in admin ui.. 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.