Cypress does not currently offer SCIM-based user provisioning. Stepwork automates Cypress provisioning with 98% accuracy — no API required.
No native SCIM endpoint Complexity Vector: User and project permissions are administered through org and project UIs rather than SCIM
You’re right—Cypress does not expose a native SCIM endpoint, so access changes can’t be automated through your IdP. Stepwork automates Cypress admin workflows in the UI…which is why teams use Stepwork to automate Cypress flows with 98% accuracy without needing an API.
Cypress supports SAML sign-on. Stepwork authenticates through your existing identity provider — the same way your employees do.
No. Cypress does not currently offer SCIM-based user provisioning, leaving IT teams to manage user lifecycle changes manually.
Stepwork automates Cypress 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 Cypress 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 access control for test infrastructure. Additional risks include permission sprawl;, delayed offboarding;, audit gaps. Stepwork eliminates these risks by automating the entire provisioning workflow.
See how Stepwork provisions users in Cypress 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.