Fleet does not currently offer SCIM-based user provisioning. Stepwork automates Fleet provisioning with 98% accuracy — no API required.
No SCIM Support Complexity Vector: Telematics platform access is device- and client-specific. APIs do not validate entitlements or handle offboarding safely without UI context.
You are correct; Fleet does not natively support SCIM, keeping user provisioning manual — which is why teams use Stepwork to automate Fleet flows with 98% accuracy without needing an API.
Fleet supports SAML sign-on. Stepwork authenticates through your existing identity provider — the same way your employees do.
No. Fleet does not currently offer SCIM-based user provisioning, leaving IT teams to manage user lifecycle changes manually.
Stepwork automates Fleet 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 Fleet 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 admin, unclear sso. Stepwork eliminates these risks by automating the entire provisioning workflow.
See how Stepwork provisions users in Fleet 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.