IconScout does not currently offer SCIM-based user provisioning. Stepwork automates IconScout provisioning with 98% accuracy — no API required.
No native SCIM. Complexity Vector: Access spans web + plugins, so lifecycle control depends on manual admin cleanup.
You are correct; IconScout does not natively support SCIM. That forces manual access management across web and plugin surfaces, which is why teams use Stepwork to automate IconScout flows with 98% accuracy without needing an API.
No. IconScout does not currently offer SCIM-based user provisioning, leaving IT teams to manage user lifecycle changes manually.
Stepwork automates IconScout 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 IconScout 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 provisioning.. Additional risks include social login accounts, seat changes are manual, access reviews are manual.. Stepwork eliminates these risks by automating the entire provisioning workflow.
See how Stepwork provisions users in IconScout 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.