Overview#
A military intelligence analyst and a PSAP dispatcher both log into the same platform, but they should not land on the same screen. The analyst needs tactical feeds, ISR previews, and fusion workspace access. The dispatcher needs incident control, workforce posture, and communications pivots. Presenting a generic set of tiles to both users wastes their first moments of every shift and makes the platform feel like a product built for someone else. The Role-Based Operations Dashboard solves this by adapting its default modules to the operator's persona automatically.
The dashboard is the canonical web home workspace: a single starting point that shifts its default layout based on mission role, current operational posture, and live platform activity. Investigators, supervisors, military analysts, legal reviewers, administrators, and PSAP users each land in a workspace that prioritises their immediate tasks.
Key Features#
- Persona-Aware Module Defaults: Dashboard module visibility changes by operational role so each user starts with the most relevant overview, alerts, and pivots for their job. No configuration required at the individual user level.
- Role Briefing Panel: Structured briefing content summarises the current operating context, recommended focus areas, and key shift priorities for the active persona.
- Live Operational Posture: Real-time alert, investigation, and incident summaries provide an immediate view of current load, urgency, and response status, updated via GraphQL subscriptions and WebSocket state feeds.
- Hub Launch Surface: Direct entry cards route users into specialist workbenches including cyber, tactical, ISR, geospatial, simulation, communications, messaging, CERT, forensics, and earth observation.
- Cross-Domain Preview Widgets: Shared preview widgets expose tactical, ISR, fusion, and satellite-monitoring posture without requiring users to leave the home view.
- Shared Dashboard Shell: Layout persistence, responsive modules, and shell-level personalisation provide continuity across desktop and mobile workflows.
Use Cases#
- Investigator Start of Shift: Investigators land on a view that emphasises recent alerts, active cases, search, mission planning, and collaboration so they can move directly into casework.
- Military Analyst Operating Picture: Military users start with tactical, fusion, ISR, and earth observation previews, then pivot into dedicated workbenches for deeper mission analysis.
- Supervisor Oversight: Supervisors assess current operational tempo, identify overloaded queues, review hub status, and prioritise the next response actions for their teams.
- PSAP Dispatch Coordination: Dispatch-focused users begin with incident control, alerts, workforce posture, and communications pivots aligned to live operational demand.
Integration#
- GraphQL alert and investigation queries for live counts and summaries
- WebSocket updates for operational state changes
- Tenant and user profile context for persona defaults
- Mission planning, collaboration, and shared dashboard shell services
- Direct navigation into specialised workbenches
Open Standards#
- GraphQL (June 2018 Specification): All dashboard queries, mutations, and live subscription feeds use a GraphQL API, enabling clients to retrieve exactly the metrics and panel data they need and to receive server-pushed operational updates via named subscriptions.
- RFC 6455 (The WebSocket Protocol): Real-time operational posture updates, including alert counts, incident status, and PSAP events, are pushed to connected clients over full-duplex WebSocket connections managed by the platform's WebSocket broker.
- JSON Web Token (JWT) / RFC 7519: Every dashboard query and mutation is gated by a JWT carrying the user's identity, tenant scope, and role claims; the server validates the token signature against published RS256 JWKS before resolving any field.
- OAuth 2.0 Bearer Token Usage / RFC 6750: Authenticated clients present JWTs as Bearer tokens in HTTP Authorization headers; the platform's routing middleware enforces this scheme and sanitises tokens from logs.
- Role-Based Access Control (RBAC) / NIST INCITS 359-2012: Persona detection and module-visibility rules are implemented as a structured RBAC layer; each user's assigned roles (investigator, military analyst, PSAP dispatcher, supervisor, legal reviewer) map directly to the set of dashboard panels surfaced at login.
- JSON / RFC 8259: Dashboard panel definitions and layout configurations are stored as JSONB documents and exchanged as JSON payloads, with server-side atomic merge operations applied directly within PostgreSQL.
Last Reviewed: 2026-03-24 Last Updated: 2026-04-14