Skip to content
plugboard.appRequest a demo

Start here

Release notes

Written for somebody deciding whether to take an upgrade: what changed, whether it touches the database, and what to do first.

The status panel says which version your deployment is offered and whether it carries a migration, and Settings, Licence & billing shows the offered version under Deployment diagnostics. The full technical record is CHANGELOG.md, which ships with the software and lists every change in every release.

The most recent release is set out in full. Every earlier release is one line, grouped by month, that opens in place.

Plugboard follows semantic versioning: MAJOR.MINOR.PATCH.

ReleaseWhat it changes
Patch 0.6.1 to 0.6.2Fixes only. Nothing to learn, nothing to reconfigure
Minor 0.5.3 to 0.6.1Modules, connectors or features added. Existing behaviour is kept
MajorA change to behaviour you may rely on. There has not been one

A version number is used once. A withdrawn release is replaced by the next number, never reissued.

ChannelWhat it isWho should be on it
stableThe default: releases promoted after testing on betaEverybody, unless you have a reason
betaPre-release builds, ahead of stableA test instance, never a live desk

Set RELEASE_CHANNEL in your .env. If you have never set it, you are on stable. Managed hosting is on stable; see releases and update windows.

A release marked Migration changes the shape of the database. A release without it does not. Migrations are additive: a school that opens none of the added modules sees exactly what it saw before.

Take a verified backup before applying a marked release, one you have confirmed exists and is not empty. The installer takes and checks its own backup before a migration runs, but it does not replace yours. See backups and restore and updating.

0.59.0: Service levels per service, planned work and the Service review

Section titled “0.59.0: Service levels per service, planned work and the Service review”

29 October 2026

Each service can set its own service levels, and its support hours run the clock for the tickets filed under it. Changes name the services they affect, so a service reads Planned work while one is under way, and a major incident can name the service it is about. A service can depend on a Microsoft 365 or Google Workspace service, and cover a whole fleet of devices by rule. Reports has a Service review for the end of term, flows and webhooks hear when a service goes down or works again, and a link to one monitor opens that monitor.

  1. Check each service’s support hours. From 0.59.0 a service’s support hours run the clock. A service set to School days, Weekdays, all year or Around the clock measures the tickets filed under it in those hours, and SLA attainment and the Service review measure its resolved tickets in them too, earlier ones included. Set a service to The desk’s hours if its tickets should keep the desk’s clock. See support hours run the clock.
  2. Give services their own targets where they need them. Under Service levels on a service’s page, service.manage sets first response and resolve targets by priority and record type. Until a service has some, its tickets use the desk’s. Open tickets keep the dates they have; tickets filed under it afterwards use its targets, and reports measure its resolved tickets against the targets it has when they run. See service levels.
  3. Name services on changes and major incidents. change.manage names the services a change affects, and a major incident offers the ticket’s service when it is declared. No key is added: both need service.view as well. See services it affects.
  4. Set fleets and provider services. Give a service such as Student laptops or Wi-Fi a fleet instead of linking devices one by one, and add Exchange Online or Google Meet under Email or video calls. See fleets and provider services.
  5. Add the per-service widgets to a Termly service review board you already have. A board keeps the widgets it was made with. Add Tickets by service and SLA met by service with Add widget, or make a board from the layout again. See Termly service review.
  6. Check who is sent the Service review. It needs service.view as well as report.view, for the schedule’s owner and for every recipient. See Service review.
Services7 changes
  • Service levels per service. A service can set its own first response and resolve targets for each priority and record type, and its support hours run the clock for its tickets. Where it sets none, the desk’s targets and hours apply, and the service’s page shows the desk’s in grey. service.manage edits both from the service’s page. See service levels.
  • A ticket’s service sets its due dates. A ticket filed under a service is dated against that service’s targets and hours. Choosing, changing or clearing the service on an open ticket works its due dates out again from when it was raised, as a priority change does. Resolved and closed tickets keep the dates they were measured against. See when a ticket’s service changes.
  • Provider services. A service can depend on a Microsoft 365 or Google Workspace service that the provider has reported on, such as Exchange Online. While it has an open incident, the service, the Services list and Home say Exchange Online has a problem, which Email depends on beside the service’s own status, which it never changes. See provider services.
  • Fleets. A service can cover a whole kind of device by rule instead of one link per device, such as Chromebooks and laptops at Senior campus or Access points across the school. Depends on says how many records the rule matches, counting those you cannot see without naming them, and a rule over one device type links to the device list filtered to that type. A manager limited to some campuses sets a fleet over their own campuses only. See fleets.
  • Used by on a device or network device includes the services whose fleet takes it in, marked by rule. A fleet never counts towards a service’s status. See used by.
  • Flows and webhooks can start when a service goes down or starts having problems, works again, or is due for review, and webhooks can be sent service.down, service.up and service.status. See service events.
  • The most an AI model is given about a service is its name and status. What it depends on, its fleet and its service levels stay out of every prompt.
Changes and major incidents4 changes
  • Changes name the services they affect. A change lists each service with its owner and support hours, and says whether the window falls inside them. A change that links a monitor, network device or device offers the services that depend on it or whose fleet takes it in, and adds none by itself. See services it affects.
  • Planned work is a status. While a change that names a service is in progress inside its window, the service reads Planned work on Services, its page, Home and the public status page. See planned work.
  • A major incident names a service. Declaring one offers the ticket’s service, and an open one can change or clear it. While it is open the service reads Down, and the service’s page links to it. See naming a service.
  • What did we change? on a service lists the changes in the last 72 hours that name it or something it depends on, its fleet included, and says which part. See what did we change?
Reports4 changes
  • Service review, under Reports, Operational reports: for each service in the period, its incidents and requests, the hours it was down and its uptime from the monitors that count, the targets its tickets met, how the changes that named it went, and its open problems and known errors. Open it from a service’s page for that service alone, and schedule it like any report, at the end of each term if you wish. It needs service.view, and is worked out for each person it is sent to, inside their own campuses and departments. Ask cannot run it. See Service review.
  • SLA attainment by service. SLA attainment can group by service. A service your campuses do not use is counted under Other services, never named. See the reports.
  • Problems by service. Open problems can be grouped by service, and Issue insights shows issues by service beside each one’s open problems and known errors. A problem counts for the service it is filed under and for the services of the incidents it caused. See issue insights.
  • The Termly service review layout adds Tickets by service and SLA met by service. See Termly service review.
Also fixed2 changes
  • A link to one monitor opens that monitor on Monitors, not just the list: from a service’s Depends on, Home’s Service health, an alert, a change’s connected records, a flow’s subject and the evidence for a reported outage. See alerts.
  • The Service field of the tickets data named services on campuses the reader does not work at. It counts them under Services you do not have access to. See report boards.

0.24.0 to 0.58.0

0.58.0Services and security incidentsMigration

29 October 2026. ⚠ Migration. Take a verified backup before upgrading. Two migrations. One only adds: the tables for services and what each depends on, a service on every ticket, empty to begin with, and documentation bound to a service. One writes to existing rows: each school that saved its own list of ticket categories gains Security incident in it.

The desk keeps the school’s services: Wi-Fi, Compass, Printing and the rest, each with an owner, support hours, campuses and the records it depends on, a status from its monitors or from a person, and the tickets filed under it. Security incidents go to a private Security department, and a person’s Overview holds their devices, loans, repairs and tickets. Devices read In service everywhere, a loan whose device is not in hand cannot be lent, and the rest of what the 0.57.0 retest found is fixed.

  1. Choose where security incidents go. Until somebody with departments.manage does, security incidents stay on the ICT desk. In Settings, Ticket settings, Queues & classification, choose Create Security department or an existing department under Security incidents, then add the people who handle security in Settings, Departments. See security incidents.
  2. Give Manage services to whoever looks after services. service.view is added at start-up to the built-in roles that can view tickets. service.manage is the Owner’s to begin with; give it to others in Settings, Roles. It makes an account a Business seat. See the permissions.
  3. Add your services. Under Service desk, Services, add the services people rely on, or start from a monitor with Make a service from this monitor. Give each the other names staff use, so tickets that name them are filed under them. See services.
  4. Pick saved device status filters again. A report board filter saved on the device status “Active” needs picking again as In service. See report boards.
  • Services, under Service desk next to Changes, lists the school’s business services, with supporting services such as RADIUS below them. Each has an owner, support hours, campuses, the other names people use for it, a criticality and a review date. service.view sees them and service.manage adds and edits them, within the campuses a manager holds. See services.
  • Depends on and Supported by. A service lists the monitors, network devices, devices, printers and other services it depends on, and the contracts and suppliers behind it. A record the reader cannot open is counted, never named, and a service cannot depend on itself through another. See depends on and supported by.
  • Status in plain words: Working, Having problems, Down or Not checked, from the monitors that count towards it. A person can set it with a message for up to 24 hours, renew it or clear it, and their status wins until it ends. See status.
  • Used by. A monitor, network device, device or printer shows the services that depend on it, and Make a service from this monitor starts one from a monitor. See used by.
  • A ticket’s service. A ticket that names exactly one service, by any of its names, is filed under it, and its Service row says what matched, such as Matched on “Wi-Fi”. Several matches are offered on the ticket instead, and a person’s choice is never overwritten. See a ticket’s service.
  • Home and the status page. Home’s Service health shows services first, then any monitor that belongs to no service. The public status page lists the services marked public, with their status, a person’s message and 90 days of uptime where a monitor counts towards them. A status page with no public services is unchanged. See services on the page.
  • Runbooks, reviews and reports. A document bound to a service shows on it and in the documentation of every ticket filed under it. A service is reviewed every three months to begin with, its owner sees a due review in Needs you, and Mark reviewed sets the next date. Report boards count tickets by Service. See reviews.
  • Services and what they depend on are never sent to an AI model.
  • Security incident is a built-in category, and words such as “phishing”, “hacked”, “ransomware” or “stolen laptop” choose it. See security incidents.
  • Settings, Ticket settings, Queues & classification asks where security incidents go: Create Security department, whose only member is the person creating it, or choose an existing department. Setting it needs departments.manage, and every change is in the audit log. See ticket settings.
  • Handed to Security. An incident from the portal, email or Teams goes straight to Security, and so does one raised by a member of Security or an administrator. Anyone else with ticket.update who raises one hands it over as it is raised, and one who recategorises a ticket is asked first. The ticket then leaves their sight: Handed to Security. You will not see this ticket again unless you are added to Security. Anything already sent about it stays where it went. See handed to Security.
  • The audit log records each hand-off as Ticket handed to Security, with the ticket number, the departments and what triggered it, never the ticket’s contents. Administrators see every security incident. See the audit log.
  • Flows, ticket buttons, an accepted AI suggestion and re-triage hand off the same way. A flow run stops at the hand-off and records its remaining steps as skipped. See testing and runs.
  • The Security desk shows how many tickets were handed to it in the last 30 days. See the Security desk.
  • A server without the restricted database role keeps Security incident as an ordinary ICT category, and Ticket settings says so. See where security incidents stay on the ICT desk.
  • A person’s Overview holds the everyday record: their devices with Check MDM, active loans with Return, repairs, open tickets and recent activity, in that order. A section with nothing in it is left out, and a long list shows five rows with Show all. The Devices, Loans & repairs and Tickets tabs are gone; Account & groups, Purchases and Kiosk sign-ins stay, and a person with Overview alone has no row of tabs. See the person page.
  • Links to a person’s #devices, #loans, #repairs or #tickets, and the People list’s “more” lines, open Overview at that section with every row shown. See links to a section.
  • The side panel holds Details, Staff details, Experience with IT, Flows and Notices, so a student’s devices, loans and repairs appear once, on Overview. See the side panel.
  • Devices read In service everywhere: the device list and its filter, the summary beside the list, the school map, reports, flows and the mobile app. The device CSV keeps ACTIVE, which the import reads. See devices.
  • A loan whose device is On order, Lost or Retired shows as unavailable. It cannot be issued, the kiosk and Ask never pick it, and Home’s Loans available leaves it out. See loans.
  • No requester in the requester picker takes the requester off a ticket, with Undo. See the column beside the conversation.
  • Editing a change, work or an improvement offers Campus. Work in a project keeps the project’s campus, and work with bookings cannot move. See planning a change.
  • A report board asks for its data once when it opens, rather than twice.
  • Months read Oct 2026 in report tables, charts, board legends and report emails, while CSV files keep 2026-10. Repair turnaround groups repairs by the school’s own month. See the reports.
  • A service review, such as the termly review, cannot be marked held before its date. Until then the page offers Move to today, and the date reads Planned for. See service reviews.
  • Led by on a service review reads Not set when nobody is chosen.
  • The connected records search says what each kind is searched by, and fits the narrow side panel.
  • An improvement shows the reviews and changes that link to it. See on a record’s page.
  • A ticket with no summary, such as a seeded, imported or connector-raised one, offers Prepare a summary while an AI model is connected. See what the AI does here.
0.57.0Suppliers, support tiers, change freezes and termly service reviewsMigration

28 October 2026. ⚠ Migration. Take a verified backup before upgrading. Six migrations. Three only add: a support tier on every ticket, starting at first line; the Spare and On order device statuses; and supplier records, with an empty supplier on devices, software contracts and tickets. Three write to existing rows: each school gets Waiting on supplier straight after its own Waiting on requester, with the statuses after it moving down one place and every name, colour and switch kept; each ticket’s reopen count is filled in from the audit log, counting every return from resolved or closed; and an unanswered ticket with no requester, other than an email, loses its response target, and its overdue flag where only that target could have set it. Its resolve target stays.

