EdTech and schools
Schools come in districts, with rosters that change every term and students who are minors. LumoAuth gives each district or school its own organization, syncs rosters over SCIM, gates sign-up with parental consent, and models classes and co-teachers as relationships.
Rosters change weekly and students cannot be asked to manage passwords
Manual account creation per term does not scale. Younger students need consent gates and simple sign-in.
How LumoAuth solves it
District-level tenancy
An organization per district or school with its own identity provider and branding. Docs
Roster sync
SCIM from the student information system or the district's identity provider; groups become classes. Docs
Parental consent
Age-gated sign-up with verifiable parental consent records. Docs
Teacher, student, parent roles
Roles per organization, relationships for enrollments and co-teachers. Docs
Simple sign-in
Google and Microsoft sign-in for schools that use them, passkeys and magic links elsewhere. Docs
LMS integration
Standard OpenID Connect for learning tools. Docs
Setting it up
Create an organization per district
Connect SCIM for rosters
Turn on the parental consent gate
Standards involved
Plain names on the left, the specification on the right. The full map is in the standards reference.
- Provisioning
- SCIM 2.0
- Sign-in
- OpenID Connect, SAML 2.0
- Consent
- GDPR Article 8, COPPA
Which plan you need
Organizations and inbound SCIM are on every plan; the number of organizations grows with the plan. Relationship-based access is an add-on.
Documentation
Ship passwordless sign-in this week. Put guardrails on your agents today.
The Developer plan is free for 10,000 monthly users and ten agents, with no card. Everything speaks open standards, so moving in or out is a config change.