Skip to content
ARGUS User Manual

Dashboard overview

The Dashboard at / is where you land after sign-in. It’s the command overview: a one-screen glance at your organisation’s current state. Operators use it to jump into active ops; analysts use it to scan the mix of mission types and priorities; admins use it to spot the platform-status banner and the fleet/dock counts.

The layout, top to bottom

Header strip

A single-line banner that reads COMMAND OVERVIEW with a current-year indicator on the right. The status bar below it shows three live badges:

  • SYSTEM — OPERATIONAL (green dot)
  • COMMS — ENCRYPTED (cyan dot)
  • UPLINK — ACTIVE (cyan dot)

When the backend detects a platform incident these flip to amber / red and an extra banner renders above the strip. The incident banner is admin-visible by default and can be globally toggled by superadmin. (Today the status chips are static indicators; the incident banner is aspirational until the platform-status service ships.)

Plan badge

Shows your active org’s subscription plan — Guardian, Tactical, Command, or Sovereign — colour-coded. The plan determines feature availability (SSO, custom roles, AI copilot, E2E encryption, offline mode).

Stat cards (.dash-stats)

Four cards, each clickable to navigate deeper:

  • Total operations — count of all ops in scope. Links to /operations.
  • Active ops (green) — operations with status: active. Links to /operations.
  • Completed ops (purple) — status: completed. Links to /operations.
  • Assets — distinct asset IDs referenced across missions.

The first three hide if you lack operations.view.

Analytics grid (.dash-analytics)

Six charts, gated on permissions and data:

  • Operations breakdown — bars by status: planning, ready, active, completed, aborted.
  • Mission types — bars by missionType (SAR, recon, surveillance, combat, humanitarian, training, escort, logistics, other).
  • Priority distribution — critical / high / medium / low (only when ops have priorities).
  • Activity (7d) — sparkline column per day for the last 7 days.
  • Fleet status — total drones, flying, low battery, nominal. Driven by FleetService telemetry activated on ngOnInit.
  • DJI Docks — total, online, offline.

Recent operations

The 5 most recently updated ops (sorted by updatedOn || createdOn). Each card: status dot, codename or name, type + priority chips, status label, last-updated date, Open → /operations/:id.

Quick access

Four tile links: Operations, Profile, Settings, About.

What you actually do here

  • Join a live op — find the green ACTIVE dot in the recent-ops list, click Open, and Launch console from the mission detail to jump to /ops/:id/live as a participant.
  • Create a new op — Operations quick tile → /operations → + New → /operations/new.
  • Check fleet health — glance at the fleet and DJI dock cards. Low battery > 0 is amber; dock offline > 0 is red.
  • Ask the copilot — the floating chip opens the drawer, see The ARGUS Copilot.

Permissions

The dashboard renders differently per role. Every card below is gated on a signal from PermissionService:

You seeIf you have
Operations stat cards, breakdowns, recent ops, quick-access Operations tileoperations.view
Fleet status cardeveryone (fleet telemetry is org-wide)
DJI dock cardeveryone
Teams quick links (when added)team.view
Platform incident banner (aspirational)superadmin

Role-specific behaviour:

  • Operators typically see only operations they’re a participant in (Firestore rules filter the list).
  • Analysts / observers see read-only across all org ops.
  • Admins also see the status banner when there’s an active platform incident.

Keyboard shortcuts

  • / — focus global search (aspirational at shell level).
  • Alt+1 — Dashboard. Alt+2 — Operations.
  • C — open copilot (wired in Operation Console; aspirational elsewhere).
  • Esc — close any open drawer.

G D / G O VS-Code-style chord shortcuts are planned but not currently bound.