Skip to content
plugboard.appRequest a demo

Running the desk

Card checker

/card-checker. Needs module.cardChecker.

Tap a card, see who it belongs to. Use it at the counter to confirm the card is theirs before handing over a device, resetting a password or completing a purchase.

Tap a card on a connected reader, anywhere on the page, or type it under Or enter a card ID and choose Check. Plugboard looks it up and shows the matching person with a verified animation that is hard to misread at a busy counter, or says Card not recognised. A card matches whole, ignoring letter case, and staff cards work the same way as student cards.

A card belongs to one active person in the school, student or staff. Two active people can never hold the same card number. A leaver’s record can keep an old number without blocking anyone else.

When a card is not recognised, someone with client.manage can link it on the spot: enter the person’s Username or SIS ID and choose Register card. The page says Card linked to the person; tap the card again to confirm it verifies.

Two cases stop and ask first:

  • The person already has a different card. Confirm with Replace their card, or choose Keep the old one. Their old card stops working.
  • The card belongs to someone else. The message says “This card belongs to” the holder, and “Confirm to move it to” the person you typed. Choose Move the card to take it off the holder and give it to the person you typed, or Leave it where it is. When the person you typed also has their own card, one message covers both.

While the move question is on screen, it is the only thing the page says about the card: the Card not recognised banner is hidden, because the card is linked to someone after all. Choosing Leave it where it is brings the banner back. Changing the name you typed clears the question.

The lookup only finds people on the campuses you can see, so the move question usually means the holder is outside them. The message names the holder only when you could open their record yourself; otherwise it says “someone else”.

A move happens in one step: the holder’s card is cleared and the person you typed gets it. The audit log records it as a card move, naming both people and showing only the first four characters of the card. A plain link or a replacement is recorded as a card registration.

Most USB card readers act as keyboards: they type the card number and press Enter. That works with no configuration, and the page listens for a tap anywhere, so there is no need to click a field first. It tells a reader from a person typing by how fast the keys arrive.

If your readers are configured to send a prefix or suffix, either configure them not to, or be aware the number shown will include it.

When hundreds of new cards need checking against a roster, the fastest way to find the ones that do not work is to tap them all here.

The card tap at the service desk kiosk uses the same lookup. In the kiosk’s password reset flow the person taps their own card, which is what makes self-verification safe enough to skip staff involvement.

When a card is recognised, Follow-me printing offers Update in Fuji Xerox database, which writes the card to your enabled printing connector, so one card works at the service desk and at the printer. With no printing connector enabled, it says so. Writing the card needs device.manage, because the card releases the person’s held print jobs, and the card number and name written are the ones on the person’s record.

With PaperCut, Plugboard writes the secondary card field by default, leaving any existing primary card alone. It sends the person’s SIS ID as the PaperCut username, so it works where PaperCut usernames match SIS IDs. See the PaperCut connector.

Your student information system, synced with the rest of the person record. For people synced from it, the student system decides each person’s card: a card registered here is replaced by the next sync if the student system sends a different one, and cleared if it sends none.

If a card that should work reads as unrecognised, check whether your SIS returns card numbers. The field is easy to leave out of an API response.

The roster sync never gives a card to a second person. If the student system sends a card that another active person here already holds, that person’s row syncs without it and keeps the card it had, and the rest of the sync carries on. The sync’s audit entry counts the skipped cards, and signed-in staff with user.manage get an alert that stays on screen, naming up to five people and never the card numbers: “Roster sync left a card number unchanged because it already belongs to someone else here”. Fix the numbers in the student system, or move the card here.

If the student system swaps two people’s cards, both rows are skipped until one card is moved here.

PermissionAllows
client.viewLook a card up, and update a recognised card in the printing connector
client.manageRegister, replace or move a card
SymptomCause
Card not recognisedNot on file, or held by someone on a campus you cannot see. Register it, or check your SIS is returning card numbers
A registered card reverts or disappearsThe next roster sync wrote the student system’s card. Fix it in the student system
The roster sync alert names someoneThe student system gave them a card another active person holds. Fix the numbers in the student system, or move the card here
The number includes extra charactersThe reader is sending a prefix or suffix. Reconfigure the reader
Nothing happens on tapThe reader is not in keyboard mode. Type the number under Or enter a card ID meanwhile
Works here, not at the printerThe PaperCut card field. Check whether your MFDs read primary or secondary