Jeli does not currently offer SCIM-based user provisioning. Stepwork automates Jeli provisioning with 98% accuracy — no API required.
SSO available, no SCIM. Complexity Vector: Incident workflows span Jeli + PagerDuty, requiring consistent access mapping and evidence.
You’re right to expect lifecycle automation—Jeli supports SSO, but that doesn’t automatically give you SCIM-based provisioning. Stepwork can orchestrate the admin workflows and capture proof across Jeli/PagerDuty access, which is why teams use Stepwork to automate Jeli flows with 98% accuracy without needing an API.
Jeli supports SAML sign-on. Stepwork authenticates through your existing identity provider — the same way your employees do.
No. Jeli does not currently offer SCIM-based user provisioning, leaving IT teams to manage user lifecycle changes manually.
Stepwork automates Jeli 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 Jeli 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 native scim.. Additional risks include sso is plan-gated (legacy), auth is backed by auth0, workflow access spans pagerduty.. 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 via SAML, mirroring your organization's security posture.
See how Stepwork provisions users in Jeli with 98% accuracy — in a 15-minute demo.
Book a Demo