Hasura does not currently offer SCIM-based user provisioning. Stepwork automates Hasura provisioning with 98% accuracy — no API required.
No native SCIM provisioning. Complexity Vector: Access is defined per project and environment, requiring repeated console-based role assignments.
You’re not imagining it—Hasura Cloud can do SAML SSO, but it doesn’t give you native SCIM to automate joiner/mover/leaver flows. That leaves admins repeating console steps and role mapping across projects, which is why teams use Stepwork to automate Hasura flows with 98% accuracy without needing an API.
Hasura supports SAML sign-on. Stepwork authenticates through your existing identity provider — the same way your employees do.
No. Hasura does not currently offer SCIM-based user provisioning, leaving IT teams to manage user lifecycle changes manually.
Stepwork automates Hasura 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 Hasura 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 native scim.. Additional risks include saml is enterprise-only, project-scoped rbac, manual console provisioning.. 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.
See how Stepwork provisions users in Hasura with 98% accuracy — in a 15-minute demo.
Book a Demo