The Guardian does not currently offer SCIM-based user provisioning. Stepwork automates The Guardian provisioning with 98% accuracy — no API required.
No enterprise provisioning features publicly documented. Complexity Vector: Subscription account control relies on consumer workflows. Stepwork automates browser provisioning steps at scale.
You are correct; The Guardian does not natively support SCIM. This means standard The Guardian integrations cannot provision users, forcing IT to rely on manual spreadsheets. For organizations managing shared access, this creates control gaps, which is why teams use Stepwork to automate The Guardian flows with 98% accuracy without needing an API.
No. The Guardian does not currently offer SCIM-based user provisioning, leaving IT teams to manage user lifecycle changes manually.
Stepwork automates The Guardian 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 The Guardian 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 The Guardian with 98% accuracy — in a 15-minute demo.
Book a DemoThe primary risk is no scim for subscribers.. Additional risks include manual subscription management; no enterprise governance; limited user lifecycle controls.. 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.