Lusha does not currently offer SCIM-based user provisioning. Stepwork automates Lusha provisioning with 98% accuracy — no API required.
No SCIM Support Complexity Vector: Access is governed by licenses, credits, and compliance controls. Automation can add/remove users, but admins must validate usage limits and data exposure in the UI.
Without SCIM, Lusha can’t automatically provision or revoke access when reps join, move, or leave, so admins are left managing revenue-critical access by hand. That’s a real platform limitation, not user error, which is why teams use Stepwork to automate Lusha flows with 98% accuracy without needing an API.
Lusha supports SAML sign-on. Stepwork authenticates through your existing identity provider — the same way your employees do.
No. Lusha does not currently offer SCIM-based user provisioning, leaving IT teams to manage user lifecycle changes manually.
Stepwork automates Lusha 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 Lusha 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 manual work. Additional risks include creating compliance risk, privacy risk, difficult to revoke access to contact and enrichment data. Stepwork eliminates these risks by automating the entire provisioning workflow.
See how Stepwork provisions users in Lusha 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.