CleanSpace does not currently offer SCIM-based user provisioning. Stepwork automates CleanSpace provisioning with 98% accuracy — no API required.
CleanSpace does not expose SCIM or SSO because access is tied to proprietary industrial systems rather than SaaS identity layers. Complexity Vector: Hybrid hardware plus browser portals require human-like interaction, making API automation impractical and requiring Stepwork.
You are correct; CleanSpace does not natively support SCIM. This forces admins to manage access manually with little visibility into changes. This limitation creates operational risk, which is why teams use Stepwork to automate CleanSpace flows with 98% accuracy without needing an API.
No. CleanSpace does not currently offer SCIM-based user provisioning, leaving IT teams to manage user lifecycle changes manually.
Stepwork automates CleanSpace 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 CleanSpace 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 user lifecycle automation. Additional risks include manual role assignment, shared accounts, poor audit trails. 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.
See how Stepwork provisions users in CleanSpace with 98% accuracy — in a 15-minute demo.
Book a Demo