Kymeta does not currently offer SCIM-based user provisioning. Stepwork automates Kymeta provisioning with 98% accuracy — no API required.
No published SCIM provisioning. Complexity Vector: Access control is tied to customer portal processes and device/service management workflows.
You’re right to expect standardized provisioning, but Kymeta’s customer portal doesn’t publish SCIM-based lifecycle controls. Stepwork can run the repeatable portal workflows and capture proof for access changes, which is why teams use Stepwork to automate Kymeta flows with 98% accuracy without needing an API.
No. Kymeta does not currently offer SCIM-based user provisioning, leaving IT teams to manage user lifecycle changes manually.
Stepwork automates Kymeta 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 Kymeta 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 surface published.. Additional risks include customer portal accounts are managed manually, access is customer-rep driven, evidence is portal-based.. Stepwork eliminates these risks by automating the entire provisioning workflow.
See how Stepwork provisions users in Kymeta 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.