SPINS does not currently offer SCIM-based user provisioning. Stepwork automates SPINS provisioning with 98% accuracy — no API required.
No native SCIM support. Complexity Vector: Analytics sub-product access and reporting roles prevent automated lifecycle controls.
You are correct; SPINS does not natively support SCIM. This means standard SPINS integrations cannot provision users, forcing IT to rely on manual spreadsheets, which is why teams use Stepwork to automate SPINS flows with 98% accuracy without needing an API.
SPINS supports SAML sign-on. Stepwork authenticates through your existing identity provider — the same way your employees do.
No. SPINS does not currently offer SCIM-based user provisioning, leaving IT teams to manage user lifecycle changes manually.
Stepwork automates SPINS 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 SPINS 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. Additional risks include manual seat provisioning, data access tiers, role sync challenges. Stepwork eliminates these risks by automating the entire provisioning workflow.
See how Stepwork provisions users in SPINS 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.