Skip to content
plugboard.appRequest a demo

Start here

Words we use

A few of these mean something specific in Plugboard. In particular, “person” and “user” are two different things here.

Tenant. One institution. A self-hosted install has one. A managed customer gets a host of its own that serves no other customer; a group with several campuses can have a tenant for each campus on that one host. Every record belongs to a tenant and cannot be seen from another.

Person. A student, staff member or parent. People are synced in from your student information system and directory, not typed in. A person does not sign in to the console. They tap a card at the kiosk or sign in to a portal.

User. Somebody with a Plugboard account who signs in to the technician console, usually ICT staff. Users have roles; people do not.

Module. A feature that can be switched on or off for your institution, keyed as module.something. Turning one off removes its navigation and stops its endpoints answering. See modules.

Permission. A fine-grained right such as loan.issue or charge.approve. Permissions are granted through roles. See permissions.

Home. The desk’s first page: what needs you, what was spotted, your own work and how the desk is doing. See Home.

Settings. Where the desk is set up, at the foot of the menu. These docs name a settings page as Settings, Page, such as Settings, Ticket settings. See finding your way around.

Search or ask. The field at the top of the menu, also opened with Ctrl K. It finds records and pages. A question goes to Ask, the panel where Plugboard answers from your desk’s records or, where the school’s AI is on, from the AI model. See Ask and AI features.

Connector. An integration definition: a category, an authentication kind, a configuration form, a secret form, and a list of capabilities. Jamf Pro is a connector.

Connector instance. A connector you have configured, with your URL and your credentials. You can have more than one instance of the same connector.

Capability. Something a connector can do, such as looking up a device by serial. A feature asks for the capability, and whichever connector you have enabled answers, which is what makes swapping an MDM a settings change. See capabilities.

Demo mode. A per-connector switch that makes it return realistic fictional data instead of calling the real system. Use it before credentials arrive, and turn it off afterwards.

Connector agent. A small program installed inside your network so a managed deployment can reach systems that are not on the internet. It dials out; nothing dials in. See connector agents.

Submission. A repair. The desk calls the queue Repairs; these docs and the API also call one repair a submission. Somebody’s device needs work, and this is the record of it: the device, the problem, the person, the status and the cost.

Ticket. Work that is not a device repair. A fault, a request, a question. Tickets have categories, queues and canned responses; submissions have devices and repair types. They are separate modules and either can be switched off. A ticket’s type is Incident, Service request, Problem or Change.

Problem. A ticket of type Problem: the desk’s record of the cause behind repeated incidents, with a root cause and a workaround. Incidents link to it with Was caused by. See problems and known errors.

Known error. A problem whose cause and workaround are understood, marked as such. Its workaround shows on every incident it caused.

Major incident. A ticket that owns an outage many people report. The reports hang under it, each requester is told once, and the school sees one notice on the portal and kiosk, where it is called a known issue. See major incidents.

Change. A change record: scheduled work with a plan, a window, a risk, an approval and a review. A ticket of type Change is somebody asking for one. See changes.

Security incident. A built-in ticket category for phishing, a taken-over account, ransomware or a stolen device. It goes to the school’s Security department, which only its members and administrators see. See security incidents.

Self-approved. An approval somebody gave their own change or purchase. It is refused unless the school allows it, and when allowed it is marked on the approval and in the audit log.

Repair type. What kind of repair it is, defined by you. Each carries a coverage.

Coverage. Who pays: warranty, insurance, or chargeable. It appears when the person lodges, and it is how cost analytics splits spending.

Loan. A spare device lent to somebody, usually while theirs is being repaired. Loans have numbers, live in groups, and can be pulled automatically from an MDM smart group.

Loan group. A pool of loan devices with its own kind and numbering, such as Loan Laptops or Staff Loaners.

Charge. What a family is being asked to pay for a repair. One person raises it and a second approves it. See damage charges.

Induction. A bulk device handout, usually at the start of a year. A roster is imported, students are tracked through it, and each one’s issued device is recorded.

Stocktake. A physical audit. Work through a location scanning serials to see what is there.

SLA. Response and resolution targets per priority and record type. Missing one marks the work Overdue and raises an alert. The desk says “service level”; “SLA” appears in reports and these docs. See service levels.

Overdue. Open work past its response or resolution target. It is one number everywhere: Home, the Tickets tab and the Service levels page count each piece of work once, and a repair with its ticket counts once, as the repair.

CSAT. The one to five star rating a person can leave on the tracking page after their repair closes. See satisfaction ratings.

Monitor. A scheduled check on a service you care about: an HTTP endpoint, a TCP port, a TLS certificate expiry, a ping, or the heartbeat of a connector agent. See monitors.

Service. Something the school runs and people rely on, such as Wi-Fi, Compass or Printing, with an owner, support hours and a status in plain words. It lists the records it depends on, and each of those shows the service under Used by. A supporting service, such as RADIUS, is for IT only. See services.

Planned work. What a service reads while a change that names it is in progress inside its window, on the desk and on the public status page. See planned work.

Fleet. A rule on a service that takes in every device or network device of a kind, such as every student laptop or every access point at one campus, instead of a link for each. See fleets.

Flow. The school’s automation: a trigger (“When”), optional conditions (“Only if”) and steps, published as versions. Each time it starts is a run. See flows.

Go-ahead. A person’s approval, often with step-up, that a flow needs before it changes another system, such as creating an account. See flows.

Watching. A way to publish a flow so it records what it would have done without doing it. See testing and runs.

Decision model. An AI model that answers a typed question (yes or no, one of a list, or a score) and earns the right to act on its own only through people agreeing with it. See decision models.

Deployment. One running instance of Plugboard. Has an id, a region, a version and a release channel. The unit that gets updated, backed up and billed.

Channel. stable or beta. Beta gets each version earlier. The channel does not cause an update on its own.

Licence. A signed token stating your plan and limits. Your instance checks it locally and offline, so a network outage does not disable the desk.

Telemetry. Count-only usage a deployment reports: how many technician accounts, how many managed devices, which modules are on, what version. No names, no records, no content.

Secrets vault. Where connector credentials live. They are encrypted before they reach the database and decrypted in memory only for the duration of a call.

SECRETS_MASTER_KEY. The key that encrypts the vault and your backups. A database restored without it cannot decrypt its own secrets. Keep a copy somewhere other than the server.

Audit log. A record of covered operations, with configurable retention and no application interface to edit individual entries. Coverage is not complete. See the audit log.