Continued does not currently offer SCIM-based user provisioning. Stepwork automates Continued provisioning with 98% accuracy — no API required.
No SCIM; seat-based group admin. Complexity Vector: Group enrollment, seat moves, and compliance reporting require repeatable UI administration and verification across cohorts.
You are correct; Continued does not natively support SCIM. This means organizations must manage user lifecycle and access evidence manually through the portal…which is why teams use Stepwork to automate Continued flows with 98% accuracy without needing an API.
No. Continued does not currently offer SCIM-based user provisioning, leaving IT teams to manage user lifecycle changes manually.
Stepwork automates Continued 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 Continued 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 Continued with 98% accuracy — in a 15-minute demo.
Book a DemoThe primary risk is no scim lifecycle automation.. Additional risks include manual seat assignment, offboarding is manual, compliance evidence relies on exports/certificates.. 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.