Blanchard does not currently offer SCIM-based user provisioning. Stepwork automates Blanchard provisioning with 98% accuracy — no API required.
No native SCIM; portal-based SAML only. Complexity Vector: Access is tied to programs, cohorts, and certifications inside training portals, so joiner/mover/leaver changes require repeated UI updates rather than directory-driven automation.
You are correct; Blanchard does not natively support SCIM. This means learner onboarding, offboarding, and course access changes depend on manual portal updates instead of automated lifecycle control…which is why teams use Stepwork to automate Blanchard flows with 98% accuracy without needing an API.
Blanchard supports SAML sign-on. Stepwork authenticates through your existing identity provider — the same way your employees do.
No. Blanchard does not currently offer SCIM-based user provisioning, leaving IT teams to manage user lifecycle changes manually.
Stepwork automates Blanchard 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 Blanchard 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 Blanchard with 98% accuracy — in a 15-minute demo.
Book a DemoThe primary risk is no scim lifecycle automation.. Additional risks include manual learner onboarding and removal., course and cohort access drifts over time., certification access requires ui cleanup.. 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 via SAML, mirroring your organization's security posture.