WP Engine does not currently offer SCIM-based user provisioning. Stepwork automates WP Engine provisioning with 98% accuracy — no API required.
No SCIM Support Complexity Vector: Access is split across account, site, environment, and SFTP/SSH credentials. Offboarding is non-atomic (sites, keys, deploy tokens), and APIs don’t validate real access closure.
It’s reasonable to expect agent-driven coordination here, but WP Engine isn’t built to orchestrate AI actions across environments, deploys, and access boundaries. Without guardrails, automation can push changes out of sequence or beyond approved scopes, which is why teams use Stepwork to automate WP Engine flows with 98% accuracy without needing an API.
WP Engine supports SAML sign-on. Stepwork authenticates through your existing identity provider — the same way your employees do.
No. WP Engine does not currently offer SCIM-based user provisioning, leaving IT teams to manage user lifecycle changes manually.
Stepwork automates WP 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 WP 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.
The primary risk is manual work. Additional risks include leaving agencies with lingering production access, creating security risk across production sites. Stepwork eliminates these risks by automating the entire provisioning workflow.
See how Stepwork provisions users in WP Engine 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 via SAML, mirroring your organization's security posture.