StationCommand  Help Center
Administrator & Operations Guide

From first login to mission ready.

Department-facing setup and operations for StationCommand B.3.4.23, including the current personnel, credential, email, statistics, security, mapping, and incident workflows.

Verified against B.3.4.23Department-facing setupServer/OAuth/SSO deployment excluded

Guide scope

This guide begins after StationCommand is online and the initial Administrator can sign in. Server/database deployment, OAuth client creation, SSO provider setup, and external infrastructure remain installer-managed.

Mission-ready path

  1. Validate license, department identity, time zone, and station locations.
  2. Build Personnel, access roles, rank hierarchy, Apparatus, and Active911 device assignments.
  3. Configure Active911 API/webhook, station displays, maps, weather, and optional integrations.
  4. Configure Credentials & Certifications, email/reminder policy, public verification, and categories.
  5. Run incident, privacy, EOC/Home, statistics, and security tests.
  6. Complete the Mission-Ready checklist.

Administration workspace

Current B.3.4.23 Administration includes Email & Notifications, Department Branding, License, Station Displays, EOC Management, Active Incidents, Call Classification, Incident Records, Personnel, Credentials & Certifications, Apparatus, Announcements, Address Notes, Reports, Analytics & Security, Public Display, CSV Import, Integrations, Mapping, Weather, System Status, and Danger Zone. Top-level settings panels are collapsible.

Department Branding & time zone

Set the department name/logo and Department Time Zone. The configured IANA time zone drives statistics, reports, station clocks, calendar grouping, public statistics/weather timestamps, and server-side day/month grouping.

Personnel & rank hierarchy

Personnel records can exist with or without login access. Configure active/inactive status, optional email/login authorization, access permission, rank, personnel number, participation, and linked Active911 devices.

Custom Rank Hierarchy supports custom names, abbreviations/public names, drag ordering, and tied hierarchy levels. Access permission (User/EOC Manager/Training Admin/Admin) is separate from rank.

Inactive members retain history, certifications, verification profiles, and badge QR records but are removed from current operational selections and cannot sign in.

For complete instructions, see Personnel & Apparatus.

Apparatus

Administration → Apparatus is the canonical apparatus registry. Configure apparatus identity, one or more available Active911 devices, map icon, and tracking color. Device assignments are exclusive across Personnel and Apparatus.

Credentials & Certifications

Administration → Credentials & Certifications manages public verification IDs, photos, affiliation, certification evidence, approvals, physical badge QR codes, certification categories, Michigan EMS expiration sync, and certification ordering.

Members can submit certifications and pending updates. Credential managers can approve/reject them. Verified records remain public while a member's proposed revision waits for approval.

See Credentials & Certifications for the full workflow.

Email & Notifications

Configure global Email Alerts, personal reminders, Admin/Training Admin reviewers, optional department expiration recipient, SMTP delivery, tests, and diagnostics. Reminder scheduling infrastructure is installer-managed; department admins can use Send Test Reminder Email and Send Due Reminders Now.

See Email & Notifications.

Active911 integration & device directory

Administration → Integrations is the canonical home for Active911. Configure API refresh token, webhook, alert window, tracking switches, manual sync/backfill/import actions, and device-directory resync.

Preferred device workflow: Resync Devices from API, then assign available devices on Personnel/Apparatus. CSV device import is a fallback. Legacy /device routes redirect into Personnel.

See Active911 Setup and Device Directory.

Station Displays & incident history matching

Pair permanent TVs/browser devices at /display, compare the six-digit code, approve/deny, assign the station, and manage display/rotation settings.

Incident History Address Matching can use exact units, ignore units everywhere, or ignore units only at selected buildings.

See Station Displays & Pairing.

Mapping

Mapping controls map sources, ArcGIS/geocoder/road snap, overlays, aircraft, EOC defaults, Multiview, satellite priority, Street View mode, and diagnostics. Static Street View is the recommended default; Dynamic Panorama remains available.

CAD agency mapping includes Nearby GPS tolerance for neighboring jurisdictions while wrong-state coordinates remain rejected.

See Mapping & Multiview.

Weather & lightning

Verify department weather point, NWS conditions/alerts/radar, internal alert testing, and optional Xweather/Vaisala lightning settings. See Weather & Lightning.

Incident operations

Incident Records supports filters, editing, classification, map pin verification, participation, reactivation, and manual incident creation. Manual incidents can be active for 30 minutes or historical-only and otherwise participate in normal classification, statistics, address history, mapping, EOC, and responder participation.

Public incident data remains generalized: exact address/unit, narrative, responder identity/status, exact timestamps, CAD IDs, and raw CAD coordinates are not exposed through public incident APIs.

Department Statistics

Authenticated Department Statistics supports Month, Full Year, and Overall views. Current-year Full Year view includes a blended projection. Data-aware selectors, comparisons, mutual aid, classification breakdowns, and competition-ranked top addresses are included.

See Department Statistics.

Sessions & security

Default maximum sessions are 30 days. Analytics & Security can configure Member vs privileged maximum lifetimes, inactivity timeout, and recent-auth protection. Members can Sign Out of All Sessions; Admins can revoke another user's sessions.

See Sessions & Security.

Analytics & Security

