Whether a classroom PC is online, which machine is holding a class, and whether it needs to re-read its configuration — that used to mean walking to each machine. Control moves it into a web console: once a device is paired, you can see it and act on it from the browser.
Control does not pop up notice cards, does not push images, and cannot lock, shut down or restart a client remotely. It never touches homework content either.
Control runs on the sectl.cn platform; the console lives at sectl.cn/dashboard/control.
Pairing, in three steps
1. Generate a pairing code in the console
Open the console, pick the location, grade and class, and generate a pairing code. A code is single-use: it is spent when it is used, or expires. Generate a fresh one whenever you need it.
2. Enter the location ID and pairing code in the client
On the classroom PC, open Settings → Control in Corkboard:
- turn the master switch on (it is off by default, so nothing dials out on its own);
- enter the location ID and pairing code from the console;
- press Pair. The client dials out and the device shows as online in the console.
The location ID says which machine this is; the pairing code proves this pairing was authorised. Both have to match — one missing, or a code issued for another class, and the device does not come in.
3. Work from the console
Select devices by grade or class in the console. What you can do is limited to: see whether a device is online, occupy a class with a device, release that class, and send a configuration reload.
What it can and cannot do
| Capability | What it does | Arguments |
|---|---|---|
| Online status | The console shows the device as online or offline | none (the device reports it) |
| Occupy class | Assigns the class to this device | class |
| Release class | Frees the class the device is holding | none |
| Reload configuration | Makes the device re-read its configuration | none |
There are no refresh-notice, push-image, lock-screen or restart commands, and no channel for editing homework data remotely.
Only one device can hold a class at a time: when another device occupies it, the previous one is told it has been taken over and stops holding the class.
Actions from the console carry an expiry (two minutes by default, one hour at most). A device that is online acts immediately; anything already expired is not replayed.
Privacy boundaries
- No user data is read — note contents, handwriting, subjects and assignment lists never leave the device.
- No inbound port — the device dials out to the control platform. No public IP is needed and nothing listens on the classroom network.
- No remote editing of homework — control can only see online status, occupy or release a class, and reload configuration.
- Credentials stay local — pairing credentials are stored in a separate local file encrypted with AES-GCM and are not part of settings sync.
- Unpair at any time — revoking a device in the console clears its credentials locally and stops it reconnecting.
FAQ
Do classroom PCs need a public IP or port forwarding?
No. Devices only dial out; the classroom network just needs outbound internet access.
What happens when the network drops?
The client reconnects on its own with progressive backoff and carries on. Actions taken from the console while it was offline are not replayed once they expire — repeat them if they still matter.
Can the school see our class's homework?
No. Control can only see online status, occupy or release a class, and reload configuration. Homework data stays on the classroom machine.
Can a pairing code be reused?
No. A code is spent when it is used or when it expires. Pairing another machine means generating another code.
What does the teacher need installed?
Nothing — the console is a web page. The classroom PC does need Corkboard running and paired before it connects.