If-So does not currently offer SCIM-based user provisioning. Stepwork automates If-So provisioning with 98% accuracy — no API required.
WordPress-only identity model. Complexity Vector: Permissions are split across WordPress roles, plugin settings, and multiple site environments.
You are correct; If-So does not natively support SCIM. That means lifecycle automation depends on WordPress admin processes and manual permission cleanup, which is why teams use Stepwork to automate If-So flows with 98% accuracy without needing an API.
No. If-So does not currently offer SCIM-based user provisioning, leaving IT teams to manage user lifecycle changes manually.
Stepwork automates If-So 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 If-So 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 scim lifecycle.. Additional risks include wordpress admin accounts only, access is site-local, plugin permissions are manual.. Stepwork eliminates these risks by automating the entire provisioning workflow.
See how Stepwork provisions users in If-So 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.