Skip to content
plugboard.appRequest a demo

Running the desk

Home

/dashboard. Where you land after signing in, and where Home and the school’s crest at the top of the menu take you.

The page greets you by the time of day and your first name, such as Good morning, Sam, with today’s date under it. When you hold cost.view, the Costs module is on and the school has term dates, the date line adds the term and week, such as Term 4, week 2.

Home is made of dashboards, shown as tabs, and each dashboard is a set of widgets. What a widget can show depends on the modules you have enabled and your permissions, so a small install shows less than a large one.

DashboardWidgets
My dayNeeds you, Spotted and My work down the left; Service health, Summary metrics and Recent activity down the right
Service deskSummary metrics, Team work, Service volume, Recent activity
Fleet & infrastructureSummary metrics, Service health, Loans & equipment, Quick links
ManagementSummary metrics, Service volume, Needs attention

My day opens by default. Switch dashboards with the tabs, or with the arrow keys once a tab has focus. A widget keeps what it has already loaded on screen while a dashboard changes, so switching back and forth does not blank the page.

Updated beside the title says when the figures last loaded, and the refresh button beside it reloads every widget. New ticket opens the same dialog as New in the menu, for whoever may raise tickets or repairs.

WidgetShows
Needs youWhat is waiting on you, with the overdue count as its figure
SpottedPatterns across tickets, loans and repairs
Summary metricsThe counters you choose, as one panel
Needs attentionExceptions, each with its reason and one action
My work, or Team workYour own work, or all the work you can access, from tickets, repairs or school operations
Service healthThe school’s services and their status, then monitors that belong to no service
Loans & equipmentAvailable and issued loan devices
Recent activityRecent changes you can access, grouped by day
Service volumeTickets created and resolved over time
Quick linksShortcuts to your working pages
Domains and expiryWatched domains and when their registration expires
Mail DNS healthMX, SPF, DMARC and DKIM health for each watched domain
Recent DNS changesThe latest DNS answers that changed

The three DNS widgets need dns.view. Domains are watched from Check my domain on Monitors.

Needs you leads with one figure: how much work is Overdue, the same count the ticket queue and the service level board show. It opens the overdue tickets. Under it, one row for each kind of thing waiting, with its count and the first two by name:

  • unassigned tickets;
  • approvals waiting for you;
  • suggested device fixes, each needing one approval before it runs;
  • changes you asked for in Ask, waiting for your review. This row opens the Ask panel’s History;
  • tickets due within four hours, while none are overdue;
  • requesters chasing without a reply, where the last two public messages are both theirs;
  • frustrated requesters (see sentiment);
  • a wellbeing concern to follow up, for whoever can read internal notes;
  • open tickets gone quiet, with no change for three days or more;
  • a service you own that is due for review, with when it fell due;
  • devices that need attention, warranties ending within 90 days, and repairs ready for collection, each marked Device or Repair.

A row appears only when it has something in it. With nothing waiting it says Nothing is waiting on you. Ticket rows count the open tickets you can see.

Spotted lists patterns, each with Review:

  • similar tickets that may be one outage, worked out from ticket statistics, with or without a model. A person confirms an outage; see the ticket queue;
  • loan pools running out, from how many have gone out over the last fortnight, with the day they are likely to run out;
  • devices that keep coming back for repair, from repairs lodged in the last 12 months. Several are gathered into one row with a bar for each device and Review repeats.

With nothing to show it says Nothing unusual.

Needs you and Spotted read the same answer, so the two widgets cost one request. Each part checks its own permission and module, and both need one of the permissions that open Ask.

Summary metrics shows its counters as one strip of figures, a cell each, once the widget has room for two; in a narrow column or on a phone they are rows. Every counter is a link to the list behind it: Open repairs opens the open queue, Loans available opens the available loans. Where zero is good news, such as Overdue or unassigned tickets, zero reads All clear rather than a bare 0.

On a dashboard that also has Needs you, the summary leaves Overdue and the counts Needs you lists to it, so each figure appears once.

The counters to choose from:

GroupCountersNeeds
TicketsMy tickets, Open tickets, Unassigned tickets, Waiting on requestermodule.tickets
RepairsOpen repairs, Pending repairs, Ready for collection, Closed repairsmodule.repairs
Loans and stockRegistered devices, Registered loans, Loans available, Loans issued, ProductsThe matching module
AttentionOverdue, Warranty expiring, Fleet issues, Repair satisfactionmodule.sla, module.assets or module.csat

Overdue is one number shared with the queue and the service level board. A repair and the ticket that mirrors it count once.

Where the school answers that families bring any device or that devices are shared only, the My day template counts Loans issued in place of Ready for collection. Dashboards people have already made their own keep their counters. See how student devices are provided.

Needs attention is colour-coded by urgency. Overdue work is urgent; unassigned tickets and devices flagged by the last fleet scan need attention soon; repairs ready for collection and warranties expiring within 90 days are for information. The header totals each level.

Service health shows the school’s services when it has any. It leads with a verdict, such as Email is having problems, 2 of 6 having problems or All 6 working, with a square for each service. The services follow, most critical first, each with a service it depends on that is in trouble, a provider service with a problem, a person’s message, or its monitors and their states. A service whose change is under way inside its window reads Planned work. Monitors that belong to no service and are not up are one row after them; when only one is, the row opens it. A high-criticality service that is down replaces the verdict with a band across the widget that opens the service. Seeing it needs service.view or monitor.view.

