Institution-scoped membership
The app models school workspaces and memberships so access is tied to an institution and verified enrollment, rather than a learner identity alone. Administrative roles are distinct from educator and learner access. Exact onboarding and account provisioning are controlled by the application workflow.
A concrete operations example
A school administrator preparing a small pilot can review the institution workspace, manage verified learner access and check licensed versus active learners and current usage summaries before planning the next cohort. That can reduce spreadsheet hand-offs and make access questions easier to resolve; the amount of time saved must be measured in the school’s own rollout.
Usage summaries, not student-performance analytics
The implemented institution summary is a commercial/usage view: licensed and active learner counts, shared wallet balance, voice and audiovisual usage, and monthly seat-fee summaries for authorized roles. It is not a dashboard of grades, predicted outcomes, attendance or learning progress.
An adoption conversation, not a promised integration
Before rollout, a school should clarify identity source, enrollment approval, data responsibilities, support ownership and how usage is monitored. Integration with a school information system or automated timetable workflows is not claimed here.