Tickets can wait on a supplier with the clock stopped, and move up and down the school’s support tiers with a reason. Suppliers have records of their own, linked from the devices, contracts, repairs and tickets they hold. A change in a freeze waits for an approver’s written reason, Changes has a month calendar, and an outage lists what changed before it. Reports measure first contact resolution and the reopen rate, Improvements keeps the improvement register and the service reviews, and the Termly service review can go to school leadership on the last day of each term.

  1. Have a change approver record the reason for changes in a freeze. A reason written on a change before 0.57.0 does not count. A normal or standard change in a freeze moves to Approved or In progress only once somebody with change.approve records it with Record why it cannot wait. Emergency changes are not held. See freeze periods.
  2. Name your support tiers. In Settings, Ticket settings, Queues & classification, rename the tiers and give each a queue or a person if escalating should hand the ticket over. Left alone, every ticket is on First line and Escalate moves the tier only. See support tiers.
  3. Add your suppliers. Under Assets & stock, Suppliers, add the companies you deal with, and choose the repair vendor connector for your repair vendor. Roles with stock.view see the page and stock.manage keeps it; no role gains or loses a key. See suppliers.
  4. Mark your spares. A spare recorded before 0.57.0 reads In service and unassigned, and stays that way until you set it to Spare on its device page. Replacing a device offers it either way. See spare and on order.
  5. Check your term dates. End of each term report emails and Add term starts and ends in Change rules read them. See term dates.
  6. Rename Waiting on supplier if your desk says it differently, in Settings, Statuses & fields, Ticket mappings. It stops the clock whatever it is called. See statuses & fields.
  • Waiting on supplier is a ticket status, straight after Waiting on requester. It stops the service level clock the same way, so the days a part spends in the post do not make the desk late, and the portal shows the requester Waiting on a supplier. See waiting on a supplier.
  • Support tiers. A ticket sits on a support tier: First line, Second line and Third line, or up to five of the school’s own, each with a queue and a person when escalating should hand the ticket over. Escalate and De-escalate on the ticket move it one tier and say what will happen, and going up asks why. See support tiers and escalation.
  • The person a ticket is escalated to is told in their notifications, the move and its reason are in the ticket’s history and the audit log, Filter on Tickets has Support tier, and reports count tickets by tier.
  • A first response is owed to somebody who asked. A ticket with no requester, raised by a monitor, a flow or a technician for themselves, has no response target and never goes red for a reply nobody is waiting on. It keeps its resolve target, and setting a requester starts the response target. Tickets saved with a response target nobody is owed lose it in the upgrade, so they leave Overdue. See service levels.
  • A ticket’s brief can suggest Waiting on supplier as a next step.
  • Describe a filter reads most sentences at once. The list’s own words cover the everyday ways of saying them, such as “assigned to me” or “with no owner”, so “unassigned repairs ready for collection” applies straight away instead of after 10 to 40 seconds. Anything else is read by the school’s AI for filters only and stops after 8 seconds, and a miss names the words the list does read. See filtering the page.
  • A change in a freeze waits for a reason. A normal or standard change whose window touches a freeze period moves to Approved or In progress only once a change approver records why it cannot wait, with Record why it cannot wait on the change. The reason is kept with who and when, and moving the window clears it. See freeze periods.
  • Emergency changes go ahead in a freeze, flagged on the list and the change, with the freeze named in the audit log.
  • Settings, Change rules holds freeze periods, standard changes and self-approval. Add term starts and ends makes freezes for the first and last weeks of each term from the school’s term dates. See change rules.
  • The change calendar. Changes has List and Month tabs. Month shows a month of change windows with the freeze periods shaded, and List shows the freezes to come with how many changes fall in each. See the Changes page.
  • What changed before an outage. A major incident, an incident about a monitored service that went down, and a monitor that is down list Changed in the last 72 hours, worked out by rules from the records. The monitor’s alert says the same to people who can see changes. See changes near an outage.
  • A change lists Incidents since this change, and links the monitored services it touches under Connected records.
  • First contact resolution and Reopen rate are built-in reports, by month, queue, record type or campus. First contact resolution is the share of incidents and service requests fixed with no more than one reply from the desk, never reopened and not raised again; the reopen rate is the share that came back inside the school’s reopen window. See first contact resolution and reopen rate.
  • Both are measures on the tickets data, so report boards and Home widgets show them with a goal and a comparison. Returns before 0.57.0 are counted from the audit log.
  • Termly service review is a board layout for the end-of-term review with school leadership: tickets raised, SLA met, first contact resolution, reopen rate, change success, satisfaction and repair turnaround, then volume and SLA by type, top problems and changes by outcome. See Termly service review.
  • End of each term in scheduled emails sends a report or a board on the last day of each term in the school’s term dates, covering the term. See end of each term.
  • Improvements, under Knowledge & reports, keeps the improvement register (Proposed, Approved, In progress, Done or Not doing, each with an owner, a review date, the expected benefit and the result) and the service reviews held with school leadership, with who attended and the actions agreed. Both link to the problems, tickets and changes behind them. See improvements and service reviews.
  • The report builder reads Changes: type, risk, status, outcome, campus and success rate. The tickets data includes Support tier.
  • Suppliers, under Assets & stock, keeps who the school buys from, claims warranty through and waits on: contacts, support hours, the supplier’s own response and resolve targets and the school’s account number. A repair vendor connector is one supplier, which brings its cover agreements. See suppliers.
  • A device, a software contract and a ticket each name their supplier, and a repair shows the one it is with: its cover agreement’s vendor, the repair vendor or the device’s supplier. A ticket offers the supplier list while it is Waiting on supplier.
  • Spare and On order device statuses. A spare is in stock and ready to issue; a device on order is bought but not here yet. The status is set in place on the device, and the Devices filter, the summary beside the list and the field app know both. See spare and on order.
  • A spare laptop, Chromebook or iPad offers Add to the loan pool, which opens Register loan on Loans with its serial filled in.
  • Fleet figures leave devices on order out, and Fleet age & warranty shows spares on hand by type, with the count on order beside the fleet. Neither is a managed device on the licence. A stocktake names a device on order that turns up rather than counting it.
  • Replacing a device on a repair offers spares first, and an old device kept as a spare is marked Spare.
  • On a light repair desk, Statuses & fields lists the four repair statuses in use, with Show the 6 not in use to offer another. See statuses & fields.
  • A ticket page reads its major incident once, and My time, Your account and Service level targets each ask for their data once.
  • The inspector on Settings, School map grows with what is selected instead of scrolling inside a box, and choosing a flow template on New flow shows the whole flow.
  • A flow template lists each app it needs once: the Staff leaver template named Microsoft Entra ID or Google Workspace five times. An app reads as connected only when every step that needs it can run.
  • Reordering statuses in Statuses & fields is no longer refused while a closed ticket has a required approval still open.
0.56.1Fixes from a full check of 0.56.0

25 October 2026. No migration.

We ran a full check of 0.56.0 and fixed what it found. Problems is a tab on Tickets rather than a page in the menu, pages load with fewer requests, Home’s widgets fit their panels, connector logos are back, and a change or purchase asks the approvers you choose.

  • Problems opens straight away from Tickets. Choosing the tab left the list showing Tickets, dimmed, for about four seconds. The list changes with the tab, and coming back to Tickets lands on the tab you were on.
  • Open flow and document tabs no longer slow every page. Each flow tab kept open took about a second on every page load just to show its name. Flow and document tabs are named with the other tabs, and reloading a page no longer adds a read to an open document’s count. See workspace tabs.
  • Pages ask for things once. Every page asked for its data twice, and parts of one page asked for the same settings separately. Ticket, device, person and document pages make a fifth to a third fewer requests.
  • Opening Security after ThreatLocker requests arrive is quicker.
  • Every widget fits its panel. Needs attention had its rows on the panel’s left edge and a scrollbar near its foot. Its rows sit inside the panel on hairlines, each with its count, and its heading drops the severity legend. A panel is as tall as what it holds, not as the tallest panel in its row, and nothing scrolls inside a panel. See Home.
  • Loans & equipment shows the register’s size once.
  • Underlines clear the descenders. A link’s underline ran into the tails of g, p, q and y. Every link draws the same thin line, broken around them.
  • Connector logos are back in Settings, Connectors, Add a service, each provider’s page and the flow action picker, in their own colours at one size. See configuring a connector.
  • Settings home shows each page’s icon beside its name, the same icon the page uses elsewhere. See Settings.
  • Problems is a tab on Tickets, after All open, with its count, and the queue remembers it like the other tabs. It is out of the menu: Search or ask finds it by “problems”, “known error”, “root cause” or “workaround”, and a link to the old Problems page opens the tab. See the Problems view.
  • Changes and purchases go through an approval request. Request approval asks the approvers you choose, the page says who it is waiting for, and the last approver’s Approve moves the record to Approved. In 0.56.0 it changed the status only, so nobody was asked and Approve was refused. See Changes.
  • Ask answers queue counts exactly. “How many tickets are overdue?” is answered from the desk’s records, matching Home, and a question being asked no longer shows as a search with no results. See Ask and AI features.
  • The ticket page says each fact once: no empty summary band, the requester’s tone only under Requester tone, and the tone’s reason names its window, the last 30 days. The overdue clock stays at the top of the side column as it scrolls.
  • On the Tickets and Problems lists, the tone mark no longer cuts names and roles, Due wraps instead of being cut, and the bulk actions wrap within reach. A problem with no requester shows when it must be fixed, not a reply clock.
  • Repairs’ next step and technician columns fit their words, rows no longer show through the Loans toolbar, and Changes and Charge approvals stop repeating their column names.
  • The flow editor draws its steps as one line, from the trigger through every step. See the spine.
  • The New ticket dialog and Describe a flow drop their explanations. Describe a flow keeps what you wrote if you leave while a draft is being written.
  • Describe a filter on Devices reads location and warranty straight away, such as “devices in the Library” or “expired warranty”, instead of asking the AI model.
  • The record picker finds a ticket or repair by its number: “253”, “#253” or “R-55”.
  • Deleting a record closes its tab.
  • An induction keeps a device’s serial. Issuing or collecting a device whose serial starts with S could read it as an Apple box barcode and drop the S. The serial the desk already holds wins. See inductions.
  • A device’s owner and the card checker show the person’s year and tutor group.
  • Date retired defaults to the school’s day, not the day in UTC.
  • A school with Active Directory and Entra ID both connected sees its licence totals instead of a refusal.
  • Devices’ columns fit at 1440 px, a person’s open tickets carry the queue’s status ring and due clock, a person’s side rail scrolls with the page, and Disposals shows every year’s count.
  • Software checks the licence position from the header. Field capture leads with loading stocktakes, and a disabled field looks disabled.
  • The check-in card is the school’s card, as on the card checker.
  • Fleet, Network, Printers and Accounts fit a phone.
  • A Temporary access bundle made by mistake can be deleted, unless someone has asked for it; then it can only be turned off.
  • Passwords & links says when the school’s settings could not load, rather than showing the built-in presets as if they were the school’s.
  • Service level targets no longer carries a list of overdue repairs.
  • Add department starts on an add-on the school has, and says which are not in the licence.
  • An open notification message stays in the address, so a reload keeps it open.
  • Escape leaves Add a service on Connectors. Connectors, Account templates and the school map’s inspector fit their space, and every settings row menu is the same outlined button.
  • Print labels carries the same name everywhere, Settings home included.
  • A student’s loaner is one of their devices in Report a problem and Book a repair, marked On loan.
  • The status page gives uptime in plain words.
  • The rating page keeps five stars on one row on a phone, and a parent’s Devices and loans panel is as tall as what it holds.
  • Kiosk screens underline their ways in, and say in words when a setup code is refused.
  • Setup names the desk after the school and shows who is signed in, with Sign out.
  • On Visitors, typing a name and choosing Next picks that visitor, or adds them when there is no match.
  • Reports and Costs write money with thousands separators and months in three letters. Experience counts every ticket and shows no figure where no tone was read.
  • Logs give statuses in words, the filter for what the desk changed by itself reads Changed automatically, and the area tabs no longer show counts of only what is loaded.
  • Monitors offer a demo monitor only on one that already is one.
  • Network checks that need a campus agent are left out, with the reason, on a network not mapped to a campus.
  • School operations drops subtitles that restate the tab, and project work leaves out empty columns and keeps dates on one line.
  • Report board charts fill their card.
  • In dark mode, people’s initials are neutral and a building’s offline badge is readable.
  • On a phone, header actions that are only icons sit beside the title, and a wrapped stepper has no stray chevron.
  • The wallboard map keeps its 3D view after one dropped tile.
0.56.0Search or ask, problems and changes, and repairs fitted to the schoolMigration

24 October 2026. ⚠ Migration. Take a verified backup before upgrading. Seven migrations. Six add to the database or change its defaults: a loan group can hold returned devices until they are erased; a problem ticket records its root cause, workaround and known error; a fresh school starts with two-factor for administrators and a 60-minute sign-out, while an existing school keeps its policy; a licence can be priced per student; every role holding a School operations key gains the matching change key, so nobody gains or loses access; and service level targets can be set by record type, with every existing target applying to every type. One removes existing data: the stored tone and AI welfare reads on tickets whose requester is a student, a parent or nobody on file. The word-list safeguarding flag stays.

The desk is redrawn around the school: one side menu in the school’s colour, one place to search or ask, Home, and a ticket page with everything beside the conversation in one compact column. The service desk gains problems, major incidents and change records, Repairs fits how the school provides devices, a licence can be per student, and sign-in, support access and backups start safer.

  1. Give the change keys to the roles that run changes. Change records have their own permissions, change.view, change.manage and change.approve. The upgrade gives each to every role that held the matching School operations key. A role that runs changes without one of those keys needs the change keys added in Settings, Roles. See Changes.
  2. Answer How are student devices provided? in Settings, Setup wizard. The answer fits Repairs to the school: cover agreements, damage charges, vendor booking and the statuses, each a switch afterwards in Settings, Statuses & fields. Until it is answered, Repairs is unchanged.
  3. Review Settings, Security. An existing school keeps its policy, so check who must use two-factor and when staff are signed out. The staff password rule applies the next time each password is set; existing passwords keep working. See sign-in security.
  4. On managed hosting, grant support access when you want our help. It is off until an administrator grants it, for a set time, in Settings, Compliance. See compliance answers.
  5. Self-hosted: watch the script policy, then enforce it. The script Content-Security-Policy is sent report-only, unless EMBED_ORIGINS is set, when no reports are sent at all. When plugboard_csp_reports_total stays quiet through normal use, set CSP_ENFORCE=1. See environment variables.
  6. Choose what happens when a loan device comes back. Each loan group can Hold it until it is erased, in Settings, Loan groups. A group left alone lends it again straight away, as before. See loans.
  • One side menu in the school’s colour, under the school’s own name and crest, on the left or right. Below 1024 px it is a drawer under a band across the top. See finding your way around.
  • Menu colour and Highlight, in Settings, Branding and the setup wizard, paint the menu and its selected item. See branding.
  • The menu groups pages as Service desk, Assets & stock, People, Operations and Knowledge & reports, with Home first and Settings at the foot.
  • The Admin area is Settings. Settings home lists what needs attention and every settings page you can open, in four groups. Several pages have plainer names: Features is Modules, Licence is Licence & billing, SSO is Sign-in & SSO, Tickets is Ticket settings, SLA is Service level targets, Messages is Notifications, Print labels is Labels, Access & requests is Access, Passwords and links is Passwords & links and Desk setup is the Setup wizard. Their addresses are unchanged.
  • Search or ask at the top of the frame (Ctrl K, Cmd K or /) is the one way to ask the desk. An exact answer from the desk’s records shows in place; anything else opens the Ask panel, which keeps its history. See Ask and AI features.
  • The Assistant page, the assistant button and the prompt boxes on list pages are gone. Describe a filter on Tickets, Repairs, Devices and Loans, drawn while the school’s AI is on, takes the place of page filtering.
  • The Style preference is Density: Comfortable or Compact, with the school’s default set in Settings, Branding. Where the menu sits is Left or Right.
  • A row of tabs that does not fit wraps onto a second line on a desktop; on a phone it scrolls.
  • People’s roster has Everyone, Students, Staff and Parents tabs beside Directory accounts, and a person’s page keeps their details, devices and loans in a side rail. See people.
  • The Dashboard is Home, greeting you by name with the date. See Home.
  • Needs you and Spotted are Home widgets: what is waiting on you, and patterns such as similar tickets that may be one outage.
  • Overdue is one count, the same on Home, in the queue and on report boards. A repair and its ticket count once.
  • Home’s recent activity links to Set automatically on Logs: what the desk set by itself, each undone on its record.
  • Headline figures are one strip: Home’s Summary metrics, figure and gauge widgets side by side on a report board, and the summaries of Issue insights and the operational reports. See reports.
  • A comparison is said in words, such as “Up 12% on the previous 30 days”, with no arrow and no red or green.
  • Charts draw their series in shades of one ink, with the series a chart singles out, such as late work, in the accent colour.
  • The ticket’s details are one ruled list beside the conversation, each value its own control, with impact, urgency, estimate and dates under More. See the ticket queue.
  • Related holds linked records and tickets as rows, with one Link menu for what is not linked, and the desk’s other context for the ticket under them.
  • The composer’s tabs are Reply and Internal note, sending with Send or Add internal note. See replies and internal notes.
  • Log time in the composer opens the time field, the +5 to +1h chips and the work type. See time tracking.
  • Watchers opens People kept informed, and Display ends the filter row on Tickets.

