Schools and classes
Teachers, students and parents ask; you see which classes and schools want it.
For learning apps: group users by class or school with teacher, student and parent roles. See demand per class and what teachers want next to students.
Set it up
Send the class (or school) as company
Every token carries the group id and name. Pick one level and keep it stable: your database id, never the display name.
Settings → SSO
{ "id": "u_301", "name": "Leo", "company": { "id": "class_4b", "name": "Class 4B · Hillside School", "plan": "School" }, "attributes": { "role": "student" } }Call them classes
The dashboard says Classes (or Schools) everywhere.
Settings → General → Customers
Roles, and nothing more
teacher, student or parent in attributes.role. For students, an id and a first name; no email, photos or birth dates.
In the app or the browser
The widget in the web app, the embed in the mobile app.
TheyAsked('identify', { token });
What you learn
- Classes asking
- Breadth across classes, not one enthusiastic class.
- Teachers vs students
- Segment any insight by role.
- Schools
- Send the school as an attribute on the class to compare schools.
Who it's for
- Learning platforms
- Classes, teachers and students.
- School communication apps
- Parents and staff, grouped by school.
- Clinics and practices
- The same pattern with practitioner and admin roles.