Aha does not currently offer SCIM-based user provisioning. Stepwork automates Aha provisioning with 98% accuracy — no API required.
No verified app-owned SCIM endpoint Complexity Vector: Public evidence shows requests/connectors, but not confirmation of an Aha-controlled /scim/v2/* endpoint
You’re not wrong—Aha! supports SSO, but an app-owned SCIM 2.0 endpoint isn’t clearly confirmed in the public materials, so lifecycle automation can still be brittle. Stepwork automates the admin UI workflows to enforce access cleanly…which is why teams use Stepwork to automate Aha! flows with 98% accuracy without needing an API.
Aha supports SAML sign-on. Stepwork authenticates through your existing identity provider — the same way your employees do.
No. Aha does not currently offer SCIM-based user provisioning, leaving IT teams to manage user lifecycle changes manually.
Stepwork automates Aha 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 Aha 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 manual onboarding/offboarding of product users. Additional risks include permission sprawl;, audit gaps;, delayed deprovisioning. Stepwork eliminates these risks by automating the entire provisioning workflow.
See how Stepwork provisions users in Aha 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.