Skip to content
plugboard.appRequest a demo

Self-service portals

Self-service portals

Six surfaces for students, staff and parents. None need a staff account. All of them carry your branding and respect the light or dark theme.

PageURLFor
Service desk kiosk and student portal/portalStudents and staff: report a problem, book repairs, track them, get help, buy items
Repair tracking/track/<token>Anyone with the link from a repair email
Induction kiosk/inductStudents collecting a new device
Parent portal/parentParents
Help centre/helpEveryone
Public status page/statusEveryone, if enabled

Much of what arrives at a school ICT desk is questions about work: is it ready, where is it, what do I do, is the Wi-Fi down. Each of these surfaces removes a category of that traffic:

SurfaceRemoves
Kiosk“I need to book a repair” and “can you reset my password”
Tracking“Is it ready yet”
Induction kiosk“Am I on the list”
Parent portal“What has my child had done”
Help centreThe ten questions you answer every week
Status page“Is the Wi-Fi down for everyone”

/portal is the same page whether it runs on a kiosk at the counter or a student opens it on their own device. It greets them by name and asks What’s wrong?, with My device is broken, Locked out or forgot a password, Find an answer and Buy something beside it as the school offers them. Your device shows their device, any loan device they hold and the repair in progress with its stages and Repair details, and My requests lists what they have asked the desk for.

Each request says where it stands in plain words: With the IT desk, Being worked on, Waiting for your reply, Waiting on a supplier or Done. Only Waiting for your reply asks them to do something. Waiting on a supplier means the desk is waiting on a vendor, a carrier or a warranty provider. The parent portal uses the same words, naming the child where a reply is theirs to give.

Book a repair asks which device, what is wrong with it in plain words, what happened and, where the school lends devices, whether they need a loan device. Where the school asks for one, it also offers Add a photo of the damage, saying what the photo is for before the camera opens. The photo is kept with the repair for desk staff who can see it; families never see it. See booking a repair.

A tablet on a stand at the service desk running the kiosk in full screen, with a card reader.

A QR code on the counter and on the ICT noticeboard, pointing at /portal.

A link from your intranet, on the page students already open.

In the automatic reply of your ICT mailbox, pointing at the help centre.

These pages show a person’s own records, so who is looking matters.

Card tap is the primary identification. Tapping a card proves possession of the card, which is what a counter check verifies too.

Username entry proves nothing on its own, so it is refused by default in production. A kiosk somewhere physically supervised can opt in with PORTAL_USERNAME_ENTRY=1.

SSO is the right answer for the parent portal, and available for the student one. See single sign-on.

Sessions are short. By default a registered kiosk ends a session after 90 seconds without interaction and after five minutes at most, and pressing Finish ends it immediately, so the next person never sees the last person’s data. See kiosk timers for the settings.

A session belongs to one portal. Signing in to the parent portal gives you a parent portal session and nothing else; the student portal is the same. A parent who also has a student account signs in to each separately.

SurfaceNeeds
Kioskportal.client
Trackingmodule.repairs
Induction kioskmodule.inductions
Parent portalportal.parent
Help centreNothing, but it is empty without module.knowledgeBase
Status pagemodule.statusPage and module.monitors