GEM does not currently offer SCIM-based user provisioning. Stepwork automates GEM provisioning with 98% accuracy — no API required.
GEM supports SAML SSO but does not publicly document native SCIM provisioning. Complexity Vector: Without SCIM, recruiting roles tied to campaigns and integrations require manual UI cleanup during joiner, mover, and leaver events.
Avoid upgrading purely for identity standardization. Stepwork automates onboarding and offboarding steps inside GEM…which is why teams use Stepwork to automate GEM flows with 98% accuracy without needing an API.
GEM supports SAML sign-on. Stepwork authenticates through your existing identity provider — the same way your employees do.
No. GEM does not currently offer SCIM-based user provisioning, leaving IT teams to manage user lifecycle changes manually.
Stepwork automates GEM 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 GEM 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 native scim lifecycle.. Additional risks include sso is tier-gated., role changes require manual cleanup., offboarding misses shared workflows.. Stepwork eliminates these risks by automating the entire provisioning workflow.
See how Stepwork provisions users in GEM 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.