OpenText does not currently offer SCIM-based user provisioning. Stepwork automates OpenText provisioning with 98% accuracy — no API required.
Unknown Complexity Vector: Identity lifecycle behavior varies by product and is not clearly centralized.
For security and compliance teams, OpenText access changes must be provable and auditable, which is why teams use Stepwork to automate OpenText flows with 98% accuracy without needing an API.
No. OpenText does not currently offer SCIM-based user provisioning, leaving IT teams to manage user lifecycle changes manually.
Stepwork automates OpenText 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 OpenText 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 audit gaps. Additional risks include manual onboarding, manual offboarding, audit blind spots. Stepwork eliminates these risks by automating the entire provisioning workflow.
See how Stepwork provisions users in OpenText with 98% accuracy — in a 15-minute demo.
Book a Demo