Complinity does not currently offer SCIM-based user provisioning. Stepwork automates Complinity provisioning with 98% accuracy — no API required.
No SCIM; UI-managed roles; module-level permissions. Complexity Vector: GRC evidence and permissions span multiple modules and workflows, so access state and audit artifacts must be validated directly in the application UI.
GRC programs fall apart when access and evidence aren’t consistently provable across modules and workflows. Without SCIM, Complinity pushes lifecycle control and evidence collection into manual UI steps…which is why teams use Stepwork to automate Complinity flows with 98% accuracy without needing an API.
No. Complinity does not currently offer SCIM-based user provisioning, leaving IT teams to manage user lifecycle changes manually.
Stepwork automates Complinity 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 Complinity 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.
See how Stepwork provisions users in Complinity with 98% accuracy — in a 15-minute demo.
Book a DemoThe primary risk is no scim lifecycle automation for compliance users.. Additional risks include role drift across modules, access reviews require ui checks, evidence collection depends on exports/screenshots.. 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, mirroring your organization's security posture.