Skip to content
plugboard.appRequest a demo

Running the desk

Devices

Open Devices for the filtered inventory, or reach a device record from search, a loan, a repair or a person.

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

Search by serial, asset tag, model, room or surname, and filter by Type, Status, Location, Management (devices no MDM reports) and the school’s own device fields. While the school’s AI is on and you may use Ask, Describe a filter turns a sentence such as “unassigned iPads out of warranty” into the list’s own filters. Display chooses table or cards, the order, and up to three school field columns.

A device nobody holds reads Not assigned where a person’s name would be, or Spare or On order when that is its status.

Filter the list, then Export CSV, or tick devices and export just those. The download includes all matching devices across every page, within the same campus permissions as the inventory. A technician with device.view can export; device.manage is not required.

Columns are serial number, asset tag, device type, model, assigned person’s name, location, status and warranty expiry. Dates use YYYY-MM-DD, and the status keeps its stored value, such as ACTIVE for a device In service, which the import reads. Spreadsheet formula characters in text are neutralised. The file is read in batches and concurrent inventory changes can affect later batches.

An export can contain up to 10,000 devices and 10 MiB of CSV data, with five requests per minute. If either size limit is exceeded, the page reports an error and asks you to narrow the filters. It never downloads a silently truncated file.

The header holds Refresh, New repair (for people who can lodge repairs), any actions the school has set up for devices, and More (Model icon, Add to the loan pool on a spare, Copy serial). The main column then reads:

  1. The open repair, when there is one: its fault, the repair’s stages, where it stands and how long ago it was opened, with Open repair.
  2. History. MDM check-ins alongside the repairs, loans, tickets and handouts Plugboard already holds for the device, plus ThreatLocker history where there is any. A laptop on its third screen this year is a different conversation from one on its first.
  3. Management. First what needs a look (a compliance finding, a duplicate or unmatched record, stale check-ins), then the device commands, Remote access for people with remote.start when a remote support tool is configured, Privileged actions, the management records, which MDMs manage it, the facts each reports, Apple enrolment, where the network last saw it, and the linked sources.
  4. Lifecycle. Whether the device can be retired, and Retire device, or its disposal record once retired.

The column down the side holds the device’s facts:

  • Assigned to, with Change for people with device.manage. The holder links to their person page for anybody with client.view.
  • Status, Type, Location, Asset tag and Purchased. Type and asset tag can be corrected in place; a value typed here stops following the MDM until you hand it back. Status is the school’s own: people with device.manage set it in place to On order, Spare, In service, In repair or Lost. Retiring is Retire device, under Lifecycle, because it records a disposal.
  • Warranty or AppleCare+: whether coverage is active, ending soon (within 90 days) or ended, with the days left, and a meter of how much of the coverage period has been used when the purchase date is known. Expiry comes from the device record or a warranty connector. Insurance when the device is not on AppleCare+.
  • Supplier: the supplier it came from, with holds the warranty when the school claims warranty through them, and how to reach them. People with device.manage set it, or Change it.
  • Compliance, Last seen and System, from the MDM. When no MDM reports the device, compliance reads as not checked, because an unmanaged device is not known to be fine.
  • School fields, when the school has device fields.
  • With this repair or Lent out: the loaner lent while this device is in for repair, or the loan this device is out as.
  • Changes: the change records linked to the device, for people with change.view.
  • Used by: the services that depend on the device, with their status, for people with service.view. A service whose fleet takes the device in, such as Student laptops for every laptop, is marked by rule.

Compliance. When a management record reports the device as not compliant, or could not check it, the reasons are listed first under Management, with when it was evaluated.

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

A device’s status says where it is in its life:

StatusMeaning
On orderBought, but not here yet
SpareIn stock and ready to issue
In serviceIn somebody’s hands, or in use where it is kept
In repairBeing repaired
LostMissing
RetiredDisposed of, through Retire device

A device’s status reads the same everywhere on the desk: the list and its Status filter, the summary beside the list, the school map, reports, flows and the mobile app.

Status is the school’s own column, and no device management connector sets it. The one exception: when a sync assigns a spare or a device on order to somebody, it becomes In service, because it is in their hands. A spare kept unassigned stays a spare.

On the desk:

  • The Status filter on Devices has both. A spare or a device on order is never flagged for being unassigned, and the summary beside the list says A spare, ready to issue or On order; not here yet.
  • A spare laptop, Chromebook or iPad that is not in a loan pool offers Add to the loan pool in More. It opens Register loan on Loans with the serial filled in, offering only the loan groups of that kind. That needs loan.manage and the Loans module.
  • Replacing a device on a repair offers spares first, and an old device kept as a spare is marked Spare.
  • A stocktake does not expect a device on order. If one turns up, it is named as a device on order rather than counted.

How the fleet counts them:

SpareOn order
In the fleet, its age and its warranty figuresYes, with spares on hand shown by typeNo, counted beside the fleet
Fleet health, Unmanaged and warranty viewsYes. A spare switched off on the shelf is not called inactiveNo
Cost per device per yearYesNo
Managed devices on the licenceNoNo

The licence counts devices in service or in repair, so neither a spare on the shelf nor a device still on order is billed.

