Gitlab University does not currently offer SCIM-based user provisioning. Stepwork automates Gitlab University provisioning with 98% accuracy — no API required.
GitLab University does not document native SCIM provisioning and relies on SAML SSO under contracted training programs. Complexity Vector: Without SCIM and with SSO gated, learner enrollment and removal depend on manual UI actions that drift from HR events.
Avoid upgrading training contracts just to manage access. Stepwork automates enrollment and cleanup workflows…which is why teams use Stepwork to automate GitLab University flows with 98% accuracy without needing an API.
Gitlab University supports SAML sign-on. Stepwork authenticates through your existing identity provider — the same way your employees do.
No. Gitlab University does not currently offer SCIM-based user provisioning, leaving IT teams to manage user lifecycle changes manually.
Stepwork automates Gitlab University 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 Gitlab University 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 Gitlab University with 98% accuracy — in a 15-minute demo.
Book a DemoThe primary risk is no scim lifecycle for learners.. Additional risks include sso is contract-gated., course access lingers., manual enrollment cleanup.. 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 via SAML, mirroring your organization's security posture.