Problems, major incidents, changes and service levels

Section titled “Problems, major incidents, changes and service levels”
  • Problems in Service desk. Select tickets and choose Raise a problem; the problem records its root cause, workaround and known error, and lists the incidents it caused. Resolving it can resolve its open incidents with one reply. See problems and known errors.
  • Declare major incident on a ticket puts up a known issue for its campus. Add to major incident hangs other tickets under it and sends each requester the same update. See major incidents.
  • Changes in Service desk: Normal, Standard and Emergency changes with a risk, freeze periods, and an outcome recorded at review. A ticket of type Change offers Create change record. See Changes.
  • Nobody approves their own change or purchase unless the school allows it, and then it reads Self-approved. An approval is Declined with a note.
  • Service level targets are set per priority and record type, so an urgent incident and an urgent request can run different clocks. See service levels.
  • A ticket resolved inside its target reads Met, and a paused clock reads Clock paused.
  • Reports gain Open problems and Change success rate, and SLA attainment breaks down by type.
  • The setup wizard asks How are student devices provided? The answer decides cover agreements, damage charges, vendor booking and the statuses. A light desk works with four: Open, With vendor, Ready and Closed. See submissions.
  • Turning cover agreements or damage charges off takes their pages out of the menu, and their routes refuse.
  • Likely outcome shows only when at least 8 of the school’s own similar closed repairs back it.
  • Send to a vendor is offered only while a repair-vendor connector is on and vendor booking is on.
  • A school can ask for an optional photo of the damage when a repair is lodged at the kiosk or in the student portal. A repair lists its attachments with the lodgement photo first.
  • A loan group can hold returned devices until they are erased. Loans shows them as Waiting for erase, with Erase and Erased by hand, and no lend path accepts a held device. See loan groups.
  • A licence can be priced per licensed student. Settings, Licence & billing shows the licensed students, where the count comes from and how many are active in the student system. See licence.
  • On a per-student licence, staff seats are counted, never priced.
  • Usage reports carry the count of active students from the student system, for the re-count at renewal. It is a count only, and never billed on.
  • Settings, Security sets who must use two-factor, the password rule, passkeys and when staff are signed out. Changes are reviewed in one dialog and need you to confirm it is you. See sign-in security.
  • A fresh school requires two-factor for administrators and signs staff out after 60 minutes.
  • Staff passwords need 14 characters, or 8 where a second factor stands behind them, and never one from the common-password list. The list is checked without a network call.
  • Sign-ins, refused sign-ins, sign-outs, a password change, an authenticator turned on or off and a passkey sign-in are recorded in the audit log. See audit.
  • The web app sends a script Content-Security-Policy, report-only until CSP_ENFORCE=1. Framing protection stays enforced. A production build sends no reports, and reports never count against any address’s request limit.
  • Request limits count per route and expire on time, so a school whose staff share one internet address is never refused for normal use.
  • Settings, Security says in one line what passkeys need when the desk’s web address is not set, with a link to setting it.
  • Support access is off until an administrator grants it: for 24 hours, 3 days or 7 days, with a reason, and restoring backups only when included. End access now stops it at once, and Support activity lists what support read. See compliance answers.
  • On managed hosting, going live seals the school’s master key to an offline escrow key our panel cannot open, and trims the panel’s copy. See secrets and keys.
  • A school moving from managed hosting to its own server gets its master key ring by hand, after a written request from its domain and a call back to its published number. See moving between hosting models.
  • Managed deployments take backups from first boot, nightly at 03:00, kept for 90 days. A schedule an administrator saved is never changed.
  • Bring back offsite backups lists the school’s offsite archives after a rebuild, checks each against its upload checksum, and records it as a run to verify and restore. See backups in the app.
  • Wonde reads one school’s students, current staff, roll classes and staff photos, read only, with a school token collected straight into the connection. Limited availability.
  • ServiceDesk Plus Cloud raises, reads, notes and closes requests in one portal, for a school moving its desk across. Limited availability.
  • A student system’s first sync, in a school whose people came from somewhere else, waits for Match people: a preview of who matches by username or email, applied in one step. See the first sync of a student system.
  • The roster’s leaver cap counts each type of person on its own, and a pull that is mostly people the source has never seen writes nothing.
  • The Connectors page filters by State, Add connector goes straight to Add a service, and the connector guide is Settings, Connectors, Guide. See configuring a connector.
  • A connector in demo mode carries no label on the Connectors list, and its check reads Passed; its setup shows Use demo data.
  • Printers says which source did not answer and why, and offers Try again when none does.
  • The capability reference covers 152 providers, with the department desks marked Add-on. See connector capabilities.
  • AI reads tone and welfare only on tickets from staff. A ticket from a student, a parent or a sender who matches nobody gets no model call for either, in any mode. The word-list safeguarding flag on a student’s ticket still runs; it is not AI. See sentiment and staff experience.
  • With the school’s AI off or no model connected, nothing AI-only is drawn. Rules-only help, such as exact answers and related tickets, stays.
  • AI output is named in words: Summary, Suggested, Draft, Read by the AI model, Set automatically.
  • Describe a flow in the flow editor and Describe it on a new flow build a flow from a sentence. See building a flow.
  • Managed AI has run through Cloudflare since 0.25.0 (9 October 2026): embeddings and Clef decisions on Cloudflare’s network, with no region pinning, and chat on Anthropic’s Claude Haiku 5.5 in the United States. That replaces the DigitalOcean arrangement 0.19.2 describes. See what we process.
  • Validation runs on zod 4.6.7, which fixes a memory exhaustion advisory for long lists in a request (GHSA-mrhx-c7xc-m3w5). Validation messages and the schemas sent to AI providers and connectors are unchanged.
  • undici 7.30.1 and 8.12.2, body-parser 2.4.0, multer 2.5.0 and nodemailer 10.1.4 fix denial of service and other advisories (GHSA-xjj6-f33q-929c, GHSA-27r3-jxmh-p828, GHSA-q7qp-rjg7-q26m and others).
0.55.0Tighter sign-in, account recovery and device commandsMigration

23 October 2026. ⚠ Migration. Take a verified backup before upgrading. Three additive migrations let a ticket linked to another system keep the status that system last reported, let an authenticator code be used only once, and record who was signed in when a portal or Teams ticket was raised. No existing value changes.

A security, correctness and interface review of 0.47.0 to 0.54.0. Every finding was confirmed by a separate check before it was fixed.

  1. Grant identity.tap.issue to the roles that issue Temporary Access Passes. A pass needs its own permission from this release, and no role holds it after the upgrade apart from Owner. Until a role is given it, the pass step of a joiner plan is refused. See Temporary Access Passes.
  2. If staff sign in with the school directory, check their email addresses. Staff directory sign-in finds the directory entry by the whole email address, matched against mail or userPrincipalName. A staff member whose Plugboard email matches neither is refused until one of them is corrected.
  3. Keep API and webhooks on if anything uses an API key. Every API key stops working while that module (module.integrations, in Admin, Features) is off, including the key a mail gateway uses to deliver mail to the desk. Each REST route also follows its own module: /api/v1/devices needs Stocktake (module.assets) and /api/v1/submissions needs Repairs (module.repairs).
  4. Find the school’s device command stop in Admin, Features. Let the desk send device commands moved there from Admin, Connectors, Device management. It needs feature.manage.
  • Ending a session ends it at its next request, not when its access token expires. That covers Sign out everywhere, a password reset and a reused refresh token.
  • An authenticator code is accepted once.
  • With passkeys turned off for the school, a passkey no longer counts as the second factor.
  • Confirming it is you for one action can no longer be used to sign in.
  • An administrator’s passkey reset signs the person out everywhere.
  • An OIDC or SAML sign-in must finish in the browser that started it.
  • The first-run setup link stops working once it has been used.
  • Sign-in limits count the visitor’s own address behind Cloudflare.

Temporary Access Passes and account recovery

Section titled “Temporary Access Passes and account recovery”
  • Each person can issue up to 10 Temporary Access Passes an hour. The next one is refused and an administrator is alerted.
  • The hourly limits on MFA reset, password reset, backup codes, unlock, mailbox grants and passes hold when several requests arrive at once.
  • Account recovery from 0.54.0 checks more:
    • Their signed-in portal or Teams request counts only when the requester signed in to raise that ticket and is the account being reset.
    • Plugboard’s own Active Directory service account is refused.
    • An account whose Plugboard user holds permissions the technician does not is refused, for resets and for passes.
    • Turning on Allow account recovery for Okta, Duo, JumpCloud or Active Directory needs a whole-school administrator.
    • Reset notices go to the person the account is linked to. The dialog promises a manager’s email only for Microsoft Entra and Google Workspace, which name managers, and the audit log records when no manager was told.
  • Okta and Duo accounts can be read again without role permissions while account recovery is off.
  • Let the desk send device commands also stops locks and check-ins sent by flows, device fixes and the restart step of an access request.
  • A fully automated flow can restart, shut down or check in a device, but never lock, disable, re-enable or clear a passcode. Those always ask a person.
  • A fully automated flow’s commands count toward its owner’s 30 an hour.
  • Wipe and local administrator password confirmations accept a passkey, and require one where the school asks for passkeys on sensitive actions. Five wrong answers within 15 minutes stop them for that person for 15 minutes. The requester is checked again when the wipe is sent.
  • Intune no longer offers Lock for Windows PCs, which Intune cannot lock remotely.
  • Mosyle can clear passcodes, Jamf Pro Mobile locks reach the device, and Chrome Enterprise assigns only exact matches.
  • Syncing a person’s devices works with more than one device management service, and for staff limited to a campus.
  • Admin, API and webhooks lists only the keys whose permissions, desks and campuses you hold yourself, and only those can be changed.
  • Resetting a password at the kiosk by card needs a session that began with a card, a password or single sign-on. A session opened with a typed username cannot, because a card number is printed on the student ID.
  • The kiosk follows the Repairs, Loans and Stock module switches. A repair lodged there lends a loan laptop only to somebody who does not already have one out; anyone else is asked to see the desk.
  • An Android kiosk’s hardware attestation is checked along its whole certificate chain, not only its signatures.
  • A campus- or desk-limited administrator creates accounts only in their own campuses and desks, and cannot deactivate, change the roles of or remove an Owner or another campus’s staff.
  • Writing a print release card needs device.manage, and the card and name come from the person’s record.
  • Restricted documents stay restricted in ticket links, flow runs, case tickets, desk alerts, review reminders and the flow builder.
  • Erasing a person’s data for privacy needs user.manage and confirming it is you.
  • Stopping a flow run, or skipping its approval, needs the access its remaining steps need.
  • The assistant cannot write internal notes for somebody without ticket.internal.
  • The list of staff a Staff member school field picks from is sent only to people who can set such a field.
  • A wildcard character is matched as itself in kiosk enrolment serials, visitor sign-out by name and email or username lookups.
  • ALLOW_PRIVATE_EGRESS opens private and loopback addresses, never link-local or cloud metadata addresses.
  • Next.js 15.5.28 fixes a critical remote code execution advisory in image optimisation (GHSA-2464-fhr4-w9xw) and a denial of service in Server Actions (GHSA-p3m5-59mp-jv5r). ip-address 10.7.4 fixes GHSA-rxp7-6hxx-x8q5.
  • The connector agent sends its local credentials only to its own host, its service account can no longer write its program files, and plugboard-agent secret set leaves the secrets file readable by the service.
  • Native installs keep program files owned by root. Release signatures are checked against the release workflow, and the Cloudflare tunnel token is no longer passed on the command line.
  • Backups, restores and the school export keep school field values. A restore no longer brings back credentials or sessions revoked since the backup.
  • Email designs: publishing checks you are publishing the draft you saw, previews no longer count the logo against the sending limit, the daily template limit is counted per school, and the default design passes its own contrast check.
  • Flows: an event start that fails is tried again and set aside instead of dropped, every offer approval completes, a schedule skips the runs it missed while off, and an AI edit keeps a schedule’s filters.
  • Check the area finds the right campus for a ticket with a location, the location picker can unlink a room, and the portal keeps typed text.
  • A ticket linked to another system that staff reopen is no longer closed again by the status sync.
  • Roster syncs can clear a year level or tutor group again, and the first sync after 0.52 no longer reports every student as a mover.
  • Every page was checked at desktop, 1024 px and phone widths, in light and dark. Tables, toolbars, dialogs, filters and empty, loading and error states match, and pages that overflowed at 1024 px or on phones fit.
  • When your access cannot be checked, the page says “Your access could not be checked” with Try again, instead of saying you do not have access.
0.54.0Unlock, password reset and MFA reset for directory accounts

22 October 2026. No migration.

  • Active Directory, Google Workspace, Okta, JumpCloud and Duo accounts have an Account recovery group on the person page. A ticket’s requester card has Help with their account with the same actions. See account recovery.
  • Unlock is offered where the provider locks accounts. Reset password gives a temporary password, shown once, with a one-time link. Reset MFA clears the person’s methods or turns Google 2-Step Verification off. Google can instead issue a fresh set of backup codes, and Duo issues one to three single-use bypass codes that last at most eight hours.
  • Allow account recovery on each connection is off until a connector administrator turns it on.
  • Every reset tells the person by email and text, and a staff member’s manager by email. A student’s manager is not told. These notices cannot be switched off.
  • A reset started from a ticket records how the person was checked: in person, called back on the number on file, vouched for by a colleague or, for a portal or Teams ticket the person raised while signed in, that signed-in request.
  • An account with a directory role is refused on every provider. Each technician can make 10 password resets, 10 MFA resets and 20 unlocks an hour.
  • The ticket’s requester card always shows, with No requester yet and the picker when nobody is set.
