DataPrep does not currently offer SCIM-based user provisioning. Stepwork automates DataPrep provisioning with 98% accuracy — no API required.
No SCIM Support Complexity Vector: Access depends on Google identity, project roles, and underlying data sources. Effective permissions are inherited and asynchronous, making API-only automation incomplete.
Dataprep handles data preparation well, but it wasn’t built for agent-level orchestration across pipelines, identities, and downstream systems. Without external guardrails, AI-driven workflows can’t safely coordinate changes end to end which is why teams use Stepwork to automate DataPrep flows with 98% accuracy without needing an API.
DataPrep supports OIDC sign-on. Stepwork authenticates through your existing identity provider — the same way your employees do.
No. DataPrep does not currently offer SCIM-based user provisioning, leaving IT teams to manage user lifecycle changes manually.
Stepwork automates DataPrep 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 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 with 98% accuracy — in a 15-minute demo.
Book a DemoThe primary risk is provisioning is tied to cloud identity. Additional risks include making access cleanup hard to automate, fine-grained automation of user access and revocation is difficult, leading to over-permissioning. 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.