Make AI-supported learning easier to discuss and support.
I’m a teacher · show me how to startLearnVerity’s family app and any future school program stay separate. In the family workflow, a parent invites your verified school email. You accept or decline, then receive a limited dashboard for the learning reports that parent explicitly shares. Optional summary emails require both of you to agree. This gives educators a practical starting point: what the student tried and what help they want next.
Teacher access is not automatic
A student or teacher may request a connection, but the parent decides whether to approve it. Parent approval sends an invitation, not a report. The teacher must accept. The student must permit the check-in for teachers, and the parent previews it before sharing it to that teacher’s dashboard.
The coordinated family release
- Student-suggested teacher email requests
- Short-lived teacher request QR codes
- Parent approval, decline, removal, and contact management
- Teacher acceptance or decline, a limited teacher dashboard, and optional summary emails
- No activity, prompts, screenshots, or family contact details exposed by the request
A separate setup for your school or district
Define your learning goals
Choose the age group, classes and learning questions your program will support. Agree what a useful report should contain.
Set up the district administrator
The enterprise plan includes organization verification, staff roles, school boundaries and district sign-in. Individual family invitations do not create an administrator account.
Agree on records and permissions
Define what teachers, support staff and district leaders may see, how families and students are informed, and when records are deleted.
Start with a supported rollout
Plan roster setup, devices, accessible tutorials and support. Test the full flow with the school before expanding access.
This is the enterprise onboarding design, not a live district provisioning tool. Roster sync, district sign-in and school-wide reporting need implementation and validation with a partner.
Defined educational purpose
Every shared category should answer a specific learning-support need, not general curiosity.
Smallest useful view
Teachers should receive class-related categories and trends, not a family’s device-coverage timeline.
Visible permission
Parents approve the connection and report type. Students can see what is included before sharing starts.
Role-based access
Teachers, counselors, school leaders, and auditors receive different access based on an assigned job need.
Retention and deletion rules
School contracts should state how long records remain and what happens when a student leaves.
Reviewable history
Access and sharing changes should create an audit trail so families and schools can resolve questions.
A district program is the next step.
LearnVerity is preparing the privacy, accessibility, security, support, and outcome evidence needed for a responsible pilot. We do not claim certifications or school features that have not been completed.