0.53.0Directory suggestions in address fields, and a tidier ticket page

22 October 2026. No migration.

  • Typing in People kept informed, a public note’s CC and BCC, delegate addresses and the other address fields suggests people from the directory by name or email, with their year or role. An outside address is still accepted. People search matches email addresses too.
  • On a side rail, the navigation’s icons and labels grow with its width, including while you drag it.
  • The loan preview sets its facts in two-column tiles, names the data source once for each group, and shows storage and battery as meters.
  • The incident proposal card has one headline, one supporting line and a short Why we think this box that names the nearby equipment once. The rest is under Details.
  • On the ticket page, a ThreatLocker request shows once, in the strip above the tabs with Approve and Deny. Ticket details is a compact grid without the requester, and parent, child and related tickets are full-width cards.
  • The parent portal says Your students.
  • The Assistant button stays in the navigation on Field capture, turned off, with a note that the assistant is not available there.
  • Preview panes on Loans, Devices, Tickets and other lists scroll on their own instead of scrolling the page.
  • Hovering the edge of a map pin, button, card or row no longer flickers, and a click near an edge lands.
  • Tabbed pages, such as Flows, no longer leave a gap under the header, and a Modern-style button compresses when pressed.
0.52.0, 0.52.1Term dates, school holidays and figures from connected apps

22 October 2026. No migration.

  • TASS, OneRoster, Aeries and Edumate rosters fill year level, form or roll class and, where the system sends it, campus. People has a Student system campus filter when people carry two or more campuses, a change of campus is a mover event, and flows can test person.campus. The year-level rollover template finds students on these systems.
  • Edumate’s year level and roll class need the STUDENTS_ENROLMENT_INFORMATION_VIEW permission on the token. Without it the roster still syncs, without them.
  • The nightly roster sync keeps a stored year level, tutor group or campus when the student system does not send it, instead of clearing it and raising a mover event for every student. A field the system sends empty is cleared.
  • Sentral, OneRoster, Aeries and Synergetic can offer term dates. Check term dates on Admin, Timetable lists every term that would be added or moved, and Accept writes exactly that. Terms the school entered itself are never removed. Nothing changes term dates on a schedule, and each accepted change is in the audit log with the previous dates.
  • Closed in the school holidays on the SLA working calendar, off until a school turns it on, stops the clock on a staffed desk between terms. Loan reminders are held over the break and go out on the first day of term.
  • Issuing a loan offers End of Term N as the due date when the school has term dates.
  • A ticket’s Service incidents card shows the latest update Microsoft posted on a linked Microsoft 365 incident, with earlier ones folded. Updates never become ticket notes, and a provider recovery never closes a ticket.
  • The assistant can answer “is Outlook down?” from stored service health and the week’s Microsoft 365 message centre digest. The digest holds titles and dates only.
  • Dashboards and report boards can show five school-wide figures from From connected apps: Microsoft Secure Score, staff without MFA, Workspace accounts with 2-Step Verification, Microsoft 365 active users and Microsoft 365 changes to plan for. Scheduled board emails carry the same numbers. Each figure names its source and says when it was last collected.

22 October 2026. No migration.

  • A connected-app figure names its source before its first nightly collection.
  • A reporting period must fall inside the year it is filed under, and the year list always offers next year.
  • With targets counting around the clock, Closed in the school holidays says that the holidays do not stop them, and that loan reminders still wait for the first day of term.
  • The Sentral roster reads a student’s name from the linked person record when Sentral sends one, and from the enrolment otherwise.
  • When device commands are stopped for the school, the refusal points to Admin, Connectors, Device management. A repeated device command is refused with the time in UTC and in the school’s local time.
0.51.0Device commands from one menu

22 October 2026. No migration.

  • The device page’s Remote tools and the ticket’s Context tab show the commands the device’s connector can send, for the record you choose. Each connector declares its own commands, so the menu, flows and the assistant agree.
  • Lock, disable, re-enable and clear passcode ask for a reason. Clearing a student’s passcode also asks for the last four characters of the serial and the ticket or person who asked. Check first runs every check and sends nothing.
  • Intune and Jamf Pro Mobile can lock, restart and check in a device. Each sits behind Allow device commands (allowDeviceCommands) on the connector, which is off until a connector administrator turns it on.
  • Jamf Pro commands for Macs sit behind the same setting, off by default. After upgrading, turn it on in the Jamf Pro connector to keep sending them.
  • On a device Intune reports as not compliant, one button lists up to 20 failing policies. They are read from Intune when asked for and not stored.
  • Let the desk send device commands in Admin, Connectors, Device management stops every device command for the school at once. Each person can send up to 30 commands an hour, and the same command to the same device is refused for a minute after it is sent.
  • Intune and Jamf on and off settings saved as the text “false” read as off.
  • Chrome device commands report a failure when the connector’s setting is off, instead of appearing sent.
0.50.0, 0.50.1Tickets that know where the problem isMigration

21 October 2026. ⚠ Migration. Take a verified backup before upgrading. One additive migration lets rooms carry other names, lets equipment be filed to a room or floor, and records how a ticket’s location was known.

  • An assistant suggests a room for devices, network devices, kiosks and monitors from their names and locations. Each suggestion is accepted on its own, exact matches can be accepted together, and nothing is placed until somebody accepts it. Every accept is recorded in the audit log.
  • Rooms can carry up to 10 other names, which are matched alongside the room’s own name and code.
  • A network site with no campus suggests one, with Use, and says that a network without a campus cannot help match incidents.
  • The ticket page suggests a location from the ticket text, with Set location, and records how the location was known. A ticket raised against fixed equipment, such as a ceiling access point or a wall display, takes that equipment’s room. A location is never worked out from where a person is.
  • The portal request form has an optional Where is it? room picker, limited to the requester’s own campus.
  • When several people report the same problem, equipment that is down in the same room, floor, building or campus counts as evidence. With that evidence an incident can be raised from 3 requesters instead of 5, never fewer than 3. The incident banner names the equipment, where it is and since when.
  • Check the area on a ticket shows the same evidence on demand.
  • Staff limited to a campus see only that campus’s equipment in an incident. Incident proposals waiting from before the upgrade are hidden, and a fresh one is raised if the problem continues.
  • A school with no campuses set up has related tickets grouped across the whole school.

21 October 2026. No migration.

  • The ticket location picker finds rooms by their other names.
  • Check the area asks you to set where the problem is, or to set a category, instead of saying nothing was found.
  • Choosing a room no longer replaces the location text a person typed.
  • A placed item’s marker no longer covers the room’s name on the plan.
  • Ticket history shows typed text exactly as it was typed.
0.49.0Emails in the school’s own lookMigration

21 October 2026. ⚠ Migration. Take a verified backup before upgrading. One additive migration stores email designs, their versions, the school’s own email templates and uploaded email images.

  • Admin, Messages, Design sets one look for every email the desk sends: logo, colours, font, header and footer text, and button style. Check it in light and dark, on desktop and mobile, and as plain text.
  • Changes save as a draft and reach nobody until you press Publish. History restores an earlier version. Colour pairs that are hard to read are flagged, and the worst are refused.
  • Any message can follow the school’s design or change single parts of it. Every system and ticket email is sent through the design, with a matching plain-text part. Images travel inside the email, so opening one fetches nothing. If the design cannot be used, the email still goes, as plain text.
  • Templates holds the school’s own emails: a subject, a message and values for a flow to fill in. The flow step Send email from template sends one, up to 1,000 a school in any 24 hours. Whatever a flow fills in is shown as text, never as a link. An archived template leaves the flow picker, and flows already using it keep sending it.
  • Designs and templates are written with branding.manage. Sending from a flow needs what Send an email needs.
  • The desk name in email footers and subjects comes from branding.
0.48.0, 0.48.1Reorder points for stockMigration

20 October 2026. ⚠ Migration. Take a verified backup before upgrading. One additive migration adds a reorder point to products. No existing count changes.

  • Each product can have a reorder point. A product is low when its count is at or below it, and the Stock page shows “Reorder at N” and when it went low. A product with no reorder point is marked Low under 10, as before.
  • Add product has an optional reorder point, and Set reorder point is in each product’s menu. Setting it at or above the current count warns first.
  • Flows can start on Stock reaches its reorder point, once per drop: it starts again only after the count has gone back above the line and dropped again, however many sales happen below it. Stock is back above its reorder point starts when it recovers. Sales, adjustments, voided sales and CSV imports all count.
  • A product’s count is changed by adjusting stock, which keeps a reason. Changing the count through the product edit is refused with “Change the count by adjusting stock.”
  • The AI flow builder drafts flows for every way a flow can start: tickets, repairs, people, run by hand, schedules, events, another app and another flow. Editing an event or schedule flow with AI keeps how it starts.
  • The repair parts reorder alert starts once when a part drops to its reorder point, and again only after it recovers.

20 October 2026. No migration.

  • Run a flow is in each stock item’s menus, and flow conditions can test Which item.
  • With AI off, Build my flow and Build with AI are disabled with the reason beside them.
  • Saving or cancelling the reorder point dialog leaves nothing in the address bar, so a refresh does not open it again.
  • Renaming a flow updates its tab straight away.
0.47.0 to 0.47.4Calmer pages and a compact ticket toolbar

20 October 2026. No migration.

  • Security, Endpoint inventory opens on all sources at once, with each device’s source named under it. A source that cannot be read is named in a warning while the others still show.
  • Security allowlisting requests are one row each, with Approve and Deny in view at every width. The file path, device and ticket open on hover, focus or tap, with Copy path.
  • The AI brief on a ticket can be minimised to its summary, and the choice is remembered across tickets.
  • Monitors puts Needs attention first, tinted red, or amber when the monitors are only stale or not yet reporting.
  • The device panel shows a status strip (repair, loan, warranty, compliance), one list of properties and a timeline.
  • Documentation keeps the list beside an open document on a wide screen, with a filter and keyboard navigation.
  • On Stock, the product picture starts Record purchase. Change image is in the three-dot menu.
  • Spacing and hover fixes on Security, the ticket side column and card pictures.

20 October 2026. No migration.

  • Page headers are the title and description alone, and cards and panels are plain solid surfaces. Cards do not fade in again on every refresh, and the page fade respects reduced motion.
  • Monitors sums up in one line in the page header, such as “8 monitors: 2 down, 1 stale, 0 paused”. Security sums up in one line under its heading, each part linking to its section, or says “Nothing needs a decision.”
  • Network lists devices as one compact table per network, problems first. Firmware, hardware address, PoE and internet links open in the row. A network not mapped to a campus says so.
  • Time, timer, watchers and work sit in one toolbar on the ticket. Watch is a toggle, and in the narrow side column the labels hide while screen readers and tooltips keep the full names.
  • Device commands show only what the device’s connector accepts. Chromebooks gain Disable and Re-enable, and a command that fails because a setting is off is reported as failed.
  • Lock the ticket’s device in flows locks through Jamf Pro or Mosyle, or disables a Chromebook, with the same approval and audit as the device page.
  • Syncing a person’s devices works on Mosyle and Chrome, and a setting of “false” is read as false.
  • Warranty lookups go to the maker’s connector (Dell, Lenovo, Apple, HP) and say so when none is connected.
  • Email with an attachment over the limit still becomes a ticket, with an internal note naming each file left out.
  • Jira, ServiceNow, Freshservice, Zendesk and Salesforce steps in flows post, link and close as they should. Texts sent by flows leave a delivery record with the outcome only, no number and no message.
  • Printers report jams, open doors and empty paper. PRTG, LogicMonitor, Zabbix and WhatsUp Gold report up, down or paused, and Meraki reports internet link loss and latency.
  • The security inventory keeps health, threats, tamper protection, agent age and serial, shown as a Protection column.
  • TASS uses the school’s day, not UTC. Synergetic term dates are checked, and an expired Edumate token says so.
  • Connector help says which operations have not been checked against a live account. QuickBooks says why it cannot be set up.
0.46.0The school’s own fields on devices, people and loansMigration

19 October 2026. ⚠ Migration. Take a verified backup before upgrading. One additive migration adds a column for school field values on devices, people and loans. No existing value changes and no table is rewritten.

  • Admin, Statuses and fields, School fields adds the school’s own fields: text, long text, number, date, yes or no, choice, several choices and staff member. Each has a label, help, whether staff forms require it, who can see it (everyone who can see the record, or managers only) and whether it is shared with AI, which is off by default.
  • Up to 30 fields in use and 60 in all for each kind of record, and 50 choices a field. Fields are archived, never deleted, and their values come back with them. Student records take no free text.
  • Fields show on the device page, the person page and the loan device, in the add and edit forms, as up to three extra list columns with filters, in the device CSV export, and in the Devices, Loans and People reports and board widgets.
  • A loan field belongs to the loan device or to each lending. A lending’s fields are filled in when the device is lent or returned, and kept in its History.
  • Flows can test school fields, use them as values, and set them with Set school fields on a device, a person or a loan device. A text field never takes words a requester typed, another app sent or AI wrote.
  • The assistant reads only fields shared with AI that the person asking can see.
  • A managers-only field never shows in a list, export, report, filter, flow or assistant answer for anybody without the manage permission. The audit log records values only for fields everyone can see. A person’s fields are in their subject-access export and are emptied when they are erased.
  • Changing fields needs workflow.manage.
0.45.0Report boards by email, to the right peopleMigration

18 October 2026. ⚠ Migration. Take a verified backup before upgrading. One additive migration adds delivery records for scheduled report emails. Existing schedules keep working. The CSV in their email becomes a choice that starts off, and any date range over 366 days is capped.

  • Schedule this board in a report board’s More menu emails a summary of each widget (headline, the period before, top five rows) with one link back to the board, which asks for a sign-in. A shared board goes to people in its audience, a personal board only to its owner.
  • Scheduled emails go to staff who can view reports, picked by name, up to 20. Each person gets the figures they would see signed in, inside the campuses and desks of the schedule’s owner.
  • Schedules run daily, every weekday, weekly or monthly, at the school’s own time, shown in the school’s timezone.
  • Delivery history records every run as sent, skipped or failed, with the reason. The list shows the last run beside each schedule.
  • A schedule pauses itself, and says why, when its owner leaves or loses report management, when nobody it goes to can receive it, or after three failed sends in a row. Resume is beside the reason, and report managers are told.
  • A fixed report can also go to up to 5 outside addresses, only at domains allowed by somebody with connector.manage (none by default). Outside addresses get the summary with no names and no CSV.
  • Show people’s names and Include the report as CSV are off unless chosen. Ticket titles never leave by email.
  • A school keeps up to 50 scheduled emails and sends up to 500 report emails a day.
  • Fixes: the server checks every schedule, emails arrive at the school’s hour rather than the server’s, and the same email is never sent twice.
