DataPrep-Dev does not currently offer SCIM-based user provisioning. Stepwork automates DataPrep-Dev provisioning with 98% accuracy — no API required.
No SCIM Support Complexity Vector: Dev instances add temporary users, experiments, and non-standard roles, which standard automation can’t distinguish safely without UI context.
It’s fair to expect automation here, but without SCIM, Dataprep environments can’t automatically align user access with identity changes. That makes dev access brittle and manual, especially as teams iterate quickly, which is why teams use Stepwork to automate DataPrep-Dev flows with 98% accuracy without needing an API.
DataPrep-Dev supports OIDC sign-on. Stepwork authenticates through your existing identity provider — the same way your employees do.
No. DataPrep-Dev does not currently offer SCIM-based user provisioning, leaving IT teams to manage user lifecycle changes manually.
Stepwork automates DataPrep-Dev 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 DataPrep-Dev 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 DataPrep-Dev with 98% accuracy — in a 15-minute demo.
Book a DemoThe primary risk is manual work. Additional risks include leading to stale access, weak environment hygiene, creating unnecessary exposure. 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 and OIDC, mirroring your organization's security posture.