The device commands under Management are the ones the device’s connector can send, for the management record chosen under Send through. Each connector declares its own commands, so the device page, the ticket’s device actions, flows and Ask offer the same ones. A command the device’s platform cannot take is not shown.

ConnectorCommandsConnector setting
IntuneLock (iOS, macOS, Android; Intune cannot lock a Windows PC remotely), restart (Windows, iOS, macOS), check inallowDeviceCommands
Jamf Pro, MacsLock, restart, check in, shut downallowDeviceCommands
Jamf Pro Mobile, iPhone and iPadLock, restart, check inallowDeviceCommands
MosyleLock, restart, shut down, clear passcode (iOS)allowDeviceCommands
Chrome EnterpriseDisable, re-enableallowDeviceActions

Every connector setting is off until a connector administrator turns it on. A command turned off in the connector’s settings shows as “Turned off in connector settings” to people with connector.manage, and is hidden from everyone else.

CommandWhat it asks first
Check inNothing. It is sent straight away
Restart, shut downA confirmation
Lock, disable, re-enableA reason of at least 10 characters, in a dialog that names the device’s owner
Clear passcodeA reason and the last four characters of the serial. For a student’s device, also the ticket or person who asked

Check first runs every check and says what would be sent, and to which record, without sending anything. A refusal is shown in the dialog. Every command needs device.manage and is recorded in the audit log with its reason and ticket before it is sent. The reason is never sent to the vendor, and a command is never sent twice.

A ticket’s Device actions section offers the same menu for the ticket’s linked device, and every command sent from there carries the ticket.

A flow can send these commands too. A fully automated flow may only restart, shut down or check in a device: lock, disable, re-enable and clear passcode always wait for a person’s go-ahead, and a flow that sends them cannot be published fully automated.

Limits that apply to everyone:

  • Let the desk send device commands, under Settings, Modules, Device commands, stops every device command for the school at once: from the desk, from flows (including their locks and check-ins), from device fixes and from the restart step of an access request. It is on by default and needs feature.manage to change. While it is off, the page says that device commands are stopped for the school.
  • Each person can send up to 30 commands an hour. A fully automated flow’s commands count against its owner.
  • The same command to the same device is refused for a minute after it is sent, with who sent it and when.

Which policies fail. On a device Intune reports as not compliant, Which policies fail lists up to 20 failing compliance policies. They are read from Intune when opened and are not stored.

Erase is not a device command. Erase this device sits under Privileged actions and uses the separate privileged workflow: a request with a reason of at least 10 characters, the serial typed to confirm, and approval checks. The school turns erasing on with Let the desk erase devices under Settings, Modules, Device commands, where it also sets whether a second person must approve each erase (recommended, and on unless changed), how long to wait before sending (an erase can be called back during the wait) and the most erases per day, from 1 to 50. Confirming an erase, or reading a local administrator password, takes a code from your authenticator or a passkey, and only a passkey where the school requires one for sensitive actions. Five wrong answers within 15 minutes stop both for you: wait 15 minutes, then try again.

When a loan group holds returned devices until they are erased, the device page of a held loaner says Loan #12 is waiting for this erase. Erase on the Loans page opens this page with the erase dialog already open, the device’s MDM record chosen and a reason naming the loan (never the borrower) filled in. It does so only when the dialog could be opened by hand: erasing is on, nothing is already queued for the device, a reviewed management record exists, and no earlier erase with an unknown outcome is waiting to be acknowledged. The serial and your authenticator code or passkey are never filled in: type the serial from the label on the device in your hands, not from the screen. The loan goes back on the shelf when the erase is sent.

Import CSV (needs device.manage) adds a pallet of devices, or corrects the ones already here, from a supplier’s spreadsheet. The only required column is the serial number; the dialog maps columns such as type, model, asset tag, location, purchase date and warranty expiry from whatever your supplier called them. The campus you pick applies to devices the import creates; existing devices keep theirs.

Review import shows what will happen to every row before anything is written: new, updated, unchanged or invalid, and which fields will change. A serial already in the register is corrected from the file. A value you import is kept as entered and stops following MDM sync, so the review names any field that will. Only values that differ are written, so re-importing last term’s spreadsheet does not pin locations the MDM already agrees with.

The import applies exactly what you reviewed. If the register changes between the review and Import, it stops and asks you to review again. Invalid rows are skipped rather than failing the file; Download rows to fix gives you those rows with an Import problem column, ready to correct and import again. A file can hold up to 5,000 rows and 2 MB; split a larger one.

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, and Managed by lists each MDM that reports it. A device managed by more than one, as during a migration or on a Mac co-managed for Conditional Access, is not a duplicate.

A common school arrangement is Jamf or Mosyle for Apple, Intune for Windows, and Chrome Enterprise for Chromebooks.

Serials are matched uppercased, so case differences do not matter.

Autocomplete searches the device records already stored in Plugboard. Connector sync and supported live lookups enrich those records from the MDM.

A Chromebook disabled in the Admin console, often 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; export the inventory
device.manageAdd or import devices, correct lifecycle fields including the status, set the device’s supplier, and send the device commands a connector offers
device.wipe.requestRequest an erase through the privileged workflow, including a held loaner’s
device.wipe.approveApprove an eligible erase request