Remote access
/admin/remote to configure, and a button on each device
page. No module gate: this is available on every plan.
Plugboard does not ship a remote control product. It puts your existing one (ScreenConnect, TeamViewer, AnyDesk, Splashtop, NinjaOne, an RMM web console, plain Remote Desktop) on the device page with the right machine already selected, and write down who started a session and on whose device.
What Plugboard does and does not hold
Section titled “What Plugboard does and does not hold”It assembles a link and records the intent. That is all.
It never carries the session, never proxies a screen, and never holds a credential that could control a machine. Your own tool still signs the technician in and still decides what they may do. If your remote tool is switched off, nothing here reaches anybody’s device.
Configuring a target
Section titled “Configuring a target”Settings, Remote access. A target is a link with the device’s details substituted in.
| Field | |
|---|---|
| Label | What the button says: Remote in, ScreenConnect |
| URL template | The link, with placeholders |
| Scheme | Web console opens in a tab; App hands the URI to an installed application |
| Device type | Optional. Show this target only for laptops, or only for iPads |
| Campus | Optional. Show this target only at one campus |
| Notify the person using the device | On by default. See below |
| Enabled, rank | Whether it appears, and in what order |
Worked examples:
https://your-console.example.com/devices?search={serial}teamviewer10://control?device={mdmId}anydesk:{assetTag}rdp://full%20address={hostname}The placeholders
Section titled “The placeholders”A closed list, on purpose. If a template could name any field of the device record, it could carry a column that should not leave the database into a third party’s access log.
| Placeholder | |
|---|---|
{serial} | The serial number |
{assetTag} | Your asset tag |
{model} | The model |
{hostname} | The hostname |
{mdmId} | The MDM’s own id for the device |
A template must contain at least one.
Every substituted value is percent-encoded, so an asset tag containing & or #
cannot rewrite the rest of the URL.
A template naming a field this device has no value for produces no button, and the device page says which field is missing.
The schemes
Section titled “The schemes”Also a closed list.
https: for a web console, and then the URI schemes browsers hand to an
installed application: rdp:, vnc:, teamviewer:, teamviewer10:,
anydesk:, screenconnect:, splashtop:, dameware:, ms-rd:.
There is deliberately no http:. A remote support console reached over plain
HTTP sends a credential and a screen share across the school network in clear.
javascript:, data: and file: are refused as well. A template is written by
an administrator and rendered into a link a technician clicks, so a surprising
scheme in between is a risk.
Templates are checked when you save them, so the administrator writing one is told what is wrong with it.
Telling the person
Section titled “Telling the person”Notify the person using the device is on by default, because these are mostly students’ devices.
Plugboard returns the flag rather than sending the notice itself, because the MDM or the remote tool is what can reach somebody mid-lesson. Wire it into whichever of those you use.
Turning it off for a target is a decision a school has made about children’s screens, and it is recorded on the target and again on every session started with it.
Permissions
Section titled “Permissions”| Permission | Allows |
|---|---|
remote.start | See what can be started on a device, and start it |
remote.manage | Create, edit and remove targets |
Neither is folded into device.manage. That permission is held by whoever
corrects a room number or a warranty date; remote.start watches a screen that
mostly belongs to a child.
What is audited
Section titled “What is audited”Each of these is written to the audit log:
remote.start | Who started it, on which device, which target, which placeholders were filled, the serial, who the device is assigned to, and whether the notice was on |
remote.targetCreate | The label, the template, and whether it notifies |
remote.targetUpdate | The same, with what changed |
remote.targetDelete | Which target went |
The remote.start row is written before the link is handed over, so a
session is recorded even if the process dies straight after.
There is no second row on success: the link either was handed over, or the request errored before that point.
If your tool has a connector
Section titled “If your tool has a connector”Plugboard has a remote access connector category for the two things a link cannot do: saying whether the machine is online before somebody clicks, and minting a session that expires. Nothing ships in it yet, and the device page works without one, so any tool with a link works today. If you want a connector for your tool, see getting one built.