CloudCall does not currently offer SCIM-based user provisioning. Stepwork automates CloudCall provisioning with 98% accuracy — no API required.
SCIM not clearly documented Complexity Vector: Telephony permissions are UI-managed and account-scoped
It’s frustrating when telephony platforms support SSO but don’t clearly document SCIM provisioning. …which is why teams use Stepwork to automate CloudCall flows with 98% accuracy without needing an API.
CloudCall supports SAML sign-on. Stepwork authenticates through your existing identity provider — the same way your employees do.
No. CloudCall does not currently offer SCIM-based user provisioning, leaving IT teams to manage user lifecycle changes manually.
Stepwork automates CloudCall 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 CloudCall 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 user lifecycle can’t be standardized without verified scim support.. Additional risks include manual onboarding; role drift; slow offboarding. Stepwork eliminates these risks by automating the entire provisioning workflow.
See how Stepwork provisions users in CloudCall 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.