Contains public usage, security events, Application Audit Trail, credential verification analytics, approximate IP geography/local GeoLite2 status, and session security. Respond API access events are audited without recording bearer tokens.

Mutual Aid & CAD agencies

Configure CAD agency prefixes, home-department mapping, service-jurisdiction validation, reporting names, and Nearby GPS tolerance. See Mutual Aid.

Emergency Operations Center mode

EOC supports activation-specific map modes, weather/aircraft/map-control overrides, crew/apparatus assignment, status, call reclassification, narratives, clearing resources, and Quick Reference.

StationCommand Home

Configure Home instances under Integrations with webhook URL, signing secret, Respond API bearer token, and test controls. Home can use the same bearer token for the browser-safe Mapping API. Signed webhooks advertise tracking availability but never contain responder/apparatus coordinates; eligible coordinates come from the protected Respond API.

Troubleshooting quick reference

ProblemStart here
No new incidentsIntegrations → Active911 → Force Active911 Pull; review API/webhook status and recent errors.
Active911 devices missingIntegrations → Active911 → Resync Devices from API. Use CSV fallback only if necessary.
Person/apparatus device unavailableCheck whether the device is already assigned elsewhere; device assignments are exclusive.
Credential needs approvalCredentials & Certifications → select person → review pending submission/update.
Michigan EMS controls missingVerify the certification category is marked Michigan EMS sync capable by a full Admin.
Michigan EMS check rejectedUse a verified record with license number and approved mi-emsis Issuer Verification Link.
Certification email not deliveredEmail & Notifications → Test SMTP Connection → Advanced Email Delivery Diagnostic → review accepted/rejected/SMTP response.
Member cannot sign inPersonnel → verify active status, authorized login, enabled account, and invite/account state.
Display won't pairUse /display, compare current six-digit code, then approve under Station Displays.
Prior-address history too narrow/broadStation Displays → Incident History Address Matching.
Street View ZERO_RESULTSMapping → Test Google Street View; local ZERO_RESULTS may mean no panorama at the test point/radius rather than a credential problem.
Nearby mutual-aid GPS rejectedCall Classification → CAD agency mapping → review Nearby GPS tolerance and jurisdiction boundary.
Responder not on private mapRead Devices scope, department tracking enabled, member opt-in, correct device assignment, RESP/ARRIV, recent GPS.
StationCommand Home test failsVerify URL, enabled state, signing secret, Respond API token, and matching Home configuration.

B.3.4.23 Mission-Ready checklist

Department & license

  • Department name/logo and Department Time Zone are correct.
  • License validates with expected station count and entitlements.

Personnel & access

  • Active/inactive personnel status is correct.
  • Login authorization/invitations are correct.
  • User/EOC Manager/Training Admin/Admin permissions are correct.
  • Custom rank hierarchy, abbreviations/public titles, and tied levels are approved.
  • Personnel display order is approved.

Active911 & apparatus

  • API pull and webhook processing succeed.
  • Device directory has been resynced from API.
  • Personnel and Apparatus device assignments are correct and exclusive.
  • Responder/apparatus tracking privacy has been tested if enabled.

Credentials & certification

  • Public Verification IDs/profiles are configured for intended personnel.
  • Certification categories and colors are approved.
  • Michigan EMS sync capability is enabled only on intended categories.
  • Issuer Verification Links/public proof/evidence settings are reviewed.
  • Member submission → approval/rejection workflow is tested.
  • Badge QR creation, scan, revocation, and analytics are tested where used.
  • Inactive member public-affiliation behavior is understood.

Email & notifications

  • Email Alerts policy, Admin/Training Admin reviewers, and personal reminders are correct.
  • Test SMTP Connection succeeds.
  • Advanced delivery diagnostic is understood and available for troubleshooting.
  • Test reminder and approval-request workflow are verified.

Stations & displays

  • Every station address/map point is correct.
  • Every permanent TV/browser is paired and assigned to the correct station.
  • Idle rotation/readability and incident takeover are tested.
  • Incident History Address Matching mode/building list is approved.

Mapping & weather

  • Known-address mapping/road snap passes.
  • Static or Dynamic Street View mode is intentionally selected and tested if used.
  • CAD agency service boundaries and Nearby GPS tolerance are verified.
  • Aircraft/weather overlays are tested where enabled.
  • NWS weather/radar/alerts and optional lightning are tested.

Incidents, stats & privacy

  • Live incident, edit, reclassify, reactivate, and manual incident workflows are tested.
  • Public generalized address/time behavior is reviewed.
  • Department Statistics Month/Full Year/Overall views are reviewed.
  • Mutual-aid counts and CAD agency mappings are verified.

Security, EOC & Home

  • Session Security settings are approved; Sign Out of All Sessions/Admin Revoke Sessions are understood.
  • Application Audit Trail is accessible.
  • EOC workflow is tabletop-tested if used.
  • Every configured Home instance passes its test; Home tracking is tested privately if enabled.

Final verification

  • System Status is healthy.
  • At least one Administrator and one operational officer/member complete the end-to-end test.
  • Department understands StationCommand is supplemental and does not replace primary dispatch/911/radio/paging systems.
MISSION READYPlace StationCommand into operational service after all required department-specific items above are verified.