Obsidian does not currently offer SCIM-based user provisioning. Stepwork automates Obsidian provisioning with 98% accuracy — no API required.
No native SCIM endpoint Complexity Vector: Security-critical roles and access are managed in-product; without SCIM, lifecycle control drifts and requires UI ops
Security teams need provable control over who can access posture and remediation workflows, and Obsidian doesn’t show a native SCIM endpoint here. Stepwork enforces and records UI-level access changes around Obsidian…which is why teams use Stepwork to automate Obsidian Security flows with 98% accuracy without needing an API.
Obsidian supports SAML sign-on. Stepwork authenticates through your existing identity provider — the same way your employees do.
No. Obsidian does not currently offer SCIM-based user provisioning, leaving IT teams to manage user lifecycle changes manually.
Stepwork automates Obsidian 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 Obsidian 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 who can access security posture + remediation. Additional risks include audit gaps; over-privileged access; delayed offboarding. Stepwork eliminates these risks by automating the entire provisioning workflow.
See how Stepwork provisions users in Obsidian 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.