Multi-School Dashboards
One district organization in which every role sees the buildings it is responsible for. District staff see everything; technicians, principals and secretaries see their schools; a curriculum role sees district totals. Per-school reports come from the same records.
What it does
A district is one Google Workspace and many buildings, and the people who need to see device data are mostly building people: the principal who wants to know how many Chromebooks are out at her school, the technician who covers two of them, the secretary who issues loaners. Giving all of them the district console is a privacy problem; giving them nothing means they call IT.
UserAuthGuard maps your schools from the Google OU structure and, where you have a roster sync, from your SIS, so every device and student belongs to a building. Roles are then scoped by school. District administrators and superintendents see the whole district. Technicians are assigned to schools and see those schools’ devices and tickets. Principals and assistant principals get a lean portal for their building: device and assignment totals, usage, ticket counts, the loaner report. Secretaries handle loaners and lookups for their building. A curriculum role sees district-wide usage totals and nothing about individual students. Teachers see their classes.
The same records produce the district view and the per-school view. School reports break assignment coverage, usage, tickets and repairs out by building, and the compliance report can be scoped to one school. Devices move between schools when their OU changes, taking their history with them. Where a district also runs Windows, iPad or Mac devices under Microsoft Intune, those appear in the same inventory, matched to the staff member or student they are assigned to.
- ✓ Schools from your OUs and rosterBuildings are derived from the Google OU tree and the SIS roster sync, so every device and student has a school without a second directory.
- ✓ Roles scoped by buildingTechnician, principal, assistant principal, secretary and device-return roles each see their assigned schools only.
- ✓ A principal portalTotals, usage, tickets and loaners for the building, with no IT operational pages and no student screens.
- ✓ District roles for leadershipSuperintendent and curriculum roles see district totals; the curriculum role never sees an individual student.
- ✓ Per-school reportsCoverage, usage, tickets and repairs by building, and the compliance report scoped to a school.
- ✓ Non-Chrome devices in the same inventoryWindows, iPad and Mac devices from Microsoft Intune, matched to their assigned user.
Requires
- The Enterprise Plus plan.
- An OU structure or roster sync that identifies buildings. Most districts already have one; UserAuthGuard maps it.
- Microsoft 365 with Intune, connected to UserAuthGuard, for non-Chrome devices. Optional.
Does not
- Create separate tenants per school. It is one district organization with scoped views, which is what makes district totals possible.
- Give principals screens or per-student browsing. Leadership roles see totals and usage.
- Compare districts. Each organization sees only its own data.
Where it fits
The principal’s question
How many of my students have a device, how many devices are out as loaners, and how many tickets are open for my building. Answered in the principal portal without a call to IT.
Two buildings, one technician
A tech assigned to the middle school and the elementary sees those two queues and fleets, and nothing from the high school.
Board night
District totals and the per-school breakdown of coverage, usage and repairs, exported to Google Sheets from the same records the buildings see.
Frequently asked questions
How does UserAuthGuard know which school a device or student belongs to?
From the Google OU structure, which most districts already organize by building, and from the SIS roster sync where you have one. You confirm the mapping once; after that new devices and students land in the right school automatically.
Can building staff manage their own building without seeing others?
Yes. Technician, principal, assistant principal, secretary and device-return roles are assigned to specific schools and see only those. District administrators see everything.
How do devices move between schools?
Move the device’s OU, singly or in bulk, and its school follows. Its assignment history, repairs and tickets stay on the record.
Can different schools have different rules?
Yes. Chromebook rules and filter policies target OUs, schools or grades, so an elementary building can be stricter than the high school within one organization.
One district, every building in view
Multi-School Dashboards are part of the Enterprise Plus plan, quoted per district. Book a walkthrough, or start free: the gap report lists every device with no owner and every student with no device.