From first login to mission ready.

Guide scope

This guide begins after the StationCommand server is online and the initial administrator can sign in. Server deployment, database deployment, OAuth credential creation, and SSO provider configuration are installer-managed and intentionally excluded.

The mission-ready path

The StationCommand menu

The signed-in menu is the primary launcher for department members. Available cards are controlled by the user's role and by the StationCommand license entitlements.

StationCommand menu. Cards can be favorited and dragged to create a personalized layout.

Officer incident controls

Chief, Deputy Chief, Captain, and administrators can receive active-incident controls on the menu. Authorized officers can add 30 minutes to the active display timer or clear an incident from station displays.

Personalizing the menu

Use the star on a card to favorite it. Drag cards to arrange them. Reset Layout restores the default arrangement.

Administration workspace

Administrators use the Administration workspace to configure StationCommand and manage operational data. Like the member menu, administration cards can be favorited and rearranged.

The Administration workspace in VB.2.3.5.

StationCommand License

Open Administration → StationCommand License. Enter the license key supplied for the agency and use Save & Validate License.

What to verify

• The plan and license status are correct.
• The licensed station count is sufficient for the number of configured physical stations.
• The expected entitlements appear as enabled.
• The public-statistics monthly limit matches the purchased plan.
• The validation status shows a recent successful check.

The license panel also reports the configured installation count, validation endpoint, cached entitlement status, last validation time, and the entitlements returned by the license server.

Department Branding

Open Administration → Department Branding. This identity is used throughout internal and public StationCommand screens.

If needed, Use StationCommand Default Logo restores the built-in StationCommand identity.

Station Displays

Open Administration → Station Displays. Every physical station is a configurable display location and routing origin.

Add a station

1. Select Add Station.
2. Enter a clear station name, such as Station 1 or Headquarters.
3. Enter the station address.
4. Use Map Address to geocode it.
5. Verify the marker position. The map marker is draggable and can also be placed by clicking the map.
6. Select Save Station.
7. Use Open Display to verify the station dashboard.

Station locations affect routing origins and several map/weather behaviors, so verify the point is on the correct property.

Personnel, accounts, devices, and apparatus

The Personnel Directory combines member identity, login access, Active911 devices, rank, personnel number, participation statistics, and apparatus management.

Ranks available in VB.2.3.5

Chief, Deputy Chief, Captain, Firefighter, MFR, and Apparatus.

Create or edit a person

• Set the member's display name.
• Choose rank.
• Add an optional personnel number.
• Link the member's authorized login account.
• Choose whether the member is included in participation/statistics.
• Link one or more Active911 devices to the person.

Access levels

Authorized accounts can be assigned User, EOC Manager, or Admin access. Accounts not yet linked to a personnel record are shown separately.

Apparatus

Apparatus can be created even when no Active911 device exists yet. A device ID can be linked later. Standalone apparatus can be edited or deleted from the Personnel page.

Merge duplicate people

The Merge People tool moves devices and manual participation from a source person into a target person. Use this when duplicate personnel records were created during import or device mapping.

Active911 integration

Active911 provides the core incident and response feed. StationCommand supports both API polling and Active911's Other webhook integration.

Active911 configuration in Administration → Integrations.

StationCommand-side setup

• Set Active911 API to Enabled.
• Paste the Active911 Refresh Token.
• Set the polling interval. VB.2.3.5 accepts 15–3600 seconds.
• Set the Active Alert Window in minutes.
• Enable the webhook.
• Select Generate New Webhook Secret.
• Save Active911 settings.
• Copy the generated Active911 “Other” Integration URL into Active911.

Use the dedicated illustrated guide for the full Active911 token and webhook process: Active911 Setup Guide.

Manual synchronization tools

• Force Active911 Pull — immediately request current data.
• Import Current Year — backfill the current year's incidents.
• Import All Available Calls — import all available historical calls.

Weather

Open Administration → Weather. StationCommand uses the National Weather Service for forecast information, alerts, and weather display functions.

Forecast location

Configure or verify the weather forecast point used by the department. StationCommand is designed to use station geography when possible; the selected point should represent the department's operating area.

Verify NWS status

The Weather page includes National Weather Service status information. Confirm forecast and alert retrieval is healthy before relying on the weather slide.

Operational test

• Confirm current weather data loads.
• Confirm the 7-day forecast loads on a station display.
• Confirm radar loads and is centered appropriately.
• Use available test/refresh controls and verify the display responds.
• Verify severe-weather alert behavior.

Incident operations

StationCommand receives incident information, presents active calls on station displays, tracks responder activity, and retains incident records for later review and analytics.

Incident Records

Open Administration → Incident Records to search and review calls. The current build supports filtering by status, year, month, date range, category, and text search.

Editing an incident

The Incident Records editor includes the incident category, map pin, activity log, and responder participation. Administrators can reclassify incidents and reactivate calls when appropriate.

Active incident controls

Chief, Deputy Chief, Captain, and administrators can extend an active incident by 30 minutes or clear it from the station displays from the main menu.

Historical import

Administration → CSV Import accepts an Active911 alert export. Existing incidents are updated by Active911 alert ID and new records are added as historical calls.

Address Notes

Address Notes let administrators store operational information tied to a location, including property access, hazards, responder-safety information, and other notes useful during an incident.

Use Administration → Address Notes to add, review, edit, or remove saved notes. Keep entries concise, factual, operationally useful, and appropriate for department personnel to view.

Announcements

