Skip to content
Studeia Docs

SSO and SCIM for institutions: single sign-on and auto-provisioning

SSO (SAML/OIDC) gives single sign-on with the institutional account; SCIM 2.0 creates and deactivates users automatically. See why every institution at scale needs both.

2026-06-22 8 min
Resposta curta

SSO (SAML 2.0 or OIDC) gives single sign-on with the institutional account, no new password; SCIM 2.0 provisions users automatically — creating the account when someone joins the institution and deactivating it when they leave, syncing with the directory. At scale you need both: SSO improves security and cuts password support; SCIM eliminates manual account management and the risk of ex-students with active access. Mapped to courses, groups also drive enrollment.

Managing hundreds or thousands of accounts manually is costly and risky. SSO and SCIM solve this: the first unifies login, the second automates user creation and deactivation. Here's why they're requirements for any institutional LMS at scale.

Quick answer

  • SSO (SAML/OIDC) = single sign-on with the institutional account, no new password
  • SCIM 2.0 = automatic provisioning (creates/deactivates users and classes)
  • Integrate with Azure AD, Okta, Google Workspace, Shibboleth, ADFS
  • By mapping groups → courses, SCIM also enrolls automatically
  • Without them, account management at scale becomes a bottleneck and a risk

SSO: one login for everything

With SSO, students and teachers log in to the LMS with the same account they use across the institution. Benefits:

  • Security: password policies and MFA centralized in the identity provider.
  • Less support: fewer "forgot password" tickets.
  • Simple onboarding: the user already has an account.

SCIM: accounts on autopilot

SCIM 2.0 syncs the institutional directory with the LMS:

  • Joined the institution → account created in the LMS.
  • Left → account deactivated (no former student with active access).
  • Changed class/area → automatic update.

In Studeia, changes to SCIM group membership trigger enrollment sync per the group-to-course mapping — the student joins the right group and is enrolled in the course automatically.

SSO + SCIM together

Without SSO/SCIMWith SSO/SCIM
Separate passwordsSingle institutional login
Accounts created by handAutomatic provisioning
Former students with accessAutomatic deactivation
Manual enrollmentGroup-based enrollment

IT checklist

  1. Supports SAML 2.0 and OIDC?
  2. Has SCIM 2.0 for provisioning?
  3. Integrates with Azure AD/Okta/Google?
  4. Does group → course mapping (automatic enrollment)?
  5. Deactivates accounts automatically on departure?

FAQ

What are SSO and SCIM? SSO = single institutional login; SCIM = automatic user provisioning.

Why need SCIM? To eliminate manual management and the risk of former students with active access.

Does it work with Azure AD/Okta/Google? Yes, via SAML 2.0 or OIDC.

Does SCIM enroll automatically? Yes, by mapping directory groups to courses/classes.


See Studeia's SSO Enterprise + SCIM and the Microsoft 365 integration.

FAQ

What are SSO and SCIM in an LMS?

SSO (Single Sign-On, via SAML 2.0 or OIDC) lets students and teachers log in to the LMS with the institutional account, with no new password. SCIM 2.0 is the standard that provisions users automatically: when someone joins or leaves the institution, the account is created or deactivated in the LMS without manual work.

Why does a school or university need SCIM?

At scale, managing accounts manually becomes a bottleneck and a security risk (former students with active access). SCIM syncs users and classes with the institutional directory (Azure AD, Okta, Google) automatically, ensuring only those who should have access do, at the right time.

Does SSO work with Azure AD, Okta and Google Workspace?

Yes. SSO via SAML 2.0 or OIDC integrates with major identity providers (Azure AD/Entra ID, Okta, Google Workspace, Shibboleth, ADFS). Login becomes the same as the institutional account, which improves security and reduces password support.

Does SCIM enroll students in courses automatically?

It can. By mapping directory groups to courses/classes, a student joining a group triggers enrollment in the corresponding course, and leaving cancels it. In Studeia, changes to SCIM group membership sync enrollments automatically per the group-to-course mapping.

Veja tambem

SSO and SCIM for institutions: single sign-on and auto-provisioning