Kyriba does not currently offer SCIM-based user provisioning. Stepwork automates Kyriba provisioning with 98% accuracy — no API required.
SSO without SCIM provisioning. Complexity Vector: Treasury entitlements and authorization workflows require repeatable admin steps and evidence capture.
In treasury systems, it’s risky when SSO exists but user lifecycle and entitlements still require manual controls. Stepwork can standardize access workflows and capture audit-ready proof, which is why teams use Stepwork to automate Kyriba flows with 98% accuracy without needing an API.
Kyriba supports SAML sign-on. Stepwork authenticates through your existing identity provider — the same way your employees do.
No. Kyriba does not currently offer SCIM-based user provisioning, leaving IT teams to manage user lifecycle changes manually.
Stepwork automates Kyriba 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 Kyriba 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 lifecycle.. Additional risks include saml sso is separate from provisioning, entitlements are finance-grade, evidence is audit-driven.. Stepwork eliminates these risks by automating the entire provisioning workflow.
See how Stepwork provisions users in Kyriba 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 via SAML, mirroring your organization's security posture.