Clever is the identity provider most North American K-12 districts use to broker single sign-on across their edtech stack. If your app is deployed into a school district, Clever SSO lets students and staff sign in with the same account they use for everything else, with no new passwords and no district IT ticket per user.
Education is one of the largest verticals in professional AV, and district deployments come with identity requirements that corporate deployments do not:
- Districts generally will not allow student accounts to be created in a third-party system directly.
- Student data handling is governed by district policy and, in the US, by FERPA and often state-level student privacy law.
- IT wants one place to revoke access when a student transfers or a staff member leaves.
Clever solves all three by keeping the district as the source of truth.
- The district's Clever administrator adds your app from the Clever library or via a district-specific request.
- The district approves the requested scopes and selects which schools or sections have access.
- Configure the Clever connection in your app's Access settings.
- Users then sign in through the Clever portal or via the Clever login button on your app.
Because provisioning is district-driven, you cannot self-serve this end to end. Budget time for the district's approval cycle, which is often measured in weeks rather than days.
- Rostered identity. The app knows whether a user is a student, teacher, or staff member.
- Automatic deprovisioning when the district removes a user.
- No password management on your side.
- Scope the agent tightly for student-facing use. A room-support agent that students can reach should not be able to reach ticketing, cost data, or staff-only knowledge sources. Use Access Control alongside Clever, not instead of it.
- Confirm the district's AI policy before you deploy. Many districts now have explicit policy on AI tools touching student accounts, and it is separate from their general edtech approval.
- Non-US districts. Clever is primarily US K-12. Canadian districts more often use Entra ID or Google Workspace for Education, in which case use standard OAuth or Bring Your Own Auth instead.
*AVCodex · Your AV expertise. Amplified by AI.*