Administrators can create and manage department announcements in Administration → Announcements. Signed-in members can view current announcements from the main menu, and announcements can also appear on configured displays.

Use announcements for department-wide operational or informational messages. Review older announcements periodically and remove items that are no longer relevant.

Public Display & Public Statistics

The Public Display section controls which public-statistics screens participate in the rotation. Available controls in VB.2.3.5 include:

• Statistics Overview
• Call Trends
• Time of Day
• Daily Calls by Month
• Active Incidents
• Current Month Heat Map
• Year to Date Heat Map

Public incident mapping is intentionally privacy-reduced compared with authenticated operational displays. Review the public display after setup to make sure it does not expose information the department does not intend to make public.

Analytics, reports, and security history

Monthly & Yearly Reports

Use Administration → Monthly & Yearly Reports to generate printable department statistics sheets.

Analytics & Security

This section separates public analytics from security/audit records. It includes public usage summaries, top content, approximate geography, location mapping, privacy/retention settings, security events, and audit history.

Member statistics

The member-facing My Statistics page includes calls responded to by month, department rank, current-month leaderboard, all responders, personal breakdown, incident categories, and response details.

Emergency Operations Center mode

EOC Management is available to administrators and EOC Managers. It is intended for periods when the department needs a centralized view of multiple active calls, crews, apparatus, and call status.

EOC Management

Use Administration → EOC Management to manage EOC mode and active EOC calls. The EOC workspace supports crews, assignments, apparatus, and incident status management.

EOC Quick Reference

When EOC mode is active, eligible users receive an EOC Quick Reference launcher. The quick-reference page shows active calls and apparatus/crew assignments.

StationCommand Home

StationCommand can send incidents to one or more StationCommand Home installations. Each Home instance has independent webhook signing and Respond API credentials.

Add a Home instance

1. Open Administration → Integrations → Station Command Home Integrations.
2. Select Add Home Instance.
3. Give the instance a recognizable name.
4. Enter the Home webhook URL.
5. Generate or enter the webhook signing secret.
6. Generate or enter the Respond API bearer token.
7. Enable the instance and save it.
8. Copy the generated secret/token to the matching StationCommand Home installation.
9. Select Send Test Alert and confirm an HTTP success response.

Instances can be enabled, disabled, tested, rotated to new secrets/tokens, or removed independently.

Calendar, Google Groups, and Google Photos

This guide assumes the required OAuth application credentials are already installed by the StationCommand installer. Department administrators only need to configure the department-facing integration settings.

Calendar & Group Announcements

• Enable or disable the overall integration.
• Enable Calendar API and enter the Calendar ID.
• Enable Group Announcements and enter the Google Group email.
• Set the Gmail mailbox user, announcement age, and maximum announcements.
• Connect/reauthorize the department account when instructed.
• Use Refresh Google Data to test retrieval.

VB.2.3.5 uses read-only permissions for Calendar and Gmail-based Group announcements. StationCommand does not request Calendar or Gmail write access.

Google Photos Collage

When configured by the installer and permitted by the license, administrators can enable the Photos slide, connect the account, choose albums/photo collections, check authorization, and refresh photos. The collage is intended for internal displays.

Roles and access

Rank and access level are separate concepts. Rank affects operational behavior such as officer incident controls, while access level determines administrative permissions.

In VB.2.3.5, Chief, Deputy Chief, and Captain ranks are treated as command/officer ranks for active-incident controls.

System Status

Use Administration → System Status to check application health, database state, integration health, active incident count, and configured station displays. This should be one of the first places checked when a normally working feature suddenly stops updating.

Danger Zone

The Danger Zone contains destructive administrative actions. In VB.2.3.5, Purge All Incidents permanently removes incident data and requires an active administrator session plus typed confirmation.

Troubleshooting quick reference

Mission-Ready checklist

Department identity

• Correct department name is displayed.
• Department logo renders correctly.
• Current StationCommand license validates successfully.
• Expected plan entitlements are enabled.

Stations & displays

• Every physical station is configured.
• Every station address and map point is correct.
• Every station display opens on its intended hardware.
• Display scaling is readable from normal viewing distance.

Personnel

• Personnel names and ranks are correct.
• Personnel numbers are entered where used.
• Accounts are linked to the correct people.
• Access levels are correct.
• Active911 devices map to the correct people/apparatus.
• Participation/statistics inclusion is correct.

Active911

• API is enabled and refresh token is configured.
• Force Active911 Pull succeeds.
• Webhook is enabled with a generated secret.
• Active911 “Other” URL is configured.
• A real dispatch-fed alert increments Received.
• The alert is successfully Processed (Live).
• Incident information displays correctly.
• Responder information updates correctly.

Operational testing

• Active call takes over the station display as expected.
• Multiple active incidents behave as expected.
• Officer +30 minute control is tested.
• Officer Clear Incident control is tested.
• Incident appears correctly in Incident Records.
• Reclassification/reactivation workflow is tested.
• Address Notes are tested, if used.

Weather and content

• Weather location is correct.
• NWS forecast and alerts load.
• Radar loads correctly.
• Announcements display correctly.
• Calendar/Group/Photos integrations work if enabled.
• Public display screens are reviewed and approved.

EOC / Home

• EOC mode and Quick Reference are tested if the department will use them.
• StationCommand Home test alert succeeds for every configured Home instance.

Final verification

• System Status shows healthy application/integrations.
• Administrators know how to access this guide and the Active911 guide.
• At least one administrator and one officer have completed a test workflow.