GMass does not currently offer SCIM-based user provisioning. Stepwork automates GMass provisioning with 98% accuracy — no API required.
API access without SCIM. Complexity Vector: Access spans keys, campaigns, and Gmail accounts.
GMass does not support SCIM, and relies on Google OAuth per user, so provisioning and team management are manual. This constraint makes introspective automation limited, which is why teams use Stepwork to automate GMass flows with 98% accuracy without needing an API.
GMass supports OIDC sign-on. Stepwork authenticates through your existing identity provider — the same way your employees do.
No. GMass does not currently offer SCIM-based user provisioning, leaving IT teams to manage user lifecycle changes manually.
Stepwork automates GMass 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 GMass 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;. Additional risks include google oauth only per user, manual team onboarding.. Stepwork eliminates these risks by automating the entire provisioning workflow.
See how Stepwork provisions users in GMass 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 and OIDC, mirroring your organization's security posture.