0.44.0Loans that show the device, and clearer Microsoft 365 connections

17 October 2026. No migration.

  • With permission to view devices, each loan row links to its device and shows the MDM’s user, free storage, battery and last check-in. A Not the borrower chip shows when the MDM’s user is someone else. The loan panel adds OS version, compliance, encryption and device notes, each with the MDM and time it came from.
  • The campus can be found by typing the school’s address. The address is looked up through Plugboard’s server, with no cookies or school details.
  • The Microsoft 365 and Google Workspace connection page has a header with the account and status, and groups services by area, each with one sentence on what it gives the desk and its permissions behind a disclosure.
  • A service waiting on a permission reads Needs permission or Some permissions missing, names each missing permission with a copy button, and offers Check again.
  • Microsoft 365 and its services show their own logos.
  • Managed AI offers Enable or Disable, Test and provider details; the school keeps the switch. Switching on the school’s own AI connector switches Managed AI off in the same role, and the page says so.
  • On a wide screen the ticket has a property strip across the top, a Work column and a reply box that stays in the page.
  • RingCentral signs in with a JWT credential and says so, and connector setting names read as words.
  • Fixes to placing the campus on the map, the flow list with AI off, and flow names.
0.43.0A desk that works cleanly with AI off

16 October 2026. No migration.

  • Resolving or closing a ticket pauses every running timer on it and keeps the time to log. The resolve prompt offers to stop and log a running timer.
  • With AI off: the assistant says AI is off instead of showing an old provider error, flow templates whose steps need AI say so, Describe an action does not offer to draft, and the SLA and cover document dialogs say before upload that the document text still shows without AI.
  • The private note written when a secret is shared says the link is shown once and not kept.
  • Return on loans stays disabled until a loan is selected.
  • AI activity says when its counts are from before AI was switched off.
  • Wording fixes across devices, secret sharing, Admin, Cover and Admin, AI.
0.42.0Documentation that describes what is built

15 October 2026. No migration.

  • The README and download documentation describe only what is built.
  • No change to the desk.
0.41.0Quicker assistant answers

15 October 2026. No migration.

  • The assistant answers sooner. Lookups it needs together now run at the same time. A step that proposes a change still stops for your review first.
  • When an AI provider fails three times in a row (timed out, unreachable or rate limited), it is skipped for 60 seconds. The next model answers at once, or the assistant says the provider could not be reached, instead of waiting out the same timeout on every question. Skipped calls show in the AI call log. There is nothing to configure.
  • With Claude, later steps of an assistant answer read the tool list from Anthropic’s prompt cache. Anthropic bills cache writes at a higher rate than plain input; the AI call log counts them at the plain input rate.
  • Connector setup labels read as words, such as JWT credential for RingCentral and Organisation ID for Webex, and catalogue cards say how a service signs in.
  • A service that cannot be set up yet, such as QuickBooks or Microsoft Excel, says why.
  • Entra Connect Sync setup says to install the site agent on the active sync server.
  • Tickets and the school map wait for your permissions to load instead of briefly saying you cannot view them.
0.40.0Set up from a document, and icons from a photoMigration

15 October 2026. ⚠ Migration. Take a verified backup before upgrading. Two additive migrations store uploaded agreements and the school’s icons. No existing records change.

Set up SLAs and cover agreements from a document

Section titled “Set up SLAs and cover agreements from a document”
  • Admin, SLA has Set up from a document. Admin, Cover agreements has Add from a document, and Update from a document on each agreement. Upload the agreement as a PDF with selectable text, up to 6 MB and 60 pages.
  • Read with AI suggests values for the form. Each value shows the words it came from and its page, highlighted in the document text beside the form. Accept, edit or skip each one, then press Apply. Nothing changes until you apply, and applying uses the same forms, permissions and audit log as typing the values in.
  • A value whose wording cannot be found in the document must be edited before it can be accepted. Dates that could be read day first or month first, and amounts quoted excluding GST, are flagged. Terms the form has no setting for, such as public holidays or service credits, are listed with their quotes and not applied.
  • The original stays with the SLA or agreement and can be downloaded from it. Revert puts the previous values back. A document that is never applied is deleted after 30 days.
  • With AI off, the document text still shows beside the form and nothing is sent. A school can switch document reading off in Admin, AI. Each read sends only the extracted text, with names, email addresses and phone numbers masked. Reads are limited to 3 per document and 20 per day for a school.
  • On a device page, Model icon gives every device of that model its own icon in the device list, on cards and on the device page. Choose one of the school’s icons, one from the built-in library, or make one from a photo. Usual drawing puts the model back.
  • Add icon from a photo: photograph the object on a plain surface, crop it, pick one of up to three traced outlines, set the detail and check how it looks at small and large sizes on light and dark. The photo is traced in your browser and never uploaded or stored.
  • School map point categories can use the school’s icons, and any icon can be downloaded as an SVG file. A school keeps up to 300 active icons. Archiving an icon keeps every record that used it, drawn with its usual icon.
  • Managing icons needs device.manage or workflow.manage and is recorded in the audit log.
  • Admin, Connectors lists connections as a table with anything failing or needing attention at the top. Each row says what is wrong in a few words and offers one next step: Fix, Test or Review & enable. Sort by name, state or last check, group by kind of service, and read each connection as a card on a phone.
  • Every connector shows a mark of its own: the brand’s logo, a picture for open standards such as LDAP and SMTP, or a two-letter monogram in a colour that stays the same everywhere. A provider’s connectors share one mark.
  • Share a secret from a ticket’s Actions menu, or while writing a private note. Type, paste or generate a password or PIN and copy the one-time link into Teams or email. The private note records only who made the link, its label, expiry, opens and whether it has a passphrase. It never holds the link or the secret and is never emailed. Needs secret.share.create and ticket.internal.
  • Build with AI in Flows works with Claude again.
  • Admin, AI activity shows a provider’s short reason when it refuses a call, and AI usage shows embeddings, decisions, drafting flows and flow ideas as four tiles.
  • Webhooks can subscribe to DNS record changes and to domains or certificates about to expire.
  • Setting or removing an SLA target is recorded in the audit log.
  • DNS, domain and mail DNS monitors are checked as soon as they are added, and a monitor’s first check no longer shows as a Recovered incident.
  • Fixes to network discovery and the label designer.
0.39.0DNS monitoringMigration

15 October 2026. ⚠ Migration. Take a verified backup before upgrading. The API server needs outbound UDP and TCP port 53.

  • Monitors watch the school’s DNS without a DNS login, so they work when a department or a web agency runs it.
  • DNS record checks one name and record type (A, AAAA, CNAME, MX, TXT, NS, SOA, SRV, CAA or PTR) from public resolvers or the domain’s own nameservers. Each change of answer is recorded and can count as a failed check. A CNAME left pointing at a deleted cloud site that someone else could claim is flagged. Pin current answer makes today’s answer the required one.
  • Domain watches registration expiry, with reminders at 30, 14 and 7 days, and checks that every nameserver answers and serves the same version of the zone. Where the registry publishes no expiry date, as .au often does, enter the renewal date yourself.
  • Mail DNS checks MX, SPF (including the ten-lookup limit), DMARC, DKIM, MTA-STS, TLS-RPT and reverse DNS. Advice such as DMARC at p=none shows as a warning and never pages anyone.
  • Check my domain adds all of these for one domain in one step.
  • Dashboard cards: Domains and expiry, Mail DNS health, and Recent DNS changes.
  • Flows can start when a DNS record changes or a domain is about to expire. The gallery includes Mail DNS record changed, which raises a ticket when an MX or TXT record changes.
  • dns.view lets someone read DNS record history and the DNS dashboard cards. See permissions.
  • Domain and mail DNS monitors cannot go on the public status page.
0.38.0Label printingMigration

14 October 2026. ⚠ Migration. Take a verified backup before upgrading.

  • Print label on repair and ticket pages and in the right-click menus on their rows and cards. The repair list can print a label for every repair on the page. Choose a template, the number of copies and, for A4 sheets, the first free label, and see the first record as it will print.
  • Labels print through the browser at the label’s exact size (Brother QL, DYMO LabelWriter, Zebra 4 x 6 and 2 x 1, A4 3 x 7 sheets, or a custom size), or save as a PDF.
  • Admin, Labels is a designer for label templates. Drag and resize text, QR code, Code 128 barcode, photo, logo, line and box blocks on a to-scale canvas, and add record details such as the repair number, the person’s name and the device serial. Duplicate, archive, and choose a default for each record type and label stock. Four templates are ready to use: repair intake on 62 x 29 mm and 62 x 100 mm, a 62 x 29 mm ticket label and an A4 sheet.
  • label.print (held by Technician) and label.design. Printing also needs the record’s own view permission and follows campus and department scope. Each print is recorded in the audit log without the printed text. QR codes carry only the desk link to the record, which needs a sign-in.
0.37.0Network discoveryMigration

14 October 2026. ⚠ Migration. Take a verified backup before upgrading. Update the API, web and campus connector agents together using the normal update procedure. Nothing is swept until an administrator approves a range, turns discovery on for the campus, and the same range is listed in discovery.allow on that campus’s agent.

  • Network, Discovery sweeps ranges the school approved for switches, access points, printers, UPSes and other infrastructure, over SNMP with the school’s own credential profiles. It is part of the network module and uses no extra connector slot.
  • Ranges are private IPv4, no wider than /20 and at most 16,384 addresses per campus. Approving one asks you to confirm your identity again, and every Owner is emailed. Never-scan ranges mark segments to leave alone.
  • Runs go 64 addresses at a time, overnight and at weekends by default, and stop themselves if hosts that answered last time go quiet or when someone presses Stop discovery.
  • The agent checks every address against its own allow and deny lists, only reads identity details, never writes and never tries a default community. Credential profile secrets live only on the agent. SNMPv3 always uses authentication and privacy; v2c is allowed with a warning.
  • The same device seen by an MDM, a network controller, a sweep, a printer poll or an IPAM reservation becomes one record with several sources. Serials and hardware MAC addresses link automatically; a shared name or address is suggested in a queue to confirm or reject.
  • Discovered addresses appear in IPAM for people who can view discovery.
  • Printers report their serial number. Printers (SNMP) can poll over SNMPv3 and no longer tries the public community when none is set. Printers already set up keep polling over v2c.
  • Permissions network.discovery.view and network.discovery.manage.
  • Letters typed straight after Ctrl K or Cmd K land in search, and a dialog’s error message appears beside its buttons.
0.36.0Widgets you describe, and calmer dialogs

14 October 2026. No migration.

  • Build a widget and Describe a widget on Home, under Customise, Add widgets, and Describe a widget on report boards. Describe one in a sentence, such as “open tickets by priority this month as a bar chart”, and choose from up to three proposals shown with real figures. Nothing is added until you choose Add.
  • Widgets built on any dashboard or report board you can open can be reused anywhere, limited to data your role can view.
  • Describe a widget has its own switch in Admin, AI. With AI off, everyone can still build widgets by hand.
  • Dialogs open, close and finish faster. With reduced motion turned on, they use a short fade instead of movement.
  • The ticket effort report shows each technician’s avatar beside their name.
  • The command palette opens the password generator: type “generate” or “password”.
0.34.0, 0.35.0People on tickets, names instead of ids, and one-time linksMigration

14 October 2026. No migration in this release, but it carries 0.34.0, which has one. ⚠ Migration when upgrading from 0.33.0 or earlier: take a verified backup before upgrading.

  • A ticket’s requester and assignee show as contact cards: photo or initials, year level or job title, and where they are timetabled now. Press the card to pick someone else with search.
  • Photos show wherever a roster person is named, following the school’s staff and student switches and each person’s own switch.
  • Repair cards lead with the person the repair is for. The person page leads with who they are, where they are timetabled now, and what they hold and have open.
  • Activity, history, assistant approvals and workspace tabs name records and connectors instead of showing database ids.
  • When AI cannot answer, the assistant says why: AI switched off, no healthy AI connection, the provider did not answer, the daily limit reached, and so on. Administrators get a link to fix it. Admin, AI shows a diagnosis line.
  • The ticket queue names each priority and puts status beside it.
Section titled “0.34.0: Password generator and one-time links”

Not published on its own. Everything here ships in 0.35.0. ⚠ Migration.

  • Password generator. Passwords, passphrases, PINs and tokens, made in your browser and never sent to Plugboard. It shows each value’s strength and refuses anything under 60 bits, except a PIN. Open it from Shared secrets, Generate or the command palette.
  • Admin, Passwords and links sets what each generator preset makes, such as Student account, Staff account, Wi-Fi key and PIN.
  • One-time links. Shared secrets, Share a secret encrypts a secret in your browser and makes a link that opens once (or up to five times), for 15 minutes to 7 days, with an optional passphrase. Plugboard cannot read what it stores and never keeps it in a backup. Nothing is shown until the recipient presses Reveal, so link scanners cannot use it up. Five wrong passphrases destroy the link, and you are told when it opens.
  • Shared secrets lists the links you made, with their state and Revoke. Holders of secret.share.manage across the whole school see everyone’s and can set a link policy: shorter lifetimes, fewer opens or a required passphrase.
  • An identity password reset can hand the temporary password over as a one-time link, and the temporary password follows the school’s Student or Staff account preset.
  • Permissions secret.share.create (held by Technician) and secret.share.manage.
  • The wipe recovery PIN now picks every digit equally and never issues a repeated digit or a straight run.
0.33.0Connectors that renew their own sign-in

14 October 2026. No migration. Provider access, permissions and licences still apply.

  • RingCentral signs in with the app’s client ID, client secret and a JWT credential issued to a user with ReadCallLog, instead of an access token that stopped working after an hour.
  • QuickBooks Online, Webex Calling, Jira, Jira Service Management, Confluence and HubSpot take their OAuth app’s client ID and secret and a refresh token, and renew their own access. Jira and HubSpot are available in connector setup.
  • NinjaOne, Salesforce, Halo, Zoom Phone and Zoom Rooms reuse a token until shortly before it expires instead of requesting one for every call.
  • Entra Connect Sync refuses to run on a staging-mode server and says to install the site agent on the active server. A warning while the sync module loads no longer turns a working sync into a failure.
  • Google Cloud Directory Sync no longer stops part-way through a large directory.
0.32.0More from Microsoft 365 and Google Workspace connections

14 October 2026. No migration.

  • Connect another on the Microsoft 365 and Google Workspace cards, for a school with more than one tenant or domain.
  • When a working connection fails its check, everyone who manages connectors sees one alert and the whole-school administrators get one email. Its features wait instead of failing one by one.
  • With the client secret’s expiry date recorded, whole-school administrators are reminded 30, 14 and 7 days before it.
  • Every feature under a connection shares 600 calls a minute, so one busy feature cannot use up the provider’s budget for the others.
  • The Microsoft 365 Cloud Shell script also grants the Defender, Office 365 Management and Exchange application permissions.
  • Microsoft 365 and Google features appear only under their connection. Teams policy reads use the connection’s own app on the site agent: put the client secret in the agent’s secrets file for that feature.
