Skip to content
plugboard.appRequest a demo

Self-service portals

The service desk kiosk

/portal. Needs portal.client.

A self-service kiosk where somebody identifies themselves and then chooses what they need. Put it on a tablet at the service desk with a card reader.

A kiosk is a device you reserve, not a browser you point at a URL. That is what lets you name a counter, say which campus it stands on, decide what that particular device offers, and revoke one iPad without un-enrolling the library.

Kiosks live under Settings, Kiosks. The page has four sections, one under the other: Devices, Enrolment tokens, Kiosk look and Shared key, with Reserve a device and Kiosk status in its header. Device actions apply at once; the kiosk look waits for Save kiosk look.

There are two ways to make a device a kiosk:

  • A one-time setup code, typed or scanned at the device. Works for any tablet or browser.
  • An enrolment token in your MDM, for iPads and Android tablets you manage. Nobody touches the device. See enrolling through your MDM.

Two things, and they happen on two screens on purpose. A technician holds the tablet in one hand and their laptop in the other, and typing a staff password into a counter iPad is the exact shape of a phishing screen.

On your own machine: Settings, Kiosks, then Reserve a device. Give it a Name (what the office calls it, like Front office iPad) and, if you like, Where it lives. Then choose Reserve and show code.

You get a six-digit code. It is single use and good for ten minutes.

On the tablet: go to /portal/kiosk and type the code, or scan the QR code shown beside it with the tablet’s camera, which opens the setup page with the code filled in. The kiosk list shows when the device has claimed it.

The address is printed beside the code in Settings, so you read both off one screen. The device is then enrolled and holds its own secret; nothing about a staff account is ever left on it.

That page also answers “what is this device?”. It asks the server rather than trusting what the browser is holding, so a tablet still carrying a secret for a kiosk you have since revoked is told so, in front of the person who can fix it. It also offers Use this device as an ordinary browser for a tablet that should stop being a kiosk.

There is deliberately no “unlink this device” button. Forgetting the secret locally would leave the record looking live in Settings with nothing answering to it. Pointing a device somewhere else takes a fresh code: choose New setup code from the kiosk’s More actions menu in Settings, which is also what un-enrols whatever held the old one.

Open Settings from a kiosk’s More actions menu.

SettingWhat it does
Name and Where it livesShown under the school’s name on the kiosk
CampusWhich site it stands on, or Any campus
Only people from this campusRefuses anyone from another campus. See below
Card tapStudents and staff hold their card to the reader. On by default
Username and passwordThe sign-in form, for anyone without a card. On by default
Where the card reader isLeft, right or below the screen. The sign-in screen points to it. Shown when card tap is on
Card format for the tablet’s own readerHow a tablet’s built-in NFC reader turns a card into a number, to match your records. Plug-in readers send what they are set to type
Visitor sign-in on this kioskVisitors and contractors sign in and out here too. Off by default. See visitor sign-in
Sign out when nobody is using itThe idle timeout. After 90 seconds by default, with a twenty-second warning first
End every session afterThe session ceiling, however busy someone is. 5 minutes by default, with a warning a minute before
This kiosk’s own lookA headline, a line under it and a background for this kiosk alone. Leave empty to use the school’s kiosk look

The kiosk picks changes up when it next checks in, within a minute.

Settings, Kiosks, Devices lists what is enrolled, where, and when each was last seen. Revoke from the kiosk’s More actions menu ends its live session as well as refusing the next, so an iPad that walks off the counter stops working immediately and every other counter keeps going. The device has to be set up again with a fresh code.

A kiosk the server refuses shows “This kiosk is switched off” and stays that way until somebody sets it up again.

A kiosk keeps its secret in the browser’s own storage, so clearing the browser’s data, resetting the tablet, or re-imaging it through your MDM takes the secret with it. The device still opens the portal, but as an ordinary browser, which means the password form comes back, the campus restriction stops applying and the short session limit reverts to the general one. It looks fine from the front.

