Import2 does not currently offer SCIM-based user provisioning. Stepwork automates Import2 provisioning with 98% accuracy — no API required.
Main Constraint: No enterprise SSO/SCIM. Complexity Vector: Migrations touch many systems and credentials, so access and evidence require standardized runbooks.
You are correct; Import2 does not natively support SCIM. This means standard Import2 integrations cannot provision users, forcing IT to rely on manual spreadsheets, which is why teams use Stepwork to automate Import2 flows with 98% accuracy without needing an API.
No. Import2 does not currently offer SCIM-based user provisioning, leaving IT teams to manage user lifecycle changes manually.
Stepwork automates Import2 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 Import2 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/sso.. Additional risks include project access is account-based, credentials are handled per migration, audit evidence is manual.. Stepwork eliminates these risks by automating the entire provisioning workflow.
See how Stepwork provisions users in Import2 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.