Git-Zen does not currently offer SCIM-based user provisioning. Stepwork automates Git-Zen provisioning with 98% accuracy — no API required.
No IAM lifecycle controls. Complexity Vector: Access spans multiple systems and app installs.
You are correct; Git-Zen does not natively support SCIM. This leaves access cleanup across Zendesk and dev tools manual, which is why teams use Stepwork to automate Git-Zen flows with 98% accuracy without needing an API.
No. Git-Zen does not currently offer SCIM-based user provisioning, leaving IT teams to manage user lifecycle changes manually.
Stepwork automates Git-Zen 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 Git-Zen 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 or sso.. Additional risks include connector permission drift, manual setup per instance, offboarding checklist-driven.. Stepwork eliminates these risks by automating the entire provisioning workflow.
See how Stepwork provisions users in Git-Zen 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.