Operational summary
Administrators create per-node missions in the hub (missions drawer): title, description, and status. When assigned, operators can open them under the Missions tab in the mobile app if the feature flag is enabled in remote config.
Operators can mark a mission completed from the phone; the update is stored in Supabase and reflected for the team in the web dashboard.
Deep dive
Missions are the structured way to ask field operators to do something concrete: check a point, attend an event, go to a geofence, complete a maintenance task. Before missions, that coordination went over chat or radio and got lost in noise; missions add traceability, assignment, and state.
The creation flow is from the web hub: the admin opens the missions drawer, picks the destination node or team, writes title and description, and saves. The mission appears immediately in the panel list and, if the module is enabled in remote config, in the corresponding operator's mobile app. The app shows missions in a dedicated tab and lets them mark missions as complete.
When the operator marks complete, the change persists in Supabase and the dashboard reflects it in its list. That bidirectionality gives the operations center real-time visibility on the team's progress: how many missions are open, in progress, completed in the last hour. For later reports, the history stays as audit of work done.
Operational tips: use short but specific titles ('Inspect north perimeter'), use the description for details the operator needs at the moment (safety notes, gate code, on-site contact), and close missions promptly so the panel reflects reality. Missions left open contaminate reports.
Open in product