The audit log records when this happens: a device presenting a kiosk credential that matches no kiosk writes a line naming the address it came from. If you see those, the device at that address needs a fresh setup code. Also check Settings, Kiosks: a kiosk shown as Offline is the same story from the other side.

A shared key enrols kiosks with one key for the whole school, carried to the device as ?kiosk=…. It works for a school that has not reserved a device.

Claiming your first device switches the shared key off for the whole school, and any device still on the shared key stops tapping at that moment. Do the rollout in one sitting rather than across a week, and have every counter in front of you before you start.

Settings, Kiosks, Shared key shows whether the shared key is in use, and offers Rotate key and Switch the key off.

Tap a card on a connected reader, where this kiosk offers card tap. The waiting screen shows a large Tap your card prompt that points at the reader, using the kiosk’s Where the card reader is setting. On a landscape tablet the prompt sits beside the sign-in form. The kiosk recognises the card, flashes a verified ID card, and greets the person by name.

Or type a username, where this kiosk offers the password form.

A kiosk with password entry switched off leads with the reader and says “Card not working? Please see the office.” That is enforced at the server, not just hidden on the page.

Card tap only ever works on an enrolled kiosk. A card is one factor, and a found card plus any laptop must not open a student’s portal.

Typing a username proves nothing, so it is disabled by default in production across the whole deployment. People tap their card instead.

If your kiosk sits somewhere physically supervised and you want username entry, an administrator can enable it with PORTAL_USERNAME_ENTRY=1. Each kiosk’s own password entry setting then decides which counters offer it.

A kiosk pinned to a campus can refuse to open a session for somebody belonging to a different one. An iPad in the junior school office is not a place the senior school’s records should appear.

Off by default. Tick Only people from this campus in the kiosk’s settings, beside its Campus.

Five ways, each covering a different case.

DefaultCovers
Idle timeout90 secondsThe student walked away
Session ceiling300 secondsSomebody parked on the page, or a token lifted off the device
Sign outImmediateThe student is done and says so
The next card tapImmediateThe queue moved on
End session in SettingsWithin a minute on screenSomebody left a session open and the office can see it

Twenty seconds before the idle timeout the kiosk asks “Still there?” with a countdown and an I’m here button. A minute before the session ceiling it says “Your time is nearly up”, and from two minutes out the header shows when the session ends. That warning matters: a student typing a long repair description with a stylus generates no events for a minute, and a kiosk that dumps their form without warning is a kiosk the school turns off.

A tap while somebody is still signed in switches user rather than being ignored. At a counter the next student taps while the last one’s menu is up, and the alternative is that they read the previous student’s screen while waiting.

Signing out is real. The session is ended on the server, not merely forgotten by the tab, so a copied token dies with it. The screen is cleared before anything is waited on, and every form on it is reset, so the next person starts on an empty form rather than on the last one’s half-written repair reason.

Both timers are bounded server-side. Idle is clamped between 15 and 900 seconds, and the ceiling between 30 seconds and an hour, so a typo cannot produce a kiosk that never signs anybody out. 0 for the idle timeout is honoured as “no idle timeout”, which a kiosk in a locked room may want, and the ceiling still applies, so it switches off one clock rather than both.

Legacy shared-key and demo kiosks use a 120-second idle timeout and a 900-second session ceiling. These fallback values differ from a reserved device’s default 90/300-second settings. Repair progress is shown inside the current sitting; signing out clears it without placing a reusable tracking link in browser history.

The home screen greets them by name and asks What’s wrong?: Report it opens a request to the desk with what they typed. Beside it are My device is broken, Locked out or forgot a password, Find an answer and Buy something, as the school offers them. Below, Your device shows their device, any loan and the repair in progress with its stages, and My requests lists what they have asked the desk for.

