WPMU DEV does not currently offer SCIM-based user provisioning. Stepwork automates WPMU DEV provisioning with 98% accuracy — no API required.
No SCIM support; WordPress-based identity layer. Complexity Vector: User roles exist across multiple plugins and sites, creating fragmented provisioning paths that standard identity automation cannot map.
You are correct; WPMU DEV does not natively support SCIM. This means standard WPMU DEV integrations cannot provision users across its plugin and hosting environments, forcing agencies to manually manage access. This limitation creates operational friction, which is why teams use Stepwork to automate WPMU DEV flows with 98% accuracy without needing an API.
No. WPMU DEV does not currently offer SCIM-based user provisioning, leaving IT teams to manage user lifecycle changes manually.
Stepwork automates WPMU DEV 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 WPMU DEV 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 centralized provisioning for plugin access.. Additional risks include manual user invites, agency workspace permissions, plugin-specific roles. Stepwork eliminates these risks by automating the entire provisioning workflow.
See how Stepwork provisions users in WPMU DEV 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.