Skip to main content

Southeast Delco School District

How a Pennsylvania district solved Chromebook accountability with true 1:1 device assignments

6,943Chromebooks
1:1Device Assignments
RepairsIn the Same Record
ClassroomTeachers Use It Too

The Challenge

Southeast Delco School District, in Delaware County, Pennsylvania, runs a fleet of 6,943 Chromebooks. The district had invested in third-party tools for ticketing and content filtering, but there was a critical gap: no system enforced true 1:1 device accountability.

Students could pick up any Chromebook and use it freely. There was no reliable way to know which student had which device at any given time. When a device was damaged or went missing, there was no accountability trail. The IT team spent hours trying to trace devices manually, and stolen Chromebooks were essentially untraceable.

No Device Accountability
No system enforced which student was assigned to which Chromebook. Devices had no clear owner.
Rampant Device Swapping
Students used any available Chromebook. Damage couldn't be traced to the responsible student.
Stolen Devices Untraceable
When Chromebooks went missing, there was no assignment record to identify who last had the device.
Multiple Disconnected Tools
Their existing ticketing, filtering, and Google Admin each handled a piece, but none provided unified device-to-student tracking.
"Kids were using any Chromebook they wanted. There was no accountability. When something broke or went missing, we had no idea who was responsible."
Matt Miller, Technology Coordinator, Southeast Delco School District

The Solution

Southeast Delco deployed UserAuthGuard to close the accountability gap. By integrating directly with Google Admin Console, every Chromebook was linked to a specific student, creating true 1:1 device assignments that the existing toolset couldn't provide.

With UserAuthGuard, the IT team gained a single platform for device assignments, repair and support tracking, and full device inventory visibility. For the first time, when a device was damaged or reported missing, they could immediately identify the assigned student and see the complete activity history.

Device Assignments
True 1:1 student-to-device assignments with complete audit trail and accountability
Repair & Support Tracking
Structured repair workflows replacing scattered tracking across multiple tools
Device Inventory Visibility
Full inventory view synced with Google Admin: every device accounted for in one place
Activity & History Visibility
Complete device history showing assignments, repairs, and status changes over time

Implementation Impact

1

Google Admin Integration

Connected to Google Workspace and synced all device records automatically. Device details, organizational units, and status pulled directly from Google Admin Console.

2

1:1 Device Assignments

Established true 1:1 student-to-device assignments across the district. Every Chromebook linked to a specific student with a full accountability trail.

3

Repair & Support Configuration

Set up repair tracking and support workflows, giving technicians a single view of device issues tied directly to assigned students and device history.

Before & After

Before UserAuthGuard

  • • Students used any Chromebook freely
  • • No way to trace damage to a student
  • • Stolen devices were untraceable
  • • Multiple tools with no unified view
  • • Hours spent manually tracing devices
  • • No accountability for device condition

After UserAuthGuard

  • • True 1:1 device-to-student assignments
  • • Instant identification of assigned student
  • • Complete device history and audit trail
  • • One platform for assignments and repairs
  • • Device history, repairs and assignment in one record
  • • Full accountability for every Chromebook

From the IT Closet to the Classroom

Southeast Delco bought UserAuthGuard to solve a device accountability problem. What happened next was not in the plan: the product moved out of the IT office and into classrooms.

The district turned on classroom monitoring district-wide, replacing a separate tool teachers had been using. Teachers now sign in to UserAuthGuard to watch screens during a lesson, pause a class, reset a student password without filing a ticket, and send a message to every Chromebook in their room.

That changed what the product is for. Device accountability is an IT outcome. A teacher who can see that a student is on a game instead of the assessment is an instructional one.

What a teacher report changes

In October a third-grade teacher at Harris School reported that two students were working on their Chromebooks but her monitor said they were not reachable. One of them, she noticed, was playing a game.

The cause turned out to be worth knowing. The student had saved game files into his Google Drive and was opening them directly on the Chromebook. Chrome does not permit any extension to see that kind of page, so there was genuinely nothing to show her. The monitor was telling the truth in a way that sounded like a fault.

Two days later the classroom view was changed to say which kind of unreachable it is: a Chromebook that is shut, or one that is switched on and in use with something we cannot display. The second is the one worth walking across the room for.

That is the shape of the relationship. A teacher reports something, the cause gets traced properly rather than dismissed, and the product changes. Staff support requests are raised and resolved inside UserAuthGuard too, so the ticket, the device and the student sit in one record.

The Results

After deploying UserAuthGuard district-wide, every Chromebook at Southeast Delco is assigned to one student, and Google enforces that assignment at the sign-in screen.

1:1Every Chromebook to one student
GoogleEnforces it at the sign-in screen
TracedDamage and loss to a record
One placeAssignments, repairs, history

The biggest impact was accountability. For the first time, every Chromebook in the district was assigned to a specific student. When a device was damaged or went missing, the IT team could identify who was responsible instead of guessing.

Technicians no longer track down device assignments by cross-referencing systems. Device history, repair status and the student assignment are one record, so the information they need is where the ticket is.

By consolidating device tracking into a single platform that integrated directly with Google Admin, the district eliminated the gaps between their existing tools and finally had complete visibility into their Chromebook fleet.

Matt's Recommendation

"I would absolutely recommend UserAuthGuard to other districts. If you need to keep track of your devices and you're using Google Admin, it's a no-brainer."
Matt Miller, Technology Coordinator, Southeast Delco School District

Need Chromebook accountability?

Free: every device and every assignment gap, no device cap, no credit card. Pay only when you're ready to enforce.