My device is broken opens Book a repair:

  1. Which device? The kiosk lists the devices linked to them, the one they last signed in to first. If theirs is not listed, My device isn’t listed lets them type the serial.
  2. What’s wrong with it? The faults appear in plain words, such as Cracked or damaged screen or Won’t charge. They do not choose a coverage; Plugboard works that out from the repair type.
  3. What happened? When it started and anything they tried.
  4. Add a photo, only where the school asks for one (Photo of the damage in Settings, Statuses & fields). Before the camera opens, one line says what the photo is for: it helps the technician and the repair company see the damage, faces should be kept out of it, and it is kept with the repair. They can retake it, remove it, or skip the step.
  5. Do you need a loan device while it’s repaired? Asked where the school lends devices. Somebody who already has a loan laptop out is not given a second one here; the desk can lend one.
  6. Book repair.

The photo can be a JPEG, PNG or WebP. It is scaled to at most 1600 pixels on its long edge before it is sent, held only in the page’s memory (never in the browser’s storage) and cleared when the sitting ends. Plugboard checks and re-encodes it, and drops its location data and other metadata before storing it with the repair. Only desk staff who can see the repair can see the photo; families never do.

A photo that cannot be used is refused before anything else happens, so it costs nothing: no loaner is issued, no repair is created, and the rest of the form keeps their answers. If the repair is booked but the photo cannot be stored, the repair stands and the finish card asks them to show the damage at the desk.

They are told the outcome immediately. The finish card gives the repair number to quote at the IT desk, such as Repair R-74 booked, followed by Photo added. when the photo was saved, and says they will be emailed when it is ready to collect. If a loan device was assigned, its loan number is shown large, with where to collect it. When the loan comes from a pool that erases devices on return, the card adds: Anything saved on a loan device is erased when it comes back. Save your work to your school account. If no loan device was free, it says to ask at the IT desk. Track this repair follows it, and Done goes back to the home screen.

At the desk, the repair arrives with a sticky toast so it is not missed.

Their repairs with current status, so they can check progress without asking anybody.

Two kinds of request.

Password reset. The fastest path is self-verification: the person taps their own card, or types its number, and goes straight to a “set a new password” screen. No staff time at all. This works only in a session that began with a card, a password or single sign-on: a card number is printed on the student ID, so a session opened with a typed username cannot use one to set a password. There the kiosk asks them to tap their card, sign in with their password, or ask a staff member.

If they cannot, they choose “Request reset (staff verifies)” and an ICT staff member approves it at the desk. The kiosk shows a waiting spinner and updates automatically when approved or denied.

Something else. They describe what they need and a staff member verifies their identity and helps.

Password resets go through your LDAP connector and are subject to your directory’s password policy, so a password your directory rejects is rejected here with the directory’s own message.

Buy a consumable: a bag, an adapter, a cable.

Products appear as tiles with their photo or icon, name, description and price.

  1. Pick the product and quantity.
  2. Verify it is them by tapping or entering a card, or entering a password.
  3. Confirm.

A confirmation is emailed to the student’s parents. That message cannot be switched off, because a parent is owed a receipt for money taken.

Opens the help centre.

With Facilities on (the campus operations add-on), a reserved kiosk with Visitor sign-in on this kiosk ticked in its settings, under Settings, Kiosks, becomes the front-office sign-in book for the visitor register. It is off by default on every device, and switching it on changes nothing about what the same device does at /portal.

Enrol the device as above, then open /visit on it, or use the Plugboard app’s kiosk mode, which offers the same register. A device that is not reserved, or does not have visitor sign-in on, says so and points a staff member at the setup steps. It keeps its secret either way.

Signing in. The visitor chooses Visitor or Contractor and gives their name, company and, optionally, a phone number, then who they are here to see and why. The host list is a typeahead over staff on the roster at the kiosk’s campus, and staff with no campus: it needs two letters, shows at most eight names, and shows nothing else about them. A contractor the office has issued a card to can tap it instead of typing. They are told to wait at the front office to be collected, or, for a contractor whose WWCC is expired or not recorded, that a staff member needs to see them before they go in.

Signing out. Tap the card, or type the full name. The kiosk looks first at its own campus (every campus, for a kiosk with no campus), ignoring case. If nobody matches there and the register’s setting Let visitors sign out at any campus’s kiosk, not only the one they signed in at is on, which it is by default, it looks across every campus. The name must match exactly one open visit; anything else asks them to see the front office.

