How to Make School Chromebooks Safe

Quick Answer

Short answer: Most schools filter which sites pupils may open but nothing cleans the words on the sites that stay open. Compare the three layers below, keep the two you have and add on page text filtering with a forced install by organisational unit. Pupils cannot remove a forced extension.

A classroom set of Chromebooks looks controlled. The Admin console blocks categories, search runs in SafeSearch and the devices reset on logout. Then a pupil opens an allowed video and the comments underneath carry language no teacher would permit in the room. The school filtered places while nobody filtered words.

This guide compares the layers available to schools, recommends which combination fits primary and secondary classrooms and explains deployment through forced installation. It is written for teachers and IT administrators rather than parents, so it covers organisational rollout instead of single device setup.

Compare the three layers

No single layer covers a classroom. Each one owns a different part of the problem, and the gaps only close when the layers combine. The table compares them on what each blocks, what each misses and what each costs a school.

The judgement is straightforward. A school with the first two layers still shows pupils unfiltered words daily, because comments, forums and search snippets live on allowed domains. The third layer is the cheapest to add and it covers precisely the gap the other two leave open. Nothing here replaces supervision, but supervision stops working at thirty screens per teacher without tooling.

Deploy with forced installation

Google Workspace for Education supports forced installation of Chrome extensions by organisational unit. Add PureWord to the forced list for the pupil units and it installs on every managed Chromebook automatically. Pupils cannot disable or remove a forced extension, which removes the failure mode where a filter works until a curious pupil switches it off.

Apply different organisational units for primary and secondary years if your console is organised that way. The extension itself runs with no account and no analytics, so there is nothing for pupils to sign into and no browsing data leaves the device. See the privacy policy for the full statement, which matters for school data reviews.

Word lists for the classroom

Primary classrooms need the broadest list. Use the full standard list plus playground insults such as stupid, ugly and shut up, because young pupils repeat screen language in the playground and the complaint lands on the teacher. Add game specific taunts for the titles pupils actually play, since allowed game sites generate most classroom incidents.

Secondary classrooms need the standard list plus current slang, configured with the pastoral team rather than imposed on it. Restraint with mild language matters at this age, because a filter that masks everyday words gets disabled mentally even where it cannot be disabled technically. Pupils who accept the list report problems instead of routing around them.

What the layers still miss

Spoken audio in videos passes all three layers, since none of them transcribes sound. Phones on mobile data bypass school DNS and run apps outside Chrome, so the classroom policy and the phone policy remain separate documents. Stating this boundary helps set expectations with parents: the school owns the Chromebook while the household owns the phone. Each needs its own controls.

FAQ

Can I force install an extension on school Chromebooks? Yes. Google Workspace for Education supports forced installation of Chrome extensions by organisational unit, so pupils cannot remove them.

Does a text filter replace the Admin console web filter? No. The Admin console blocks places and a text filter cleans words. Schools need both layers because each misses what the other catches.

Which word list suits a primary classroom? Use the full standard list plus playground insults such as stupid, ugly and shut up. Young pupils repeat on screen language at school and at home.

Is pupil browsing data collected? Not by PureWord. Everything runs on the device with no account and no analytics. See the privacy policy for details.

Summary

Classroom Chromebooks are usually filtered by place and unfiltered by word. The comparison shows that Admin console and DNS layers cannot clean language on allowed sites, which is where pupils actually meet it. A forced text filtering extension closes that gap in minutes, with lists tuned by key stage and no pupil data collected.

Related Articles