Respondent does not currently offer SCIM-based user provisioning. Stepwork automates Respondent provisioning with 98% accuracy — no API required.
No documented SSO or SCIM. Complexity Vector: Study-based role management requires UI-level administrative changes.
You are correct; Respondent does not natively support SCIM. This forces manual provisioning and increases offboarding risk. Stepwork automates Respondent admin workflows directly in the browser, which is why teams use Stepwork to automate Respondent flows with 98% accuracy without needing an API.
No. Respondent does not currently offer SCIM-based user provisioning, leaving IT teams to manage user lifecycle changes manually.
Stepwork automates Respondent 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 Respondent 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.
See how Stepwork provisions users in Respondent with 98% accuracy — in a 15-minute demo.
Book a DemoThe primary risk is no enterprise lifecycle provisioning.. Additional risks include study-level permissions; incentive payout roles; manual access removal.. 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, mirroring your organization's security posture.