Badges and photos. With Print a visitor badge after signing in, at kiosks and at the office on in the register’s settings, the kiosk prints a badge once a visitor is signed in: their photo if one was taken, name, visitor or contractor, company, host, the time in, and the school’s name and logo. Choose the Label size to match your label printer. A browser shows its print dialog unless the device prints silently; in the app, an iPad prints to a printer chosen once. A contractor held for a WWCC gets no badge until the office sights the check, and the office’s Sight check and print badge prints it then.

Visitor photo at kiosk sign-in is Off by default; it can be Optional (visitors can skip it) or Required. The kiosk’s front camera takes the photo, and before the camera opens the visitor is told what it is for and how long it is kept. Photos are deleted 7 days after the visit, and only staff who can see the register can see them.

The kiosk never lists who is on site. A list of the strangers in the building is not something to leave on a counter; the on-site list is on the desk, for staff with visitor.view. The kiosk cannot record a WWCC either, and every screen clears itself after 90 seconds.

A visitor kiosk signs people in at the campus it is reserved for, so reserve one per front office, or leave its campus as Any campus to serve the whole school from one counter. If your school still uses the shared kiosk key, claiming the first device switches it off; plan that before you set up a visitor kiosk.

For supervised iPads and Android tablets enrolled as dedicated devices, your MDM can make a tablet a kiosk with nobody typing a code at it. The device runs the Plugboard app, enrols itself when it opens, and locks itself to the app.

Settings, Kiosks, Enrolment tokens, Create a token.

FieldWhat it does
NameWhat the devices are, like Library iPads
Let known devices in without approvalA serial your MDM sync already knows, and that has no kiosk, goes straight through. Anything else waits for you
Only the genuine Plugboard app goes straight throughDevices must prove they run the genuine app (Apple App Attest or Android hardware attestation). Devices that cannot prove it wait for approval; none are refused
Stop after this many devicesLeave empty for no limit
ExpiresAfter 7, 30 or 90 days, or never
Kiosk settingsThe settings every kiosk it enrols starts with, as in each kiosk’s settings

The token is shown once. Before you leave the dialog, either:

  • Download the profile files: the iPad app configuration, the iPad single-app profile and the Android managed configuration, with your MDM’s serial number variable filled in. Choose Your MDM first; the page tells you to check the variable against your MDM’s own reference.
  • Or push it straight into your MDM: pick a configured Jamf Pro or Intune connector and press Push to it. Plugboard creates the app configuration and the single-app profile, unassigned. You then scope them to your kiosk devices in the MDM. Nothing else in your MDM changes.

On an iPad, add the Plugboard app to the devices, paste the app configuration into its App Config, and deploy the single-app profile. On Android, add the app from managed Google Play, apply the managed configuration, and allow the app in your kiosk or lock task policy. Open the app once on a device and it appears under Devices, enrolled or waiting for approval.

Revoke token stops any further devices using it. Devices it already enrolled keep working.

A device waits under Kiosks waiting for approval when its serial is not in your device list, already has a kiosk, or did not prove it runs the genuine app. An unknown serial is how a leaked token would show up, so approve only a device you expect. Review shows the serial, whether it is in your device list, the token it used and whether it proved the genuine app. Approve lets it in, and it collects its key the next time it checks in, within a minute. Approving a device retires any other kiosk with the same serial. Reject refuses it, and it stays an ordinary app until it enrols again.

Removing the profile in your MDM un-enrols a device that enrolled this way.

The app locks the device to Plugboard (Autonomous Single App Mode on a supervised iPad, lock task mode on an Android dedicated device) while it is a kiosk. On a device your MDM does not supervise or fully manage, the app cannot lock itself; use the platform’s own Guided Access or screen pinning instead.

To get into the device, choose Unlock for 15 minutes from the kiosk’s More actions menu. The device unlocks at its next check-in and locks again by itself when the window ends; Lock again now ends it early. The app also unlocks when the kiosk is revoked.

