Skip to content
plugboard.appRequest a demo

Running the desk

People

/people for the People screen, and /people/<id> for one person’s full page. People is in the navigation’s People group for anybody with client.view, or with the Directory module and directory.view, and a person is also one search away.

A person is a student, staff member or parent. People come from your student information system, from a CSV import, or are added by hand. The source owns them, and the roster sync keeps the synced ones current.

Directory accounts are the Directory accounts tab of People. A /directory link, including the ones on tickets, opens it with its search and ticket carried across.

Type a name or a username in Search or ask at the top of the frame and pick a person to open their page, or press Enter for full results. Or open People and search the roster.

A link to a person from anywhere else in the desk, whether a device’s holder, a ticket’s requester, a repair’s client or a buyer in stock history, opens that person’s full page. A link to /people?q= opens the person it names, or searches the roster when it names nobody in particular.

Each source keeps its own record of a person: matching ids in two sources do not merge them. A student system’s first sync, in a school whose people already came from somewhere else, matches them first. See the first sync of a student system.

Tabs across the top choose who is listed:

TabShowsNeeds
Everyone, Students, Staff, ParentsThe people stored in Plugboard, each tab with its countclient.view
Directory accountsA live search of the accounts in every directory connection you can see: Entra, Google and Active DirectoryThe Directory module and directory.view

Somebody with only directory.view opens straight into Directory accounts. The tab and the search are kept in the address, such as /people?view=accounts&q=jordan, so a bookmark or a link from a ticket opens the same search.

In every tab, selecting a row opens a preview beside the list, or as a sheet from the bottom on a narrow screen. Escape closes it.

Search by name, username or ID, choose a Year, and narrow further under Filters: campus, tutor group, source, status (active, inactive, or both), student system campus when people carry two or more, and the school’s own fields. Display chooses table or cards, grouping by role, year or department, and which of the school’s fields show as columns. The refresh button sits at the end of the row.

Each row shows the person, their campus when the school has more than one, the school’s list fields (a House column, say), and counts of their devices, items on loan, open repairs and open tickets. A zero is left blank.

Under the list, Source names where the stored records came from, with a count for each: the student system’s connection, CSV import, or By hand. Find someone in the SIS searches the stored records and the student system together; choosing somebody only the student system knows adds them, once.

The roster preview shows who somebody is, what they have right now (devices, loans, open repairs and open tickets) and the common actions, so a quick question at the counter does not need a page of its own. Open full profile takes you to their page.

Add person (needs client.manage) covers people your student system does not have, such as a relief teacher on their first morning. The More menu beside it holds:

  • Import CSV (needs client.manage). An import is reviewed before anything is written, and never changes somebody already here. Invalid rows are skipped instead of failing the whole file, and Download rows to fix returns them with an Import problem column to correct and import again. If the roster changes between the review and the import, it stops and asks you to review again.
  • Sync roster (needs user.manage) pulls from your student system straight away, as well as on its schedule. The result says how many people were added, updated and deactivated, or why nothing changed.

Search every directory connection at once. If a connection cannot be searched, the results say they are incomplete and name it. Open an account to see whether its sign-in is on, its licences, inbox delegates and groups, and act on it: Disable sign-in or Enable sign-in, Reset password, and assign or remove a licence. Find in roster switches to the roster searching for that person’s name.

Each account action is recorded to a ticket. Ticket for these changes drafts and raises one for you, and arriving from a ticket links the actions to that ticket straight away.

For a live Entra account, each action asks for the person’s name or sign-in address, a reason for the audit log and fresh authentication, the same checks as the person page. Other accounts use the older directory operations, which change demo fixtures only. A demo action logged to a ticket is marked as demo and is not evidence of a real change.

Inbox delegates can be added and removed here only on the demo directory. For a live account the delegates are listed read-only, and delegation is managed from the person’s Account & groups tab.

Everything about a person in one place. The header shows their name and one line of who they are here: year, tutor group and the school’s list fields for a student, position and department for staff, with a staff member’s Teams status where it is shown. Where a timetable connector is set up, it shows where they are timetabled now and next.

Overview holds the everyday record, in the order somebody walking over needs it:

SectionShows
DevicesThe devices assigned to them, with Check MDM for people with client.manage. With none, it reads No devices assigned in Plugboard and offers Find by serial
Active loansThe loans they have out, overdue first and then soonest due, with how many are overdue and Return on each
RepairsTheir repairs and where each stands, the 20 most recent
Open ticketsTheir open tickets, the 20 most recently updated
Recent activityWhat has happened with them lately, newest first

A section with nothing in it is left out, so a person with no loans has no Active loans section. Devices stays, so Find by serial is there when nothing is assigned. A long list shows its first five rows (six for Recent activity), with Show all and the count to open the rest in place, and Show less to fold it again.

Each section needs the permission and module for what it shows. When your role or the school’s modules leave something out, a note on the page says which.

Beside Overview, a tab appears only when you have access to what it shows:

TabShowsNeeds
Account & groupsTheir live directory account: state, groups, licences, sign-in methods, recent sign-ins and Conditional Access, with the account actionsThe Directory module, identity.view and an email address on the person
PurchasesUp to 20 recent purchases at the desk or kiosk, with the visible totalAccess to purchases or costs
Kiosk sign-insWhere and when they signed in at a kioskkiosk.view and client.view

When Overview would be the only tab, the page shows no row of tabs. What each directory provider supports is on directory accounts.

