Skip to content

Devices

/devices/<serial>. Reached from search, or from a link on a loan, a repair or a person.

Every device has a record in Plugboard, enriched live from your MDM when a connector is configured.

Identity and hardware. Model, serial, and whatever your MDM knows: OS version, enrolment status, battery percentage, last check-in. Which of these appear depends on the MDM.

Assignment. Who it belongs to, and their year level or role.

Lifecycle fields. Purchase date, status, location and notes. See asset lifecycle.

Warranty. Expiry and coverage, when a warranty connector is configured.

History. Repairs and loans associated with the device.

That last section is the one technicians use most. A laptop on its third screen this year is a different conversation from one on its first.

When an MDM connector is configured, the page exposes the management actions that MDM supports:

ActionNotes
LockRemote lock
Wipe or eraseDestroys data and cannot be undone
Restart
Clear passcode
Push an app or profileDepends on the MDM

The exact set depends on your MDM and your permissions. Actions require device.manage and every one is audited with who sent it and to which device.

The device still has a record. It just has no live inventory and no management actions until you configure an MDM connector.

Records are created from repairs, loans and inductions, so a device turns up in the system the first time somebody does something with it, whether or not it is enrolled anywhere.

Configure as many MDM connectors as you run. A device resolves through whichever one knows its serial.

The common school arrangement is Jamf or Mosyle for Apple, Intune for Windows, and Chrome Enterprise for Chromebooks. The repairs screen does not change.

Serials are matched uppercased, which handles the most common transcription inconsistency.

The autocomplete when lodging a repair or registering a loan queries your MDM live, so what gets recorded is what is actually enrolled rather than what somebody read off a worn sticker.

Worth knowing if you run Chromebooks. A Chromebook that was disabled in the Admin console, usually months ago, presents to a student as a device that will not start.

The Chrome Enterprise connector carries the status through, so DISABLED appears on the record and answers the ticket before anyone opens the lid.

PermissionAllows
device.viewSee device records and history
device.manageSend MDM commands