An Android tablet with NFC reads cards with its own reader, so nothing has to be plugged in. An iPad has no NFC reader; use a USB or Bluetooth reader that types like a keyboard. If a tablet’s own reader reads a card as a different number from the one in your records, every tap is refused. Test the card reader, in the app’s kiosk setup, shows a tapped card in every format so you can pick the matching Card format for the tablet’s own reader. Matching on the server is always exact.

Kiosks in the desk navigation (/kiosks, under Operations) shows which kiosks are online, who is signed in on each, and who was. It needs kiosk.view, a free permission meant for the front office or a year coordinator answering “who was on the library iPad at 2pm”. The page is read-only: it shows no address, serial or setup details, and cannot change a kiosk.

Settings, Kiosks, Devices shows the same, plus each device’s settings, the platform and app version it reports, and the actions.

StateMeaning
In useSomebody is signed in, with their name and since when
OnlineThe kiosk checked in within the last two minutes
OfflineIt has missed two check-ins
Waiting for approvalEnrolled through your MDM and held

History on a kiosk lists each sign-in, newest first: who, how (card, the tablet’s reader, camera, password or school account), when, how long, and how it ended (signed out, timed out, session limit reached, the next person tapped in, or ended from Settings). Filter it by name or date. Visitor sign-ins appear for readers who can also see the visitor register. History is kept for 90 days at most.

A person’s profile has a Kiosk sign-ins panel with the same rows for that person, for staff who hold both kiosk.view and client.view.

End session, from a kiosk in use, signs the person out at once on the server. The kiosk’s screen clears within a minute and says the office signed them out. It is recorded in the audit log.

Settings, Kiosks, Kiosk look sets what every kiosk screen looks like:

  • a background image (PNG, JPEG or WebP, up to 4 MB; landscape works best);
  • what sits Over the image: darken it for white text, lighten it for dark text, or leave it as it is. A warning appears when the headline would be hard to read;
  • a font: one of a curated set, or your own file (TTF or OTF everywhere, WOFF and WOFF2 in browsers only, up to 2 MB). Check its licence allows this;
  • a headline (up to 80 characters) and a line under it (up to 200).

A sample of the kiosk’s sign-in screen follows your changes. Save with Save kiosk look. A kiosk with its own headline, line or background in its settings uses those instead.

The look applies to reserved kiosks and /visit, not to a student opening the portal on their own laptop.

The arrangement that works:

  • A tablet on a stand, at the counter, in full screen, showing /portal.
  • A USB card reader attached. Most act as keyboards and need no configuration. The kiosk keeps a hidden field focused while it is waiting for a card, so the reader always has somewhere to type, including on an iPad, where nothing would be focused otherwise. The on-screen keyboard stays down, and focus is handed back the moment somebody uses a real field.
  • A sign saying what it is for. “Book a repair here” gets used; an unlabelled tablet does not.
  • Somewhere staff can see it, both so people get help if they are stuck and because that supervision is what makes username entry defensible if you enable it.

The kiosk shows its own name discreetly in the header, so a student can tell they are on a school device and a technician can tell which record they are looking at without opening Settings.

SettingEffect
Per kiosk, in SettingsCard tap, password entry, campus enforcement, reader position, card format, visitor sign-in, idle timeout, session ceiling, the kiosk’s own look
PORTAL_USERNAME_ENTRY1 allows username-only entry on this deployment. Off by default
PORTAL_SESSION_TTL_MSThe default portal session lifetime, 15 minutes. A kiosk session takes the shorter of this and its own ceiling

Everything under Settings, Kiosks needs feature.manage, the same permission that turns the portal module on. Pushing enrolment files into an MDM also needs connector.manage. Seeing which kiosks are in use and who signed in needs only kiosk.view (see watching your kiosks).

Repair types, and whether booking a repair asks for a photo, come from Statuses & fields. Loan assignment comes from loan groups. Products come from stock.

The induction kiosk runs on a reserved device and shows its name and kiosk look, but does not use that device’s sign-in settings. The card checker has its own notion of a kiosk.

A reserved kiosk’s lock and status are reported by the device. Plugboard shows them as reported and does not enforce the lock; that is the job of the device and your MDM.