Curinos does not currently offer SCIM-based user provisioning. Stepwork automates Curinos provisioning with 98% accuracy — no API required.
Client-specific access; no SCIM surface. Complexity Vector: Permissions and evidence live across client portals, reports, and platform UI workflows that differ by institution.
In finance, it’s stressful when access and evidence are scattered across portals and reports without lifecycle controls. Stepwork automates UI-based verification and evidence capture across Curinos workflows…which is why teams use Stepwork to automate Curinos flows with 98% accuracy without needing an API.
No. Curinos does not currently offer SCIM-based user provisioning, leaving IT teams to manage user lifecycle changes manually.
Stepwork automates Curinos 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 Curinos 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 surface for client access.. Additional risks include access varies by engagement/tool, role changes are manual, evidence collection is document/portal-driven.. Stepwork eliminates these risks by automating the entire provisioning workflow.
See how Stepwork provisions users in Curinos 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.