Skip to content

The dashboard

/dashboard. Where you land after signing in.

The desk’s overview: the work and services that need your attention. It is made of views, shown as tabs across the top, and each view 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.

View Widgets
My day Summary metrics, Needs attention, Service health, My work, Recent activity
Service desk Summary metrics, Team work, Service volume, Recent activity
Fleet & infrastructure Summary metrics, Service health, Loans & equipment, Quick links
Management Summary metrics, Service volume, Needs attention

My day opens by default. Switch views 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 view changes, so switching back and forth does not blank the page.

Widget Shows
Summary metrics The counters you choose, as one panel
Needs attention Exceptions, each with its reason and one action
My work, or Team work Your own work, or all the work you can access, from tickets, submissions or school operations
Service health Monitored services and when each was last observed
Loans & equipment Available and issued loan devices
Recent activity Recent changes you can access, grouped by day
Service volume Tickets created and resolved over time
Quick links Shortcuts to your working pages

Summary metrics balances its counters into even rows. Every counter is a link to the list behind it: Open submissions opens the open queue, Loans available opens the available loans. Where zero is good news, such as SLA breaches or unassigned tickets, zero reads All clear rather than a bare 0.

The counters to choose from:

Group Counters Needs
Tickets My tickets, Open tickets, Unassigned tickets, Waiting on requester module.tickets
Submissions Open, Pending, Ready for collection, Closed module.repairs
Loans and stock Registered devices, Registered loans, Loans available, Loans issued, Products The matching module
Attention SLA breaches, Warranty expiring, Fleet health, Satisfaction module.sla, module.assets or module.csat

Needs attention is colour-coded by urgency. SLA breaches are 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, so you can see at a glance whether anything is urgent.

Service health 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 as tiles, with any that are down first.

Recent activity is the part worth using. Entries are grouped 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 rather than searching for it. It is the fastest way to answer “what happened while I was at lunch”.

The numbers are live. A colleague closing a repair updates the counter without a page reload, because the console updates itself. Refresh reloads every widget on the view.

Choose Edit view to change the view you are on. From the editor you can:

  • Add widgets from the list, and remove the ones you do not use.
  • Drag widgets into a different order, or use Move earlier and Move later from the keyboard.
  • Set each widget’s size (small, half width or full width), its density and, where it applies, what it counts: which metrics, which queue, whose work.
  • Rename the view, tick Open this view by default, duplicate it, reorder the tabs, or delete the view.

Nothing changes until you choose Save views. Cancel discards the draft. If a save fails, your draft stays on screen until you choose to reload.

New view starts either a blank view or a copy of a team template. You can keep up to twelve views. They are personal: visible only to you, and they need no permission.

Somebody with dashboard.manage can choose Save as team template while editing a view. A template is available to everyone in the desk when they start a new view. Publishing copies the view’s configuration, including unsaved layout edits. It shares no records, because each person still sees only what their own permissions allow, and it does not change anybody’s existing views.

The same people can update a template or delete one. Each publish, update and removal is recorded in the audit log. Wildcard administrators already hold dashboard.manage; see permissions.

A morning routine that works:

  1. Needs attention. Anything urgent, before it gets worse.
  2. Unassigned work. Work nobody has picked up.
  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.

My day is built for this order.

From 0.17.1, when closed repairs are still waiting for an outcome, a banner at the top of the dashboard says how many, such as 3 closed repairs need an outcome, and asks you to record parts and cost so billing stays accurate. Add outcomes opens the batch outcome form. The same banner is on the Submissions list. It needs the Submissions module and repair.view, and the button needs repair.update. It updates as submissions change and goes once the last outcome is in. It used to be a notification that came back on every page; it now stays on these two screens.

The Satisfaction counter summarises ratings left on the tracking page after a repair closes. It is only meaningful once enough repairs have closed to make the average mean something, so on a new install it is worth ignoring for a term.

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

The bell in the top bar is separate from the dashboard and carries things needing attention: monitor alerts, SLA breaches, 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 SLA targets has no SLA breaches to count.

If you want a different cut of the same data, that is what reports are for, including scheduling one to arrive by email each Monday.