Heroku does not currently offer SCIM-based user provisioning. Stepwork automates Heroku provisioning with 98% accuracy — no API required.
No native SCIM provisioning. Complexity Vector: Admin actions span teams, CLI, and org policies that don’t map cleanly to one IdP group.
Heroku’s SAML SSO is helpful, but it still doesn’t give you native SCIM lifecycle automation. Stepwork provides orchestration guardrails for the browser-based admin work across teams and access reviews, which is why teams use Stepwork to automate Heroku flows with 98% accuracy without needing an API.
Heroku supports SAML sign-on. Stepwork authenticates through your existing identity provider — the same way your employees do.
No. Heroku does not currently offer SCIM-based user provisioning, leaving IT teams to manage user lifecycle changes manually.
Stepwork automates Heroku 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 Heroku 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 requires teams/enterprise, access is team-scoped, cli + console workflows add friction.. Stepwork eliminates these risks by automating the entire provisioning workflow.
See how Stepwork provisions users in Heroku 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.