0.31.0One connection for Microsoft 365, one for Google WorkspaceMigration

13 October 2026. ⚠ Migration. Take a verified backup before upgrading. After upgrading, connect Microsoft 365 and Google Workspace once in Admin, Connectors, then switch on the features you use. A feature that still held its own credential is switched off until you switch it on under the connection, which keeps its history.

  • Microsoft 365 is one card. Setup asks which features you want (Identity, Devices, Mail and collaboration, Security, Reporting, Azure), shows the app registration guide for exactly those, with a permission table and an Azure Cloud Shell script that adds the permissions and grants admin consent. Enter the tenant ID, application ID, client secret and its expiry, and an optional Exchange certificate, once. Seventeen Microsoft connectors are features of it. The Teams bot keeps its own registration.
  • Google Workspace is one service account: the APIs to enable, the full domain-wide delegation scope list for your features, and the key file, administrator and customer ID. Directory, Gmail, Chrome Enterprise, Classroom and Sheets are features of it.
  • Each feature reads Ready, Missing permissions (by name), Blocked, Off, Not checked yet, or Waiting for the connection. Consent is checked on save, on Check again, when a feature is switched on, and hourly. A permission added or removed outside Plugboard is recorded in the audit log.
  • A technician signs in with Microsoft once per connection, not once per connector, and a connection uses one licence slot however many features are on.
  • Privileged features, such as Intune wipe, local admin passwords, directory writes and mailbox actions, need a whole-school administrator who confirms their identity again to switch on.
  • Shared accounts are removed from Admin, Connectors.
0.30.0, 0.30.1Acting as yourself at a connectorMigration

13 October 2026.

Minor bug fixes and improvements.

13 October 2026. ⚠ Migration. Take a verified backup before upgrading.

Check two switches after upgrading. Allow account changes on Microsoft Entra connections is off by default: MFA and password resets, turning accounts on and off, sign-outs, licences, group membership, creating accounts and temporary access passes run only when it is on. Allow insecure on LDAP connections is also off: a plain ldap:// address is refused unless it is on, and password reset always needs ldaps://.

  • Who acts. An administrator chooses, per connector action, whether the vendor sees Plugboard’s own account or the technician: “Acts as Plugboard”, “Acts as the technician when they have signed in”, or “Acts as the technician; refuses otherwise”. Plugboard’s own permissions and approvals still run first.
  • Technicians link their own Microsoft account or Google admin address on the Account page. An action that needs it asks them to sign in and then runs.
  • Intune erase, local admin passwords and remediation scripts, Teams posts and Excel writes can run as the signed-in technician with their own Intune role. Google admin actions can too, behind a per-action setting that starts off.
  • Jamf Pro can use separate API clients for device commands and for privileged actions, each with its own narrow role. Jamf Pro commands use the Jamf Pro API, and a Mac lock carries a six-digit PIN.
  • A school can require a second person to approve turning on fully automated flows. A flow pauses at once when its owner is turned off or loses access it uses, and everyone who can publish flows is alerted.
  • An event flow published as Watching counts as tested once a Watching run finishes with nothing refused.
  • Actions, From a template offers ready-made actions: message the requester, lock a lost device, mark a device lost and tell the desk, and remind a borrower about an overdue loan. Each starts as a draft and off.
  • AI suggestions on a ticket can be applied together with Accept all and Do all.
  • Deactivating someone, resetting their password or ending their sessions also ends their connector sign-ins. Microsoft sign-ins unused for 90 days ask to sign in again.
  • A review of every connector against its provider’s documentation fixed paging, retries and edge cases across mail intake, directories, device management, ticketing, messaging, payments, printing, student systems, networks and AI.
0.29.0Staff photos, and widgets from your toolsMigration

12 October 2026. ⚠ Migration. Take a verified backup before upgrading.

  • Staff photos beside names in the people list, on cards and on a person’s page, with initials where there is none. Photos are copied nightly at 2:30 am from Sentral and, only when a school turns it on in Admin, Photos, from Microsoft 365, Google Workspace or Active Directory. Student photos are not included.
  • Turning staff photos off deletes the stored photos at once. Don’t show a photo for this person on a person’s page deletes theirs. Leavers’ photos are deleted at the roster sync. Photos never reach kiosks, portals, emails, exports, the API or AI.
  • Widgets from your tools. When you customise a dashboard, pick Jamf Pro groups and Kandji blueprints (up to 12 at a time) and each becomes a count of devices in that group, at the viewer’s own campuses. Device questions on report boards can filter by MDM group.
  • Fully automated flows. A flow that starts on its own can run its change and privileged steps with nobody asked. It is off unless a school turns on Allow fully automated flows in Flow controls, which needs flow.unattended, feature.manage and identity confirmation. Publishing one also needs a passing Try it in the last 7 days. Account changes, device locks and hand-offs always ask a person.
  • Custom actions have Try it and History, and administrators can describe one in a sentence for AI to draft. Both the action and its flow stay off until a person checks and turns them on.
  • The repair ready-for-collection notice is a built-in flow you can edit.
  • Google Vertex AI signs in with a service account, and SharePoint, Power BI and Power Automate sign in as an Entra app with a tenant ID, application ID and client secret. Microsoft Teams keeps itself signed in. Re-enter these connectors’ credentials after upgrading.
  • Self-hosted: the API keeps 10 database connections by default. Set DATABASE_POOL_SIZE to change it.
  • Working With Children Check reminders run on schedule again.
0.28.0, 0.28.1Dashboards, cards and a resizable menuMigration

12 October 2026.

Minor bug fixes and improvements.

0.28.0: Dashboards, cards and a resizable menu

Section titled “0.28.0: Dashboards, cards and a resizable menu”

12 October 2026. ⚠ Migration. Take a verified backup before upgrading.

  • Home and report boards share one dashboard model in every school. Each school starts with the four Home dashboards staff already had (My day, Service desk, Fleet & infrastructure, Management) as templates. Saved layouts, team templates and boards are copied across on first use, and nothing is deleted.
  • Home has resize handles, report questions beside the built-in widgets, sharing with roles, desks and campuses, and widgets each person can hide.
  • Dashboard wall screens. A wall-screen link opens a dashboard read-only on a screen with no sign-in. It refreshes at most once a minute and stops when the link is revoked or expires. Creating one needs dashboard.link.manage.
  • Drag the edge of the side navigation to set its width. It is kept on the device and on your account.
  • Tickets and people can show as cards or a table, and every card list shares one layout.
  • Parents are called parents/guardians across the desk, portals, app, notices and user guide. Sign-in addresses and settings are unchanged.
  • The per-person “Hide where they are timetabled” setting is removed. The student system decides who may know where a student is, and people.whereabouts.view with its audit record on every look is unchanged.
0.27.0, 0.27.1Records beside the list, and custom actionsMigration

12 October 2026.

Minor bug fixes and improvements.

0.27.0: Records beside the list, and custom actions

Section titled “0.27.0: Records beside the list, and custom actions”

12 October 2026. ⚠ Migration. Take a verified backup before upgrading. Existing ticket actions become custom actions with the same settings, and their category and queue limits become filters.

  • People, devices, fleet, repairs, loans and tickets open a record summary beside the list on wide screens and in a sheet on narrow ones. The open record is in the address, so a link or reload keeps it, and arrow keys and Escape work.
  • Devices, fleet, repairs and loans can show as cards or a table.
  • A device summary shows assignment, school map location, compliance and why it needs attention. Fleet category tiles filter one findings table.
  • Custom actions. Administrators with action.manage add buttons to records, choose who may use them (roles, desks, campuses and named people), and have each run a flow. Presses act as the person pressing and are recorded in the audit log.
  • Flows can be run by hand on devices, repairs and loans, and can start when a monitor goes down or up, a loan becomes overdue, a repair is ready for collection, or a ticket or repair changes status.
  • Dashboards and report boards load faster, and fleet attention counts respect campus scope.
0.26.0Identity in one view

11 October 2026. No migration.

  • A person’s Identity pane merges every connected directory that holds an account for them, labelling where each fact came from and flagging where providers disagree.
  • Selecting a room, building or point on the school map lists the equipment there, with status and last seen, within your permissions and campus scope.
  • Stock can show as cards. Selecting a person shows their open tickets, loans, repairs and devices in plain sentences, with alerts for non-compliant, lost or disabled items.
  • The device page has a key-facts strip and a side rail with assignment, location, compliance, warranty and related work.
  • Mail intake sets aside a message it cannot take and carries on with later mail. Connector tests say whether credentials, a certificate or the network failed.
  • Self-hosted installs can reach a mail relay on the school network.
  • Names and other personal fields are masked before reaching an AI model. Dashboard tiles, monitors, the daily digest and other summaries respect the viewer’s campus and department scope. Creating an API key asks you to confirm your identity again.
0.25.0Connected context and clearer answersMigration

9 October 2026. ⚠ Migration. Take a verified backup before upgrading. Update the API, web and campus connector agents together using the normal update procedure.

  • Run permitted network checks from a device or ticket, and open supported management tools for network equipment. Checks require a configured campus agent and its local destination allowlist. Keep useful results as private notes.
  • Set your desk status and hold ordinary notifications while on do not disturb. Directory presence is optional and requires explicit provider setup and consent.
  • Import a school timetable and use supported OneRoster mappings. Student room lookups require separate permission and are audited; protected people remain hidden. Requesters can confirm their own timetabled room when reporting a problem.
  • See service observations alongside notifications, ticket context and assistant answers. Provider access and licences determine which observations are available.
  • Review AI-assisted bulk triage and draft public or private notes before applying selected changes. Public notes support optional requester email, CC and BCC.
  • Use clearer assistant summaries and follow-up questions, calmer dialog resizing, consistent controls and school-map wallboards with explicit access checks.

Managed AI configuration supports a separate credential for each deployment. Provider availability, usage charges and your configured allowance still apply.

0.24.0, 0.24.1A wider desk, quicker intake and connected ITMigration

7 October 2026.

Minor bug fixes and improvements.

0.24.0: A wider desk, quicker intake and connected IT

Section titled “0.24.0: A wider desk, quicker intake and connected IT”

Regular release, 7 October 2026. ⚠ Migration. Take a verified backup before upgrading. From the preceding development build, one additive migration adds personal favourites. Upgrades from 0.22 also apply the intervening connector, mail-delivery, decision and Flow migrations in sequence. Update the API, web and site agents together using the normal update procedure.

The desk uses wider layouts, readable record summaries and consistent controls across tickets, repairs, equipment, people, reports and administration. Star permitted pages, records and saved views in personal favourites. Top navigation categories open on mouse hover as well as click and keyboard activation.

The header’s create action and Shift+N open ticket or repair intake when your permissions and enabled modules allow it. Auto selects clear descriptions after a typing pause using local rules. Choosing Ticket or Repair overrides the suggestion until you choose Auto again. Switching keeps the description and verified shared context; specialised fields stay with their own form.

Internal notes have a full orange box. System activity uses automation icons and a System label. Reply fields, requester names and sentiment indicators have clearer spacing. Dialogs resize briefly and close with a short fade at their visible size, with reduced-motion preferences respected.

The education connector catalogue covers identity, device management, security alerts, backups, infrastructure, mail, files, teaching systems and AI. Microsoft management includes SharePoint, Teams, Defender, Purview, reports and service health. Google management includes directory, Gmail, tenant posture and Chrome operations. Hyper-V, IMAP and SFTP support their documented infrastructure, mail and file workflows. Each operation requires its documented provider permissions and any applicable licence or API entitlement. Check the relevant connector guide before enabling it.

Saved connector accounts can supply credentials to compatible capabilities without entering them for each connector. Sharing requires fresh identity confirmation. Setup, test and enable remain separate steps. Mac users can open Screen Sharing from a supported device’s configured remote-access action.

Flows support manual, event, scheduled and called automation, with reviewed versions, dry runs, run history, go-ahead decisions and undo controls. Forms retain legitimate unsent answers; publication checks the revision reviewed. Optional AI writing and decisions follow the school’s provider policy and budget. Decision-provider activation cannot proceed through a failed review. Rules and manual work remain usable with AI disabled.

Report boards combine scoped widgets over tickets, repairs, devices, loans and time, with CSV/PDF export and wall-screen views. Charts preserve missing values and signed amounts, explain partial coverage and use additive measures for shares. Reports include the complete selected final day and respect calendar boundaries. Device detail shows stored hardware even when its MDM source is disabled; opening it does not call a provider.

Supported field capture can prepare a bounded set of signed records and assets for offline work, verify stored preparation and recover after fresh sign-in. Loan, stocktake, disposal, printer and network workflows retain current record scope, with complete filtered disposal exports within the server limits.

Restricted actions explain insufficient permission before opening their editor or confirmation and check access again before saving. Signing out or changing confirmed access discards protected drafts and delayed results. Technician connector guides require sign-in and the relevant permission. Published public help remains separate, and document copies are bound to the reviewed snapshot.

Ticket mail delivery records admission and reconciliation, so an interrupted submission can be investigated without blindly sending it again. Repairs recover existing mirror tickets instead of duplicating them. Flows distinguish requested privileged roles from roles actually provisioned by the provider.

After upgrading, check readiness, sign-in and your configured connector results. Live provider and physical-device validation remains necessary for your own environment. Testing toward 1.0.0 continues; final native installer publication is separate from this release.

0.8.0 to 0.22.1

0.22.0, 0.22.1Decision providers, shared mailbox intake and reliability fixesMigration

⚠ Migration. Take a verified backup before upgrading.

A stale browser presenting the same retired refresh token repeatedly now creates one security event and cannot sign out a later, unrelated session. A dropped live update stream no longer rotates a healthy refresh token on each retry; sessions that have ended return the browser to sign-in.

An initial reuse alert still ends live sessions for that account. Investigate an unexpected first alert as a possible credential replay; repeated alerts with “no live sessions” on earlier versions may have come from the same stale browser retrying.

0.22.0: decision-provider release and reliability fixes

Section titled “0.22.0: decision-provider release and reliability fixes”

⚠ Migration: additive changes for decision provenance, school criteria, tags, history and mail delivery. Take a verified backup before upgrading.

New: optional reviewed decision providers, school criteria and up to ten AI tags, and Microsoft 365 shared mailbox intake and sending. Jev starts off, and inputs are pseudonymised before leaving Plugboard. Laya has no trained Plugboard checkpoint, and identity approvals remain manual. Rules and manual work remain usable with AI disabled.

Repair lodging and ticket visibility in the portals, worker status sync, support backup restore and Teams follow-ups now use the intended department scope. Failed repair lodging cleans up the unlinked submission and releases its loan. Repair and parent-portal status labels wrap beneath titles on phones.

