The quickest way to get a set of connected robotics kits onto a school network is not to ask "can the robots use the WiFi." It is to hand your IT team a short, precise request they can read once and approve. IT says no to vague asks because vague asks create unknown risk. Give them the exact parameters instead, and most of the friction disappears.

What your IT team actually needs to know

Classroom IoT boards are small, low-power devices. They join WiFi, send tiny messages out to a cloud service, and receive commands back. That is close to how any well-behaved sensor behaves, and it is far less demanding than a laptop trolley. Translate your request into the fields IT plans around:

• Band and security: the boards use 2.4GHz WiFi with WPA2-PSK. They do not connect to 5GHz-only SSIDs, and older WPA or TKIP networks will fail. A standard WPA2 pre-shared key is all they need.
• SSID or VLAN: which network they should join. IT will often prefer a separate device SSID or an isolated VLAN, which is fine, so say you are happy with that.
• MAC allow-list: each board has a stable hardware MAC address, unlike phones, which randomise theirs. Offer the full list so IT can allow-list exactly those devices and nothing else.
• Outbound ports: devices connect outbound only, typically HTTPS on 443 and secure MQTT on 8883. No inbound ports, no port forwarding, nothing exposed to the internet.
• Bandwidth: a live class of boards uses a trivial amount, a few kilobytes per device per minute for status messages. It will not compete with video streaming or online exams.
• Client isolation: if the boards only talk to the cloud, IT can leave client isolation on. Mention it either way so there are no surprises.

The email you can copy and paste

Adapt the bracketed parts and send this to whoever manages the network:

Subject: Network access request, [number] classroom IoT devices

Hi [name], I am running a coding and robotics class in [room] on [days and times]. I would like to connect [number] battery-powered microcontroller boards to the network for the lessons. They behave like simple sensors, and I have the technical details below so you can approve them cleanly.

• Devices: [number] boards, 2.4GHz WiFi, WPA2-PSK only (no 5GHz-only, no WPA1 or TKIP).
• Connections: outbound only, HTTPS 443 and MQTT over TLS 8883. No inbound access required.
• Traffic: a few kilobytes per device per minute.
• Identification: stable hardware MAC addresses, full list attached for allow-listing.
• Placement: happy to sit on a separate device SSID, guest VLAN, or isolated segment if you prefer.

Could you let me know the SSID and key to use, or the best way to get these on the network? I can bring the boards to you to register the MACs. Thank you.

If IT says no, or not yet

Approvals take time, and a term can start before the paperwork clears. None of that has to stop the lesson:

• Run offline first. Students can build and test the same programs in a browser simulator with no network at all. Try the block simulator or the verse simulator, then move to real hardware once the network is sorted.
• Use a dedicated hotspot. A cheap 2.4GHz travel router or a phone hotspot gives you a clean WPA2 network you control, kept off the school LAN entirely. It also survives a load-shedding reset better than a shared network.
• Ask for a guest SSID. Many schools already run an isolated guest network. Devices on it can reach the cloud without touching internal systems, which is often the easiest yes for IT.
• Bring the platform to them. With a managed setup like sheenIoT and the sheenbot infinity board, the connection profile is known and repeatable, so IT reviews it once rather than device by device.

A 60-second check before you send

• Count the devices and note the room, days and times.
• Collect the MAC addresses into one attachment.
• State clearly that traffic is outbound-only and low.
• Offer the isolated-network option up front.
• Give IT a single, specific ask: which SSID and key to use.

Speak the network's language and the request stops looking like a risk and starts looking like a five-minute job. The July break is a good window for IT to process it, so the boards are ready to connect when term three begins.