Rootly does not currently offer SCIM-based user provisioning. Stepwork automates Rootly provisioning with 98% accuracy — no API required.
No native SCIM endpoint Complexity Vector: Responder roles are assigned via UI and Slack-based workflows
You’re right—Rootly does not expose a SCIM endpoint, so responder access must be managed manually. Stepwork automates those Rootly workflows directly…which is why teams use Stepwork to automate Rootly flows with 98% accuracy without needing an API.
Rootly supports SAML sign-on. Stepwork authenticates through your existing identity provider — the same way your employees do.
No. Rootly does not currently offer SCIM-based user provisioning, leaving IT teams to manage user lifecycle changes manually.
Stepwork automates Rootly 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 Rootly 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 control of incident responder access. Additional risks include over-permissioned users; delayed offboarding; audit gaps. Stepwork eliminates these risks by automating the entire provisioning workflow.
No. 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.
See how Stepwork provisions users in Rootly with 98% accuracy — in a 15-minute demo.
Book a Demo