The Account tab lists the person’s groups, and people with identity.license.manage can assign and remove licences there. Assigning uses one of the tenant’s seats straight away; removing stops the services that depend on it. Both ask for the person’s typed name, a reason and fresh authentication, like the other account actions. Without that permission the licences are listed read-only.

Each connected account on the tab has an Account recovery group: Unlock, Reset password and Reset MFA, as the provider and your permissions allow. See account recovery.

The side panel holds:

  • Details: username, student or staff ID and email, each with a copy button, campus and Source. Edit school fields (needs client.manage) edits the school’s own fields.
  • Staff details for staff. See staff details.
  • Experience with IT, for staff, to people with report.view and client.view. See staff experience.
  • Flows, their people flow runs.
  • Notices: the language their notices go in, their mobile number and SMS opt-out.

/people/<id>#devices, #loans, #repairs and #tickets open Overview at that section with every row shown, and #account opens Account & groups, so you can send a colleague straight to the part that matters. On the People list, a line beside a selected person such as 2 more open tickets. opens their Overview at that section in the same way.

Start date, leaving date, department, position, manager and preferred name come from the student system where it sends them. A field it does not send can be filled in on Staff details (needs client.manage); a field it does send shows where it came from and cannot be edited in Plugboard.

On the preview and the person page, each shown only to somebody who could complete it:

ActionNeeds
Lend a deviceloan.issue and loan.view
New ticketticket.create and the Tickets module. The person is already filled in as requester

The person page also shows any actions your school has set up for people. Its More menu holds:

ItemNeeds
Copy link to profile
Check cardThe Card checker module and client.view. Opens the card checker
Check MDM for devicesclient.manage
Search all accountsThe Directory module and directory.view. Opens Directory accounts searching for this person, to find their account in another directory connection or one that is not linked
Don’t show a photo for this personclient.manage, for staff
Reset password…Access to their directory account, as above, and identity.password.reset. Opens the Account & groups tab

Which fields are populated depends on your source system.

FieldFrom
External idThe source system’s own identifier
Name
Email
UsernameUsed at the kiosk when card entry is unavailable
TypeStudent, staff or parent
Year levelStudents
Tutor or form groupDrives the tutor notification email
CampusStudents, from TASS, OneRoster and Wonde where the system sends it. Free text; it never decides who can see the person
Card numberUsed by the card checker and the kiosk
ActiveLeavers stop appearing
SourceThe student system’s connection, CSV import or By hand

A school that already has people from one student system or a CSV import, and connects another, would otherwise get a second copy of everyone. So the first sync of a student system waits when:

  • it has synced nobody yet,
  • active people here came from another source (another student system or a CSV import; people added by hand do not count), and
  • nobody has matched people or chosen to add everyone as new.

Sync roster then says Match people before the first sync. A school with nobody from another source syncs straight away.

On Settings, Connectors, choose Match people in the student system’s row menu. It needs user.manage, from an administrator not limited to some campuses, because the match covers the whole school. Plugboard reads the student system’s roster and previews, without changing anything:

ListMeans
MatchedKept as they are, and kept up to date by this student system from then on
NewAdded by the first sync
Look like returning peopleNew here, with the username of somebody inactive. Merge them by hand if they are the same person
Could not be matched safelyMore than one possible person, so none was chosen. Added as new by the first sync
Here, but not in this student systemLeft as they are. Nobody is deactivated by matching

Matching is by exact username, then exact email, ignoring case, within the same type of person, and only when the match is one to one both ways. Nobody is ever matched on name.

  • Match n people keeps each matched person, with their devices and history, and hands them to this student system. The student system they came from is switched off. Nobody is deactivated.
  • Add everyone as new people matches nobody, so the first sync adds a second record for anyone already here.

If the student system or the people here change between the preview and Match, it stops and asks you to check the matches again. Then sync the roster from People.

Plugboard detects leavers itself: on each sync, anyone active whose record came from that student system and whose external id is missing from the pull is deactivated, whether or not the system flags them inactive. People from a CSV import or another student system are never deactivated by it. Their records stay, so a repair they lodged in 2024 keeps its owner.

Three stops keep a bad pull from rewriting the roster:

  • An empty pull usually means a broken connector, so Plugboard leaves the list alone instead of deactivating everyone.
  • The leaver cap, per type of person. If a pull would deactivate more than a fifth of the active students from that source, no student is deactivated; the same holds for staff and for parents. The other types proceed. The result says Roster synced, deactivations held back, and people with user.manage get an alert.
  • The creation cap. If more than half of a pull is people the source has never seen, while it already holds active people, it looks like a re-keyed roster (a school changing student systems, say) and nothing is written. The result says so, and people with user.manage get a sticky alert to check the student system before syncing again.

The sync result and the audit log report how many people were added, updated and deactivated. A failed sync raises a sticky alert for people with user.manage, so an overnight failure is still on screen in the morning.

Card numbers come from your student system. A card belongs to one active person, student or staff. Where somebody has a card that is not on file yet, such as a replacement, register it from the card checker, which also moves a card from one person to another after you confirm it.

The roster sync never gives a card to a second person: if the student system sends a card another active person holds, that row syncs without it and staff with user.manage get an alert naming them. See where card numbers come from.

If you run PaperCut, the card checker can write a recognised card into it, so the card that identifies somebody at the desk is the same one that releases their printing.

Parents use the parent portal to see their children’s records. The link between a parent and a child comes from your student system, so if the parent portal shows the wrong children, or none, fix it there.

PermissionAllows
client.viewSee people and their profiles
client.manageAdd, import and edit person records, register cards
user.manageSync the roster, and match people before a student system’s first sync