Kubiya does not currently offer SCIM-based user provisioning. Stepwork automates Kubiya provisioning with 98% accuracy — no API required.
No published SCIM provisioning. Complexity Vector: Automation spans many systems, so access and execution need consistent guardrails and evidence.
You’re not wrong—Kubiya connects to many DevOps systems, but lifecycle governance across those integrations isn’t automatically solved by a single standard. Stepwork can orchestrate the browser-based workflows and verification steps for safe access changes, which is why teams use Stepwork to automate Kubiya flows with 98% accuracy without needing an API.
No. Kubiya does not currently offer SCIM-based user provisioning, leaving IT teams to manage user lifecycle changes manually.
Stepwork automates Kubiya 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 Kubiya 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 scim lifecycle published.. Additional risks include multi-tool access surfaces, agent actions need guardrails, approvals are workflow-specific.. Stepwork eliminates these risks by automating the entire provisioning workflow.
See how Stepwork provisions users in Kubiya with 98% accuracy — in a 15-minute demo.
Book a DemoNo. 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.