Tegus does not currently offer SCIM-based user provisioning. Stepwork automates Tegus provisioning with 98% accuracy — no API required.
SCIM not supported. Complexity Vector: Investor-level entitlements require manual portal management without provisioning APIs.
Automate the collection of access evidence from Tegus for SOC2 audits. Because Tegus lacks native SCIM provisioning, investor access must be reviewed and documented manually. Stepwork captures screenshots and logs to maintain chain of custody, which is why teams use Stepwork to automate Tegus flows with 98% accuracy without needing an API.
Tegus supports SAML sign-on. Stepwork authenticates through your existing identity provider — the same way your employees do.
No. Tegus does not currently offer SCIM-based user provisioning, leaving IT teams to manage user lifecycle changes manually.
Stepwork automates Tegus 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 Tegus 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 automated investor provisioning.. Additional risks include manual access reviews, compliance documentation gaps, license tier restrictions.. Stepwork eliminates these risks by automating the entire provisioning workflow.
See how Stepwork provisions users in Tegus 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.