Structured AI answers now work with Ollama 0.32.14, llama.cpp-based OpenAI-compatible servers and Anthropic. Hosted deployments no longer offer new Ollama or Laya configurations; existing local-model records remain visible.

Before relying on AI, confirm your chosen provider is configured and enabled, and review its suggestions on your own data.

0.21.0Teams intake, a visitor register and network IP addressesMigration

⚠ Migration: three additive migrations, for network IP addresses and configuration snapshots, Teams intake, and the visitor register. None removes or rewrites customer records. Take a verified backup first, and use the normal update procedure.

None of the four new features has yet been run against real vendor systems (Teams, Meraki, UniFi, SNMP, kiosk hardware or real email). If you turn one on, check the first results against the source, and tell us what does not match.

Microsoft Teams ticket intake. Staff message the school’s IT bot in Teams, or @mention it in a channel, and a ticket opens through the same intake as email. A channel thread stays on one ticket; a chat joins its open ticket unless the message starts with new:. Public replies and closures are posted back, but channels and group chats get a pointer, never the reply itself, and internal notes never go. The bot uses the school’s existing Entra connector app registration and accepts nothing until an administrator’s Test has passed. Public cloud only. See Microsoft Teams intake.

Visitor and contractor register, part of the campus operations add-on (Facilities module). Visitors and contractors sign in and out on a reserved kiosk with the new visitor sign-in option (off by default), or at the office, and the register keeps the on-site list for an evacuation. The person being visited is emailed by default; turning that off is an audited setting. A contractor’s Working With Children Check is recorded as sighted by staff, with expiry reminders; Plugboard does not check a registry. A contractor with an expired or missing check is held at the office rather than turned away. See visitors and contractors.

Network IP addresses and configuration history. The Network pane gains an IP addresses tab: subnets and VLANs from Meraki, UniFi (local) and SNMP, plus subnets and reservations recorded by hand, with utilisation and address conflicts. Client addresses appear only with client tracking on and network.clients.view. A Configuration tab keeps read-only, versioned snapshots of Meraki and UniFi (local) configuration with a comparison between versions. Secrets are removed before anything is stored, and nothing is pushed, restored or exported.

New permissions. network.config.view, visitor.view, visitor.manage and visitor.configure. No built-in role other than Owner holds them; grant them to the roles that need them. visitor.configure is Technical; the others are free Participant permissions. See the permissions reference.

Reviewed CSV import for devices and stock. Device and stock imports now show every row’s outcome before anything is written. All three imports, people included, skip invalid rows instead of failing the file and return them as a file to fix. See devices and stock.

The assistant filters the page you are on. On tickets, devices, people, loans, repairs, stock, AV rooms, printers and monitors, a request such as unassigned tickets or low stock sets that page’s own filters. See the assistant. Known errors reach their incidents: a document bound to a problem ticket is listed first on every incident caused by it. See documentation.

The mobile app is not yet available. The iPhone, iPad and Android app is built but not published, so it cannot be installed.

Also fixed: confirming a managed-hosting onboarding now creates the administrator named at confirmation. New managed deployments have the hosting provider’s weekly server backup switched on. Custom domains on managed hosting no longer fail with Cloudflare error 1456. LDAP and Active Directory agent jobs no longer fail on binary identifiers.

0.20.0, 0.20.1Safer sign-in, larger registers and read-only OneRosterMigration

No database migration. Schools upgrading from before 0.20.0 still need the 0.20.0 migration and upgrade checks.

Legacy AI calls now stop if the school’s AI settings cannot be read. The ticket classifier and ticket-from-description path could previously call an AI provider after a settings lookup failed, without confirming the school’s AI policy. They now return no AI result instead.

0.20.0: safer sign-in, larger registers and a OneRoster preview

Section titled “0.20.0: safer sign-in, larger registers and a OneRoster preview”

⚠ Migration: one additive migration creates three database indexes. It does not remove or rewrite customer records. Take a verified backup first and allow time for index creation on large databases.

Review connector-agent trust when upgrading. Creating an agent or rotating its token now requires an unrestricted whole-school administrator and fresh authentication confirmation. An agent can answer LDAP sign-in jobs, so delegated connector-management access alone is insufficient. Review existing enrolments, revoke unknown or untrusted agents, and enrol approved replacements. Rotation keeps the old token valid for seven days and is not immediate containment. See connector-agent security.

SAML sign-in must start in Plugboard. Reused assertions are refused, and unsolicited sign-in from an identity-provider launcher is not accepted. Test the school’s IdP after the upgrade. Multiple API replicas need the start and callback to reach the same process; an API restart invalidates unfinished sign-ins. See SAML setup and routing.

Larger registers load in pages. The loan desk and repair loan picker fetch 50 records at a time, with search and filters applied across the whole pool. Bulk actions apply to the current page. Custom console clients should use /loans/inventory; the legacy /loans list now rejects a result above 1,000 records. See loans and the loan API transition.

OneRoster is available as a read-only preview. It supports OneRoster 1.1 and 1.2 and imports student and staff people records. It does not provision accounts, import family relationships or write back to the SIS, and has no live school-provider validation or 1EdTech certification. Pilot it with independently checked counts before scheduling a school sync. See OneRoster setup. Sentral no longer silently stops at 20,000 records and refuses an incomplete pull. See Sentral roster limits.

Also fixed: campus technicians can use an authorised local device’s shared district MDM for wipe requests and LAPS without permission to manage the connector. Failed configuration reads now show unavailable states and retry controls rather than empty catalogues or default policy values. API responses now explicitly prevent caching sensitive data. Native embedded-database starts apply row-level security; externally managed databases still require the operator’s separate migration-owner and application-role configuration. The default container release does not publish native installers; check the download centre for your platform.

0.19.0 to 0.19.3The assistant becomes the desk’s background brainMigration

⚠ Migration: three: repair replacement, the portal device snapshot and text-message delivery status, and sentiment. Take a verified backup first.

Sentiment on tickets. Every requester message is read for tone, urgency and signals such as chasing or being blocked from class. The queue gets a Tone column and a “Frustrated requesters” filter, and Briefing lists them. Suggest mode proposes a one-step priority bump; auto mode applies it, never to the top priority, and it can be undone. With no AI, a rules pass still gives a coarse level, labelled Rules. A student ticket using a safeguarding word, or read as distressed, is flagged to staff alongside the school’s safeguarding contact.

Staff experience. A nightly 90-day summary for each staff member, shown on the person page, in Briefing and on a new Experience report. It needs report.view and client.view. No per-person score is ever calculated or stored for a student or parent; they appear only as school-level totals. See sentiment & staff experience.

Replace device on a repair. Choose the new device from stock or a loan already out, or record one on its way, and say what happens to the old one. A covered repair never asks the family to pay for the replacement. See replacing a device on a repair.

Also: the person page answers questions about a person’s records with no model call; portal-lodged tickets carry an MDM device snapshot; parent portal status lines and loan notices can be translated; and the Sent tab shows Twilio delivery status (needs PUBLIC_URL on HTTPS). The AI value card moved from the dashboard to Briefing. See what we process.

0.19.2: managed AI moves off OpenAI and Anthropic, and quieter monitor alerts

Section titled “0.19.2: managed AI moves off OpenAI and Anthropic, and quieter monitor alerts”

No database migration. Includes 0.19.1, which was never released.

Managed AI now runs entirely on open models that DigitalOcean serves itself. OpenAI and Anthropic are no longer sub-processors; DigitalOcean is the only AI sub-processor for managed AI, still processing in the United States. The managed connector moves over by itself on start-up, and the move is audited.

On a deployment that took 0.19.0, every managed AI call was refused and AI suggestions stopped until this release. If you went straight from 0.18.2 to 0.19.2, this never affected you.

A monitor that stays down no longer piles up alerts: repeats replace the card on screen, the bell keeps one entry per monitor, and the alert clears when the monitor recovers.

See the assistant and AI features and what we process.

0.19.0: the assistant becomes the desk’s background brain

Section titled “0.19.0: the assistant becomes the desk’s background brain”

⚠ Migration: eight migrations: the AI engine, notices, the fix catalogue, repair outcome and cover, known issues, API-key write approvals, identity runbooks and the portal device snapshot. Take a verified backup first.

If you take this release, read 0.19.2’s notes above before you rely on AI suggestions. Every managed AI call failed until 0.19.2.

Every AI value is labelled and can be undone, and with no AI connector configured the desk behaves as 0.18.2 did. Names, emails, phone numbers and IDs are masked before every managed AI call. Each AI feature has its own mode (off, shadow, suggest, auto) under Admin, AI settings; auto unlocks only after a proven accuracy record, and never for identity work.

Ticket brain. A brief, triage suggestions and a reply draft are prepared in the background when a ticket arrives and after each requester reply. Triage shows as values you accept, dismiss or undo; drafts are never sent without a person. Resolving offers a wrap-up note, time worked and a knowledge-base draft.

Same issue. A same-person duplicate within 48 hours can merge automatically, with one-click unmerge. Outage clusters at a site are proposed as an incident.

Briefing replaces the old assistant page. The page assistant now knows which record you are on.

Joiners, movers and leavers. SIS changes plan runbooks (disable, revoke sessions, licences, groups, mailbox delegation, device and loan recovery) that are previewed, approved with step-up, staged and undoable; nothing is deleted. New Licences & access reports.

Device fixes on staff devices: a catalogue of fixes the AI can suggest and a person runs through the MDM. Never on a student device.

Repairs get a likely-outcome card at lodgement and cover agreements, so a covered repair never asks a family to approve or pay.

Notices gain approved translations, text messages with quiet hours, and family contact preferences.

Portal, kiosk and parents: device selection when lodging, help articles and known issues while typing, and plain repair status for parents. No generated text reaches a student or parent; safeguarding words show the school’s configured contact instead.

Admin gains AI settings and AI activity (every model call and suggestion, with export). The people page is reworked.

Changed: API-key writes now wait for a person. A write tool called through MCP or /v1/actions with an API key is held as a pending approval until somebody with integration.manage who also holds that tool’s own permission approves it (with a step-up) or declines it, under Admin, API & webhooks, Approvals. Requests lapse after seven days. Anything scripting writes against /api/mcp or /api/v1/actions must now wait for, or poll, the approval. POST /v1/actions/:name answers 202 with a { "status": "pending_approval", "approvalId" } body, pollable at GET /v1/actions/approvals/:id. Reads are unchanged. API keys also gain an AI switch: keys made before 0.19 keep AI access, new keys start without it.

See AI features, AI settings, AI activity, access & runbooks, cover agreements, translations & text messages and what we process.

0.18.1, 0.18.2One plan, a trial and read-only mode, and interactive reportsMigration

No database migration.

  • Notifications about something going wrong, such as a monitor going down, a failed backup or sync, or a breached SLA, now arrive as warnings rather than with a green success tick.
  • Desk setup and repair outcome reminders sit below the dashboard title.

0.18.1: one plan, a trial and read-only mode, and interactive reports

Section titled “0.18.1: one plan, a trial and read-only mode, and interactive reports”

The first 0.18 release; 0.18.0 was never released.

⚠ Migration: one migration adds licence and usage fields. No existing data is changed. Verify a backup before upgrading. No new permissions.

Licensing behaviour changes on upgrade. Before 0.18.1, a school without a licence had every module with no end date, and removing a licence did the same. From 0.18.1:

  • An unlicensed school is on a 30-day trial with every base module and no add-ons, starting the first time 0.18.1 runs. After that the desk becomes read-only until a licence is added.
  • Removing a licence no longer unlocks everything. The school goes back to what is left of its trial, or becomes read-only straight away.
  • A licence that expires past its grace days, or is cancelled, also makes the desk read-only. Before, it switched modules off and hid their records.
  • If your school is licensed and current, nothing changes.

Read-only means staff can still sign in, read everything, back up, restore and export, look after their own account, take access away from people, and add or renew the licence. Every other change is refused, including through API keys, REST actions and MCP. The portals, kiosk, inbound email and webhooks keep taking requests, and sync with other systems pauses. A banner warns in the trial’s last week.

There is one Plugboard plan, with every base module, 2 Technical seats, 2,000 managed devices and, on managed hosting, 5,000 hosted AI calls a month. Extra Technical seats, Business seats, 1,000-device blocks and the campus operations add-on are added on top. Each staff account is a Technical seat, a Business seat or a free Participant, set by its roles and shown on the Users page; before, every active account counted. Going over shows a warning and is settled at renewal. Licences on the earlier tiers keep their terms. Admin, Licence shows usage against what the licence includes.

Admin, Campuses could fail to load once a school had a campus; that is fixed. Creating and deleting a campus now needs site.manage (before, connector.manage) and is audited.

Reports and Cost breakdown are rebuilt with interactive charts, sortable tables and keyboard access to exact values. CSV exports are unchanged. Admin, Roles, Security, SSO, Features and Backups are reorganised; every setting is unchanged. The page assistant is on Tickets, AV and Documentation.

See licence and plan, plans, modules, reports, costs, roles, single sign-on, campuses and moving around a page.

0.17.1Time tracking on tickets, and People and Directory as one screenMigration

The first 0.17 release; 0.17.0 was never released.

⚠ Migration: one migration adds time-tracking fields, server-side timers, quick time and ticket estimates. Verify a backup before upgrading. Time tracking switches on for every school that has Tickets; you can switch it off on Admin, Features. No new permissions.

Tickets now track time. A timer starts when you begin writing a reply or note, or from Start timer if your school prefers. Timers are kept on the server, and a tray beside the bell lets you manage them from any page. The composer has a time field with a work type, linked to the reply or note. The Time chip shows logged time against the ticket’s estimate, and the Work tab lists every entry. Resolving a ticket with no time logged offers to add time first, or requires it if your school says so.

My time (/time) shows your week against a daily target, with quick time for work that has no ticket. Leads with report.view get a Team view. Schools configure time tracking under Admin, Tickets, Time tracking. Editing somebody else’s time, and changing these settings, needs workflow.manage. Reports gain Estimate vs actual, and Ticket effort gains more groupings. A report whose module is switched off is now refused by the server, including scheduled emails.

People and Directory are one screen. People is in the navigation for anyone with client.view or directory.view, with a Roster view and an Accounts view. Old /directory links open the Accounts view. A person’s Account tab now lists their groups, and people with identity.license.manage can assign and remove licences there with a reason and fresh authentication. For live accounts, manage inbox delegation from the person’s Account tab. Search all accounts replaces Manage in Directory.

The closed-repair outcome reminder is now a banner on the dashboard and the Submissions list. The ticket’s Files chip is gone; use the Files tab.

See time tracking, ticket settings, people, reports, submissions and the audit log.

0.16.0One way of moving, rebuilt screens and staying signed inMigration

