Dilisense does not currently offer SCIM-based user provisioning. Stepwork automates Dilisense provisioning with 98% accuracy — no API required.
API keys, no SCIM. Complexity Vector: Access is token-based across environments.
You’re not wrong—compliance APIs are hard to govern when access is controlled by long-lived keys. Dilisense delivers AML screening but lacks SCIM-based lifecycle controls, which is why teams use Stepwork to automate Dilisense flows with 98% accuracy without needing an API.
No. Dilisense does not currently offer SCIM-based user provisioning, leaving IT teams to manage user lifecycle changes manually.
Stepwork automates Dilisense 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 Dilisense 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.. Additional risks include api key sprawl, manual key rotation, offboarding misses tokens.. Stepwork eliminates these risks by automating the entire provisioning workflow.
See how Stepwork provisions users in Dilisense 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.