If your child's school issued them a Chromebook, you may have noticed that it behaves differently from the laptop you use at home, and differently again depending on whether your child is on the school network or yours. The behavior is not random. It is the result of deliberate configuration decisions made by whoever manages your district's Google Workspace for Education deployment, and understanding the structure helps make sense of what can and cannot be changed.
What a Chromebook is, technically
A Chromebook is a laptop running ChromeOS, Google's operating system built around the Chrome browser. Unlike Windows or Mac, ChromeOS does not run traditional downloaded software; applications run in the browser or as Chrome extensions and web apps. This architecture is what makes Chromebooks inexpensive to deploy, easy to manage, and relatively resistant to the kind of malware that plagues traditional operating systems. It is also what makes them feel constrained compared to other laptops. From the district's perspective, the constraint is the feature.
How school management works
When a district purchases Chromebooks, it enrolls them in Google Admin Console, a management platform that lets administrators push settings and policies to every device in the fleet simultaneously. Enrollment is the key variable. An enrolled, school-managed Chromebook will behave according to whatever policies the district has configured, regardless of which Wi-Fi network it is connected to. The device's behavior follows the device, not the network.
What administrators can configure is extensive: which websites are blocked, which extensions are permitted or required, whether Google Safe Search is enforced, whether the camera and microphone can be used, whether students can install anything, how long idle sessions stay logged in. Some of these settings apply only when the student is signed in with their school Google account. Others apply to the device regardless of which account is logged in.
At home vs. at school
The distinction matters practically. If your child's school has configured content filtering, those filters travel with the device when they bring it home: the district's policies apply, not just on the school network but on yours as well. Families who expect that home means a different environment are sometimes surprised by this.
The school-managed filters are enforced through the device's management configuration rather than through the home network, which is why a student using their own personal device at home is on different footing than a student using the school Chromebook. The Chromebook is a managed school device that happens to live at your house for the night.
What you can and cannot change
Most of the district-configured policies on a school Chromebook cannot be changed by the student or the family. They are managed at the admin level. What can vary: whether you allow your child to use their personal Google account in a separate profile on the same device (possible on most deployments, though the managed account and personal account stay separate), and whether you add parental controls on your home router separately from what the school has configured.
The Chromebook is a tool the school manages and owns. It is in your home because that is where the student does their homework. The school's administrative relationship to the device does not pause when it crosses your threshold.