Bluelab does not currently offer SCIM-based user provisioning. Stepwork automates Bluelab provisioning with 98% accuracy — no API required.
No SCIM/SSO → account access is managed manually per user/device setup. Complexity Vector: Operational access depends on device enrollment + app UI states, so Stepwork automates repeatable UI steps and verification across accounts/devices.
You are correct; Edenic does not natively support SCIM. That means you can’t automate provisioning/offboarding for operators, so access cleanup turns into manual, error-prone work…which is why teams use Stepwork to automate Bluelab flows with 98% accuracy without needing an API.
No. Bluelab does not currently offer SCIM-based user provisioning, leaving IT teams to manage user lifecycle changes manually.
Stepwork automates Bluelab 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 Bluelab 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/sso for account lifecycle management.. Additional risks include shared mobile logins, manual revocation when staff changes, access reviews have no admin-grade audit trail.. Stepwork eliminates these risks by automating the entire provisioning workflow.
See how Stepwork provisions users in Bluelab 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, mirroring your organization's security posture.