Without services, it leads with a one-line verdict, such as All 12 monitors up or 2 of 12 monitors down, and when it last observed anything. Monitors follow, with any that are down first.

Recent activity groups entries under Today, Yesterday and earlier dates, and every entry links to the record it is about, so you go from “a loan was issued” to that loan in one click. With audit.view, All history opens the Logs, and Set automatically opens them filtered to what the desk set by itself, such as triage values and tidy-ups, each of which can be undone on its record.

The numbers are live. A colleague closing a repair updates the counter without a page reload, because the desk updates itself.

Add widgets, From connected apps adds school-wide figures from connected apps. They work on dashboards and report boards, and scheduled board emails carry the same numbers.

FigureConnected appNeeds
Microsoft Secure ScoreMicrosoft Defender XDRmonitor.view
Staff without MFAMicrosoft Entra IDidentity.policy.view
Workspace accounts with 2-Step VerificationGoogle Workspace directoryidentity.policy.view
Microsoft 365 active usersMicrosoft 365 reportsreport.view
Microsoft 365 changes to plan forMicrosoft 365 Service Health, by servicemonitor.view
  • Figures are collected once a night per school, from the oldest enabled, organisation-wide instance of each connector. A school with two Microsoft tenants sees the older one’s figures.
  • Each figure is a whole-school number. Staff who see only some campuses get “not collected” instead.
  • They are aggregate only. Staff without MFA sends Entra the addresses of active staff in People, so students and guests are not counted. Entra returns totals, and nothing personal is stored. It needs Entra ID P1 or P2.
  • Workspace accounts with 2-Step Verification needs tenant posture reads turned on for the Google directory connector, with organisational units selected.
  • Microsoft 365 changes to plan for counts message centre posts updated in the last seven days for Exchange Online, Microsoft Teams, Microsoft Intune and Microsoft Entra. Only titles and dates are read.
  • Each figure names its source and when it was last collected. A failed read keeps the previous value, a figure not refreshed for two nights says so, and one never collected says so, never zero. Daily values are kept for 95 days.

Choose Customise to change the dashboard you are on. The editor opens beside it:

  • Add widgets lists the built-in widgets, figures from connected apps, your tools’ device groups and widgets already built on other dashboards. Build a widget makes one from the school’s report data, and, while the school’s AI can answer, Describe a widget proposes one from a sentence. Both need report.view. The report data includes First contact resolution and Reopen rate, so Home can show either beside SLA met, with a goal and the change on the previous period. See first contact resolution and reopen rate.
  • Drag a widget by its handle, or use the arrow keys, to move it. Its menu has Configure (what it counts, which queue, whose work), Duplicate, Show on phones, Move earlier, Move later and Remove.
  • Undo and Redo step through your changes.
  • Dashboard settings holds the dashboard’s name, Open this dashboard by default, Use coloured icons and the density of its widgets.

Nothing changes until you choose Save dashboard. Cancel discards the draft, asking first if you changed anything. If somebody else saved the same dashboard while you were editing, you can keep your changes on their version or discard them.

New dashboard starts from a template’s layout or a blank page. The new dashboard is yours alone and needs no permission. The … menu beside the tabs has Duplicate and Delete dashboard.

Somebody with dashboard.manage can choose Share from the … menu, and share it as either:

  • a shared dashboard, shown as a tab to the people you choose under Who can use this: roles, desks or campuses, or every member of staff for somebody who can reach every campus and desk; or
  • a template, copied from New dashboard.

A shared dashboard shares its layout, never its records: each person still sees only what their own permissions allow. Anybody it is shared with can Hide for me on a widget, and Show hidden widgets brings them back. Edit for everyone changes a shared dashboard or a template for everybody who uses it.

Show on a screen, with dashboard.link.manage, makes a link that shows the dashboard read-only on a wall screen with no sign-in. Only widgets built from report data show on a screen.

  1. Needs you. Anything overdue, and anything waiting on you.
  2. Spotted. A pattern you would otherwise hear about one call at a time.
  3. Service health. Whether the problem you are about to hear about is one you already know.
  4. Recent activity. What happened overnight, including anything lodged at the kiosk after hours, and what the desk set automatically.

My day is built for this order.

When closed repairs are still waiting for an outcome, a band at the top of Home says how many, such as 3 closed repairs need an outcome, so billing stays accurate. Add outcomes opens the batch outcome form. The same band is on Repairs. It needs the Repairs and Costs modules both on and repair.view, and the button needs repair.update. It updates as repairs change and goes once the last outcome is in. It appears only on these two pages.

The Repair satisfaction counter summarises ratings left on the tracking page after a repair closes. The average means little until enough repairs have closed, so on a fresh install ignore it for a term.

A single one-star rating is not a trend. Three in a fortnight from the same year group is.

The bell at the top of the menu is separate from Home and carries things needing attention: monitor alerts, overdue work, backup failures. Those arrive whichever page you are on.

Which widgets and counters can show anything depends on the modules you have on. A school not running service level targets has no overdue work to count.

For a different cut of the same data, use reports, which can also be scheduled to arrive by email each Monday.