Instatus does not currently offer SCIM-based user provisioning. Stepwork automates Instatus provisioning with 98% accuracy — no API required.
SCIM Status: SAML only; no SCIM. Complexity Vector: Access is tied to UI-managed pages and incident roles. Stepwork automates repeatable UI permission updates.
You are correct; Instatus does not natively support SCIM. This means teams must manage access manually for status pages, which is why teams use Stepwork to automate Instatus flows with 98% accuracy without needing an API.
Instatus supports SAML sign-on. Stepwork authenticates through your existing identity provider — the same way your employees do.
No. Instatus does not currently offer SCIM-based user provisioning, leaving IT teams to manage user lifecycle changes manually.
Stepwork automates Instatus 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 Instatus 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 scim. Additional risks include manual roles, page access drift, offboarding gaps. Stepwork eliminates these risks by automating the entire provisioning workflow.
See how Stepwork provisions users in Instatus 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.