From "Annotated User" to Locked-Down Devices
How Union City Public Schools, a 1:1 district with 13,000+ active Chromebooks, replaced the Google Admin "annotated user" field and a spreadsheet with a sign-in rule Google enforces on every device
The Challenge
Union City Public Schools is a 1:1 Chromebook district in Hudson County, New Jersey, with more than 13,000 active Chromebooks. Every student gets a device. Every device needs to be tracked, assigned, and maintained.
At that scale, the Google Admin Console stops being a management tool. It has no real concept of device assignment, just a free-text "annotated user" field with no validation and no enforcement. Answering the most basic question in a 1:1 program (who has this Chromebook?) meant digging through sign-in logs and studying usage patterns, device by device. Multiply that by more than 13,000 devices and it becomes a full-time job that never ends.
To compensate, the district stitched together a patchwork of tools:
"Before UserAuthGuard, managing Chromebooks was very manual and time-consuming. Students would sometimes switch devices, lose them, or receive a Chromebook without proper documentation at some schools. To figure out who a device belonged to, we often had to check Google Admin logs and study device usage. This process was prone to errors and required a lot of effort from the team."
The Solution
Union City deployed UserAuthGuard across the entire district. The platform connected directly to their Google Admin Console, giving the IT team a single source of truth for device assignments, replacing the spreadsheets, manual "field user" entries, and extension workarounds.
"After implementing UserAuthGuard, device accountability improved significantly. Chromebooks automatically verify the assigned user, which prevents students from using devices that are not assigned to them. This reduced manual tracking, eliminated a lot of guesswork when investigating issues, and made device management much more efficient for the team."
Before & After
Before UserAuthGuard
- • Devices tracked via Google Admin "field user" + spreadsheets
- • Students switched or lost devices without documentation
- • Investigating ownership meant checking Admin logs manually
- • Bulk changes required Gopher extension
- • Error-prone process requiring significant team effort
- • Several tools with no unified view
After UserAuthGuard
- • Automatic user verification on every Chromebook
- • Students can only use their assigned device
- • Instant device lookup: ownership is clear
- • Built-in bulk operations replace extension workarounds
- • Ownership investigations replaced by a lookup
- • Single platform for assignments, repairs, and tracking
Implementation Impact
Device Accountability
Chromebooks now automatically verify the assigned user. Students can no longer use devices that aren't assigned to them, the single biggest change for the district.
Eliminated Spreadsheet Tracking
No more maintaining separate spreadsheets or manually documenting users in the Google Admin "field user." All assignment data lives in one system, synced with Google Admin.
Faster Issue Resolution
The team no longer digs through Google Admin logs and usage patterns to identify who has a device. Ownership is a lookup. Alex puts the time saved at several hours a week.
Consolidated Tooling
Bulk operations replaced the Gopher extension. A unified platform replaced the need to cross-reference Google Admin, spreadsheets, and Service Desk separately.
The Results
"UserAuthGuard has saved our team several hours each week by eliminating the need to manually investigate device usage and ownership in Google Admin logs."
The win Alex names is time. Ownership investigations used to mean log-digging and spreadsheet cross-referencing across 13,000+ devices. In his words, that is several hours a week the team no longer spends. Ownership is a lookup, not a research project, and the assignment is enforced by Google at the sign-in screen instead of documented by hand.
Alex's Recommendation
"I would recommend UserAuthGuard to any district managing a large fleet of Chromebooks like ours. It adds an extra layer of accountability by ensuring devices are used by the correct assigned user, which simplifies troubleshooting and reduces the time spent tracking down device ownership. For large fleets like ours, the bulk operations also save a significant amount of time and improve overall device management without having to rely on additional extensions like Gopher."
More From Union City
Accountability was chapter one. Here's what it unlocked the following summer:
Managing a large 1:1 program?
Free: every device and every assignment gap, no device cap, no credit card. See how UserAuthGuard handles it before paying to enforce.