Deucalion Docs
Admin Reference
ReferenceAn information-oriented lookup resource. Use it to find specific values and definitions.
admindashboardadmintriage

Dashboard Route Reference

Understand the admin dashboard’s attention cards, KPI summaries, and direct launch paths into the desks that own live work.

Before you start

  • You need the office-side triage surface, not a workflow walk-through.

Expected outcome

You can use the dashboard as a launch desk and understand what each summary card hands off into next.

What this route is for

The dashboard is the default office overview route. It brings together current pressure, upcoming work, recent activity, coverage signals, and integration health so admins can open the correct owning desk quickly.

Visibility and capability notes

ItemDetails
Route iddashboard
VisibilityCustomer-facing core route in the admin shell.
Capability notesThe dashboard itself is broadly visible, but some linked desks such as Finance, Quotes, Work Orders, or Connected Systems may still be hidden by workspace capability rules.
Direct inboundDefault shell route after sign-in, shell home navigation, and common "back to dashboard" flows.

Main regions and actions

RegionWhat it does
Announcement stackWorkspace notices and release-style prompts.
KPI cardsOverdue, total assets, operational count, and active fault pressure.
Needs AttentionOpens urgent operational queues quickly.
Work Orders and Quotes summariesSurfaces commercial or remedial workload without opening the full desk first.
Upcoming InspectionsLaunches the office into scheduling or inspection review.
Recent ActivityHighlights recent cross-route changes.
Site Coverage and Fire Damper OverviewShows estate distribution and specialist signal.
Integration SummaryShows Joblogic connection health and opens integration review.

Key actions

  • Open Scheduling from the header action.
  • Open Reports from the header action.
  • Drill into inspections, assets, defects, work orders, quotes, map, and integration review from summary cards.
  • Use the dashboard as a prioritisation surface, not as the place to edit the underlying records.

Filters and URL state

  • The dashboard does not expose meaningful customer-facing hash filters.
  • There are no major route-specific dialogs to manage from the dashboard itself.
  • Most state is live summary state rather than bookmarkable workspace state.

Outputs and side effects

  • The dashboard mainly causes navigation side effects by opening other routes.
  • It does not own core record creation, deletion, or export flows.
  • Summary numbers depend on current data in inspections, defects, assets, quotes, work orders, sites, and integrations.
  • Default admin sign-in route.
  • Shell home navigation.
  • General "return to dashboard" actions from the admin shell.
  • #/scheduling
  • #/reports
  • #/inspections
  • #/assets
  • #/defects
  • #/work-orders
  • #/quotes
  • #/map
  • #/integrations or Connected Systems review for integration health

Indirect handoffs

  • The dashboard determines which desk the office team opens first each day.
  • Commercial, remedial, and export desks all rely on the dashboard staying honest about pressure, but the fixes still happen elsewhere.
  • Platform-only links such as users or health may appear for broader roles, but they are outside this customer-facing set.

Troubleshooting

SymptomWhat to check
A card looks staleOpen the owning desk first. The dashboard is only reflecting upstream data.
A linked desk is missingCheck feature access or capability visibility for that workspace.
The dashboard looks quiet but engineers report active workRe-check Scheduling and Inspections. The dashboard is a summary, not the live planner.

On this page