20-minute walkthrough

See a Chromebook refuse the wrong student

A live UserAuthGuard account on a screen share, not slides. UserAuthGuard assigns each Chromebook to one student and has Google Workspace enforce it at the sign-in screen. Twenty minutes is enough to see how, and to decide whether it fits your district.

What the 20 minutes cover

  • The sign-in screen

    Each device gets its own organizational unit carrying a sign-in restriction that names the allowed student. Google refuses anyone else before a session starts. We show how that is set up and what it looks like on the device.

  • Your fleet as it actually is

    Every device, user and OU read from Google Workspace, and the assignment gaps: devices no student is accountable for. This part is free, with no device cap.

  • Spares, loaners, lost and stolen

    Each state a device can be in, how a tech moves it between them, and what each state does at the sign-in screen.

  • Your questions

    Pricing, what connecting your Workspace involves, how it sits beside your help desk and SIS, and whether it fits how your tech team already works.

Good to know

  • You talk to Stefan Verleysen, the founder, who built the product. Not a sales team.
  • Nothing to install or prepare. Bring the questions your techs ask you.
  • We confirm by email with a calendar invite and a video link.
  • No contract, no credit card, no trial clock. You can also see your own fleet free before or after.

Running in production at:

  • Union City Public Schools Hudson County, New Jersey, 13,000+ active Chromebooks Case study
  • Southeast Delco School District Delaware County, Pennsylvania, 6,943 Chromebooks Case study

Request your walkthrough

Four fields, and a time preference if you have one. We reply by email with a calendar invite.

That date is a weekend. We will suggest the nearest weekday when we confirm.

No pressure and no spam. Prefer email? Write to stef@asan.digital.