Carrier Direct does not currently offer SCIM-based user provisioning. Stepwork automates Carrier Direct provisioning with 98% accuracy — no API required.
No native SCIM; account lifecycle management is manual. Complexity Vector: Dispatch permissions and operational workflows rely on UI-enforced roles, assignments, and visibility that Stepwork automates reliably.
You are correct; Carrier Direct does not natively support SCIM. This means standard Carrier Direct integrations can’t automate provisioning or deprovisioning, leaving ops teams to manage access manually as staff and drivers change…which is why teams use Stepwork to automate Carrier Direct flows with 98% accuracy without needing an API.
No. Carrier Direct does not currently offer SCIM-based user provisioning, leaving IT teams to manage user lifecycle changes manually.
Stepwork automates Carrier Direct 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 Carrier Direct 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.
See how Stepwork provisions users in Carrier Direct with 98% accuracy — in a 15-minute demo.
Book a DemoThe primary risk is no scim lifecycle automation for dispatcher/driver/admin roles.. Additional risks include high turnover makes offboarding manual, permissions are operationally sensitive, audit trails are ui-bound.. Stepwork eliminates these risks by automating the entire provisioning workflow.
No. 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.