Compugen does not currently offer SCIM-based user provisioning. Stepwork automates Compugen provisioning with 98% accuracy — no API required.
Compugen environments lack unified SCIM support. Complexity Vector: Each client portal differs, requiring UI-based provisioning that Stepwork can standardize.
You are correct; Compugen environments lack native SCIM support, forcing manual access handling across systems. This creates inconsistency and operational drag, which is why teams use Stepwork to automate Compugen flows with 98% accuracy without needing an API.
Compugen supports SAML sign-on. Stepwork authenticates through your existing identity provider — the same way your employees do.
No. Compugen does not currently offer SCIM-based user provisioning, leaving IT teams to manage user lifecycle changes manually.
Stepwork automates Compugen 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 Compugen 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 centralized identity automation. Additional risks include manual onboarding, inconsistent access. 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 Compugen with 98% accuracy — in a 15-minute demo.
Book a Demo