Shared Classroom Tablets: Setup Guide for Small Schools

Shared classroom tablets have one requirement above all others: every device should be identical at the start of every lesson. Not mostly identical. Identical. A trolley where three tablets behave differently is a trolley that wastes the first ten minutes of the lesson, and it is the single most common complaint teachers have about school devices.

Everything else, the app control and the restrictions, follows from getting that right.

Decide what the tablets are for

The configuration depends on which of two jobs the devices do, and schools often have both.

Single-purpose devices. A set of tablets used for one thing: a reading app, an assessment tool, a language programme. These want kiosk mode, locked to the one app. Simplest to run and hardest to break.

General learning devices. Tablets used across subjects with a handful of approved apps and a browser. These want a fully managed configuration with a tight app catalogue rather than kiosk.

Be honest about which you have. A “general” tablet with twenty apps installed because various teachers asked is the configuration that generates support requests.

The baseline configuration

One approved catalogue, no store browsing. Students see only the apps you approved. Not a blocklist, a catalogue. Nothing else exists to install. Our post on controlling app installs explains why this holds up better than blocking things one at a time.

No adding accounts. Students should not be able to sign personal Google accounts into a school device. This is a single policy setting and it prevents a category of problems at once.

Camera decided deliberately. Many lessons need it, and safeguarding may say otherwise. Decide per device group rather than leaving it to chance, and write down which way you went and why.

Storage encryption on. Standard on modern Android; confirm it in the policy.

No factory reset by the user. Students should not be able to wipe a device to escape its configuration. On a properly enrolled company-owned device a reset also keeps the tablet enrolled in your organisation, so this is belt and braces.

Screen lock appropriate to the setting. A shared trolley tablet handed between classes usually wants a simple lock or none at all during the school day, with the physical security handled by the trolley. A device that goes home with a student needs a real one.

Making every tablet identical

This is the part that determines whether teachers trust the trolley.

Put every tablet in the same group with the same policy and the same required apps. Required apps install automatically, so a replacement device configured this morning matches the rest by lunchtime.

Give devices predictable names. Trolley A 01 through 24, matching a physical label on the back. When a teacher says number 14 is not working, you know which one that is without a serial number lookup.

Check the fleet weekly rather than waiting for complaints. A device that has not checked in for a fortnight is either flat in a cupboard or gone, and either way you want to know before the term ends.

The end-of-lesson reset problem

Android does not clear a shared device between users by itself, and this is the honest limitation to plan around.

If your learning apps keep a student signed in, the next student inherits that session. Some educational apps handle this with their own sign-out; some do not. Test it with an actual app and an actual student account before you build a routine around an assumption.

For single-purpose kiosk devices, choosing an app that returns to a start screen on idle solves it. For general devices, a short screen timeout plus a teacher-led sign-out routine is usually the practical answer.

Do not promise staff that the tablets wipe themselves between lessons. They do not, and discovering that during a lesson is worse than knowing in advance.

Devices that go home

If tablets leave the building, three things change.

A real screen lock becomes necessary. Lost mode matters: configure the lock screen message with the school’s number in advance, because you will need it. And the loan agreement with the family should say plainly that the device is school property, is managed, and will be wiped when returned.

Be clear with families about what the school can and cannot see. On a NounDesk-managed device that is: installed apps, compliance state, and location only while the device is reported lost, with the lock screen saying so. Not messages, not browsing history. Saying that up front prevents a much harder conversation later, and our note on explaining device management works just as well for parents as for staff.

What to do this week

1. Pick three tablets from the same trolley and compare them. Same apps? Same settings? Whatever differs is your actual problem.
2. Label the devices physically and match the names in your console. This one change removes most support confusion.
3. Test what a second student sees after a first one has used a learning app. Whatever you find determines your between-lesson routine.

FAQ

Can students get around the restrictions?

Not on a properly enrolled company-owned device. Management is applied by Android during setup, there is no app to uninstall, and a factory reset keeps the device enrolled in your organisation.

Can we filter web content?

Device management controls which apps exist, including whether a browser is available at all. Content filtering itself is usually handled by your network or by a dedicated filtering app, and for many small schools removing the browser from single-purpose devices is simpler than filtering it.

Do we need a tablet each, or is a trolley fine?

Trolleys work well for single-purpose use. They are harder for anything where students need to keep work in progress, because of the between-lesson session problem above.

What about tablets bought at different times?

Fine, as long as every device runs Android 8 or newer and supports Android Enterprise. Put them in the same group and they will be configured identically regardless of age or brand.

Does it cost per device?

Yes, device management is priced per device. NounDesk is a dollar fifty per device per month flat, so a trolley of twenty-four is thirty-six dollars a month with everything included.

A trolley where every tablet behaves the same is worth more to teaching than any individual feature. Configure the group, label the hardware, and check it weekly.

See the schools and training setup, or start a free trial.