⚠ Migration: one migration adds the optional repair outcome Result. Verify a backup before upgrading. Existing outcomes have no Result until somebody edits them. No permissions change. The portal product photo address is public in the same way the portal catalogue already is.

Staff are no longer signed out of every device without warning, which usually happened first thing in the morning. When a retired token genuinely comes back, the forced sign-out is recorded in Logs as Refresh token reuse detected.

Classic and Modern now move the same way, and notifications are compact, show failures in red and show at most four at once. The Assistant is back in the bottom-right corner on tablets and computers.

The dashboard, tickets, repairs, devices and people screens are rebuilt. Tickets bring ThreatLocker Approve and Deny back to the top. Recording an outcome, for one repair or several at once, uses one form with a new Result: repaired, replaced, no fault found or beyond repair. Each person has a full page. Products can have a photo or an icon, shown on the desk, the portals and kiosk.

See the dashboard, tickets, submissions, devices, people and stock.

0.15.1One consistent desk, saved dashboards and clearer portals

No database migration. 0.15.0 was never released, so this is the first 0.15 release.

Every staff area now follows one working language: labelled local tabs, a single primary action, aligned rows and 44px controls, with explicit loading, partial, stale and unavailable states. The Assistant launcher moves into the staff header and the AI workspace is labelled Assistant. Dialogs open with a spring and close smoothly; reduced-motion preferences are respected.

The dashboard becomes saved views of configurable widgets. People with the new dashboard.manage permission (wildcard administrators already hold it) can publish team templates, and each publish, update and removal is recorded in Logs. Recent activity has coloured event icons, linked records and a refresh control.

Ticket detail keeps its AI summary visible above Activity, Work, Context and Files. Technicians can include optional time with a reply or internal note.

The client portal puts repairs and overdue loans first, and a kiosk that cannot reach the server offers a retry. Parents see each child’s open repairs and what they owe, with charges split into To pay and Paid and the school’s own repair spend marked as not billed to them. Repair tracking shows the next stage, and ratings cannot be sent twice.

Account separates Sign-in & security from Preferences, lists where you are signed in and lets you end a session you do not recognise. Staff sign-in no longer reports a server outage as a wrong password.

In Logs, search the Action dropdown for readable choices such as Ticket created. Select several actions and combine them with person, record type and date filters. CSV exports respect those selections.

Automation rules show execution order, scope, conditions, intended actions, previews and recorded outcomes. New drafts start disabled and changes have an explicit review before saving.

Documentation separates internal runbooks from public help, and new requester articles start as drafts. Connector setup guides you through service, access, validation and activation review; one-time agent tokens are hidden when their dialog closes. Service-desk settings are split into ticket configuration, repair workflows, departments, SLA targets and staffed hours. Directory searches authorised directory connections and shows each account’s source.

Integrations, branding, features, kiosks, email messages, security requests, backups, compliance, inductions, reports, AV, printers, network, monitors, public status, access administration, stock, stocktake, disposals, charges, cost reports, software, repairs, loans, operations, People and device management all have clearer layouts and error recovery. The loan desk adds short-lived Undo actions. Recording sanitisation for a disposal does not perform a device wipe. Public status keeps internal details private.

Ticket AI now recognises an enabled AI connection when another connection in the same category is disabled.

Released 22 September 2026.

0.14.0 to 0.14.6Multiple connections, and a clearer ticket workspaceMigration

The new Assistant workspace brings together operational health, recommendations, activity and conversation, reading only the sources your role and enabled modules permit. The overview works without waiting for a model and with built-in ticketing switched off. Recommendations can be dismissed, reopened or snoozed for a day. Conversation history expires after seven days.

The assistant can prepare an exact review for supported cloud connection tests, connector display names, the product name and default Classic/Modern styles. Passwords, keys and routing stay in secure setup.

People combines a searchable roster with each person’s permitted equipment and work. CSV import previews column mapping, matches, skipped rows and errors before applying; existing identifiers remain unchanged.

Admin, Connectors guides setup through Service, Access, Validate and Review. Saving leaves a connection disabled until you explicitly enable it. This also applies when editing an enabled connection: saving pauses it while you test the changed settings, then review and enable it to resume use.

Client and parent portals have a clearer overview, and parents have an explicit Sign out control.

Upgrade: no database migration. Update API and web together.

0.14.5: faster answers with better ticket context

Section titled “0.14.5: faster answers with better ticket context”

The assistant returns direct answers for supported desk lookups without waiting for a model.

AI ticket summaries and reply drafts use linked device and repair details, category, queue, the latest public conversation and relevant published knowledge articles. Internal notes and restricted documentation are excluded.

No database migration or setup step.

Ticket detail now has Activity, Work, Context and Files views. Activity keeps the original report, AI summary and conversation together, with explicit Reply to requester and Internal note controls. On phones, use Ticket details to reach status, priority, assignee, queue and SLA.

Work holds checklists, subtasks, approvals and time tracking, Context holds linked records and related tickets, and Files collects message attachments. Transfer, merge and history are under Actions. Unsaved inputs survive tab changes, and a failed reply keeps its draft.

No database migration or setup step.

Dashboard tiles now use their icon colours as coloured backgrounds by default. Under Dashboard, Customise, turn Colored tiles off to restore neutral cards. This preference is saved to your account.

No database migration.

Admin, Connectors now uses a stable setup order: sign-in and directory services first, then device management and enrolment, student information and ticketing, then communication, infrastructure and operational integrations. AV and room monitoring has its own section.

Pressing Escape on a confirmation after connector configuration returns to the form without submitting another change.

No database migration beyond 0.14.0. An upgrade from 0.13.0 still applies the district connector migration.

Buttons, form fields and icon buttons share consistent sizes, labels and keyboard focus across the app, including Issue, Return, Mark unavailable and Edit on Loans. Tables scroll horizontally on phones when needed.

No database migration.

0.14.0: multiple connections for districts

Section titled “0.14.0: multiple connections for districts”

Add several named Jamf, Entra, Google Workspace or other connector instances in one organisation, with independent credentials and state. Choose organisation-wide or selected-campus coverage independently of the agent site. This supports a district using shared systems alongside individual schools’ connections.

Select the source for directory reads and account actions. Campus-scoped account access requires a confirmed link to a local person; device commands retain their recorded MDM source. SIS sync keeps external IDs and leaver detection separate by source.

Admin now opens settings instead of reopening completed onboarding. Connectors and desk setup offer Entra, Google Workspace, custom OIDC and SAML sign-in configuration; LDAP password sign-in remains a separate option.

Person privacy exports include their connector-source links, and erasure removes those links.

⚠ Migration: one application migration since 0.13.0. Verify a backup and update API, web and site agents together. Existing IDs, credentials, enabled state and agent bindings are preserved. Review the backfilled campus coverage. Agent secrets for additional connections must use instance IDs, and older agents cannot claim their work. Shared imports without a clear campus need local assignment.

Do not downgrade to the previous application after creating additional instances. Prefer a forward fix, or restore the verified pre-upgrade database with matching application and agent versions.

See Configuring a connector, Directory accounts and Connector agents. Upgrades from 0.12.0 also need the migrations listed under 0.13.0 below.

0.13.0School operations and assistant reviewsMigration

A guided setup takes the first administrator through choosing built-in, existing or no ticketing, licensed workflows and portals, access, connections and backups, with progress saved across sessions. Existing desks can open Admin → Desk setup without being forced through setup again.

Plan school projects, maintenance, purchases and events with shared approvals, dependencies, milestones, resources and bookings. Review synced roster changes and create lifecycle work; capture stocktake observations offline. Supported AV/room integrations and TeamViewer status mapping help identify equipment needing attention.

Purchasing can connect to Xero or MYOB. Review the supplier, account and tax mapping before exporting an approved purchase. Issue insights compare ticket and repair patterns, recurring categories and repeat devices across periods.

The native assistant can cite published knowledge, summarise tickets and draft responses. Changes require an expiring review of the recorded action. The optional Salesforce Agentforce advisory pilot is disabled until an administrator verifies its configuration and grants staff access.

Fixed annual billing is available in AUD, USD, GBP, EUR, NZD and CAD. Quotes, licences and invoices use the chosen currency; existing AUD contracts are unchanged. See Plans for quotes in the chosen currency.

Before updating: verify a backup. There are five new application migrations since 0.12.0, covering assistant controls, school operations and finance integrations, database-owner maintenance and subscription currency. Update API, web and site agents together.

0.12.0Department desks and a navigation refreshMigration

Upgrading from 0.11.1 includes 17 migrations. Back up and verify recovery before updating. Each school’s deployment needs its own upgrade; publication does not update it automatically.

  • Optional Facilities, Administration and other school departments, with service forms, department membership, explicit transfers, email routing and recurring maintenance. Add-ons require explicit activation and entitlement. Paused departments retain history and require schedules to be explicitly restarted.
  • Department boundaries extend to rules, reports, notifications and queued work. Department webhooks and external API-key access remain withheld.
  • Grouped workspace navigation in modern and classic, with desktop hover submenus, phone search, keyboard navigation and preserved personal arrangements.
  • Returning your appearance or navigation position to the school’s setting also clears an older choice on your other devices.
  • Jamf computer/mobile and optional Intune application inventory on device MDM records. Inventory does not establish installation or licence entitlement.
  • The Kandji connector is renamed Iru (formerly Kandji). Existing saved connections keep working; see the connector guide.
  • Opt-in Exchange Full Access and delegation revocation. Send As grants remain disabled.
  • Automation audit history, school and rule hourly caps, OBSERVE mode, campus conditions, previews and guarded approvals.
  • A software contract register with owners and renewal reminders.
  • Bulk device-location jobs with progress and cancellation.
  • Device CSV export uses the current filters across all matching devices.
  • Identity sections show an error instead of staying on “Loading”, and an incorrect authenticator setup code can be corrected without signing in again.
  • Wipe requests stop automatic replay after an uncertain result, and requesters must acknowledge an uncertain previous outcome before a new request.
  • Whole-school backups require unrestricted campus access, plus departments.manage when any department exists. Older archives need operator validation and a maintenance restore. Keep old archives and their encryption keys.
  • Closing tickets or submissions requires the relevant close permission everywhere, including bulk actions and tools.
  • API keys keep their issuer’s permission and campus limits. Tenant-wide SCIM requires an unrestricted campus grant, and older unbounded keys need rotation.
  • Source and native installs need the PowerShell Exchange module installed separately to use delegation; container installs include it.

Native installers and the mobile app are not published with this release.

0.9.0Devices added by hand, and photos on portal ticketsMigration

Three additive migrations.

  • The device register can hold devices no MDM enrolled, added by hand or by CSV, and fleet health shows them.
  • A device’s owner can be set from induction check-in, loan issue or the admin panel.
  • A ticket links back to the connector that filed it.
  • Closing a repair decrements parts stock, with an alert at the reorder point.
  • Portal requesters can attach a photo to a ticket.
  • Bulk loan issue and return report which rows failed.
  • An unreachable printer connector disables itself after five failures.
  • Security: a related-tickets panel could show another campus’s ticket subject and status to a site-scoped admin. Fixed.
0.8.0Loan groups synced from MDM, and printer status over timeMigration

Six additive migrations.

  • Each loan group syncs from its own MDM device group, and devices that leave the group are flagged as departed. Loans can be filtered by device kind, user group and text.
  • Repair submissions can carry an intake photo.
  • Printer status and toner are tracked over time, with alerts.
  • Fleet sync can be triggered on demand from Admin → Connectors → Fleet.
  • The identity panel shows licence spend, including licences on disabled accounts.
  • MFA enrolment shows a QR code.
  • Cost charts use Sydney time rather than UTC, so a repair or purchase may move to a different month after upgrading; yearly totals are unaffected.
  • Security: unverified device-ownership claims on portal repairs are flagged, and retired or disposed devices can no longer receive remote commands.

Known issue. The old Sync from MDM button on the Loans page fails; use the per-group Sync now control under Admin → Loan groups instead.

0.6.1 to 0.7.4

0.7.1 to 0.7.4Numbered repairs and loan due datesMigration

Two data-repair migrations: one clears a connector field that may hold a credential, the other disables misconfigured remote-access targets.

Security fixes with no change to how the desk is used. Idle sessions now actually expire, and plugboard-agent install-service now exists.

One additive migration.

  • A loan can have a due date, derived from a per-pool loan period, with a list of what is late.
  • The assistant can see the ticket queue.
  • Where a device was last seen is now its own permission, network.clients.view, rather than part of device.view. Grant it deliberately; see permissions.
  • /api/health no longer names the build commit, and HSTS is set everywhere.

Same product as 0.7.1, plus fixes: the assistant no longer disappears after one slow permission check, and tab changes under Account → Appearance apply without a reload.

The first published 0.7 release, including everything in 0.7.0. Additive migrations, one of which numbers every existing repair, oldest first. Take a verified backup first.

  • Repairs have numbers, and search finds a job by number whether it is a ticket or a repair.
  • Search can include your Zendesk or Web Help Desk, off until enabled per connector in Admin → Connectors. It searches as Plugboard’s credential, not as the person searching.
  • Hide and reorder your own tabs under Account → Appearance. Search also finds pages.
  • Network client tracking has a switch in Admin → Security, off by default, with a 1 to 90 day retention window.
  • An on-premises connector can be assigned to a site in Admin → Connectors, which managed deployments need for Active Directory, Synergetic, PaperCut, Web Help Desk and SNMP printers.
  • Ticket comments name their author.
  • Several screens are faster.
  • Security: portal request status is private to its owner, restricted documentation libraries are protected from people who cannot read them, agent tokens expire and rotate, the assistant requires a permission, and revoking a kiosk stops it.
0.6.1, 0.6.2Documentation, remote access and the network estateMigration

Fixes for 0.6.1: the Network page loads, the Meraki, UniFi and SNMP connectors run, and Documentation renders inside the desk frame.

What to do first. If you configured a network connector on 0.6.1, open Network after upgrading and press Refresh from every connector once.

Four migrations. The first published 0.6 release.

  • Documentation: internal runbooks with access rules, version history, owners and review cycles, shown on related tickets. Sold from Standard.
  • Remote access: a device-page button that opens your existing remote support tool. Starting a session is its own permission.
  • The network estate across Meraki, UniFi and SNMP. Client sightings are off by default. Sold from Standard.
  • Kiosks are devices, each named and revocable, instead of one shared key.
  • Global search reads article bodies.
  • Fixed: PaperCut on hosted deployments, and a portal reload that could show the previous student’s records on a kiosk.
  1. Take a verified backup. Four migrations.
  2. Upgrade, then go straight to 0.6.2. Three of the features this release adds do not work until then.
  3. Documentation and Network appear on their own for Standard licences and above. Turn either off under Admin, Features if you do not want it.
  4. If you enable Network, read client sightings before turning tracking on.
  5. Kiosks: claiming your first kiosk device switches the old shared key off for the whole tenant. Do the rollout in one sitting.