16 docs tagged with "missions"

Provides a paid-plan persona-aware natural-language workspace for scoped AidOrbit data answers, product documentation how-to answers, overviews, reports, Mission draft imports, action previews, and confirmation-required next steps.

Updates Mission details, schedule, volunteer operations settings, requirements, map points, GoodNearby visibility, image-capable description content, optional logistics templates, Galaxy AI shift drafting, and ICS planning fields when the Mission requires ICS / Incident Command.

Shows live event-day mission instructions, attendance context, and current operational status.

Combines event planning and Mission shift review into one operational calendar scoped by the global program selector, with add-Event, add-Mission, filters, right-side detail preview, multi-date Event scheduling, open-ended Mission registration windows, Event qualification requirements, image-capable Event descriptions, public or private Event audience settings, direct volunteer assignment and batch hour logging for Events and Mission shifts, a Future Calendar Items table for current and upcoming records, and focused record workflows. The old Events route redirects here.

Shows operational changes, notes, and audit history for a Mission. ICS 214 appears only for Missions that require ICS / Incident Command; routine Missions can export the activity log as CSV.

Shows the live Mission operations console with organization-scoped active Missions, map context, Android telemetry, battery readiness, alerts, AI Assist weather visibility and alert summaries, logistics readiness, communications, roster, persisted tracking policy, and activity logging. Program Leaders and Program Staff with Mission Command access can open it from Programs navigation. When no active Mission exists, Mission Command shows an empty state that links to the Missions & Events calendar so staff can create or schedule a Mission. ICS forms, COMU status, ICS 205, and incident-command framing appear only when the selected Mission requires ICS / Incident Command.

Shows a role-aware Mission workspace. Program Leaders and Program Staff get an operations-first command view with roster, signup, operations, logistics, photo, message, incident, and escalation actions. Volunteers get a signup-first view with shift selection, requirements, program access, directions, team or family participation, photo upload status, and their own registration state.

Lets volunteers search the full visible Mission and program catalog by keyword, organization, program, location, distance, timing, eligibility, and next steps.

Provides incident command forms plus a COMU workspace for ICS 205 channels, ICS 205A contacts, operational messages, communications equipment, logistics-backed resource context, demobilization, print, PDF, and XLSX outputs for a Mission that requires ICS / Incident Command.

Tracks Mission resources, staging, transportation, facilities, logistics requests, issue records, returns, shortage flags, logistics map pins, and CSV export without requiring ICS for routine Missions.

Prepares general Mission roster views and print-ready roster documents. ICS 211 appears only for Missions that require ICS / Incident Command.

Lets Program Leaders and authorized program staff customize reusable Mission templates for the selected program before staff create or edit Missions.

Routes users into the correct mission discovery or mission management experience.

Shows missions a volunteer can browse, has joined, or has scheduled.

Creates a new Mission with details, volunteer setup, operations settings, map points, optional logistics planning, searchable requirements, Program Leader contact defaults, image-capable description content, Launch AI Assist shift weather summaries, Galaxy AI shift drafting, and visibility. ICS planning fields appear only when Requires ICS / Incident Command is enabled for an eligible Disaster Response / Emergency Management Program.

Manages only the selected program's volunteer-facing GoodNearby configuration, previews, publishing state, program public copy, program contact details, and public page settings after at least one program exists. Mission-specific GoodNearby visibility is edited from the Mission editor.