Command overview.
Apparatus readiness and incident activity, all in one place.
Upcoming
Incident volume
Unit readiness
Incident activity
Fleet watchlist
Communications.
District messages, announcements and priority acknowledgements. Private conversations are visible to participants only.
Messages are shared securely with their intended recipients. Priority messages require each recipient to acknowledge them.
My conversations
Calendar.
Important dates, training, meetings and equipment deadlines.
Apparatus.
Track unit availability, service information, and notes.
Maintenance watchlist
Inventory.
Manage SCBA air packs, cylinders, tools, and anything else the district needs to track.
Equipment can be assigned to a station or individual apparatus. Inspection dates and history are recorded on each item's details.
Incident log.
Review response timestamps, dispatched apparatus, and activity by station.
District call numbers reset January 1 (Eastern Time). A call is counted only when a district apparatus has an en-route or on-scene time; dispatch-only records are retained without a call number. CAD incident IDs never change.
Personnel.
Member qualifications, station assignments, training totals, and certification history.
Training.
Record drill details and automatically credit each attending member.
CAD drill identifiers are retained. Officer-added attendance, time, topics, and equipment are protected from re-import overwrites. Drills never increase the annual emergency-call total.
Meetings.
Schedule and record district meetings, attendance and session hours in shared D1.
Meeting hours are recorded separately and do not count toward annual training requirements or emergency incident totals. Attendance and changes are stored in district database.
Special details.
Track event staffing and participant-hours separately from training and emergency incidents.
Analytics.
Compare year-to-date results, all-time history, and personnel training progress.
Training analytics
Calls by station
Incident categories
Dispatch to scene
Unit responses
Reports.
Build detailed district reports with configurable datasets, dates, stations, search and exports. Database backup and restore remain under Administrator.
District operations — monthly or YTD
Shared D1 totals respect your read permissions. Session-hours measure event duration; personnel-hours credit each participating firefighter separately, including individual training overrides. Station personnel-hours follow each firefighter's station assignment.
Choose report metrics (these selections can be saved)
Sign in to manage your personal report templates.
Sign in to generate this report.
Start with a report template
Report previews and exports use your authorized shared district records.
My saved report configurations
Save the checked report groups, dates, station and sorting once, then reuse those selections. Configurations are stored in D1; report previews and exports use current shared records.
Sign in to load your saved configurations.
Select records
Report filters
Matching records
Data & settings.
Back up your dashboard, import records, or start with a clean roster.
Appearance & layout
Customize how the dashboard looks for you. These preferences will be associated with your Google account when shared sign-in is connected.
Reports
Build customized reports and export selected records as CSV, HTML, or PDF. Full database backup and restore are managed under Administrator.
Import records
Restore a dashboard JSON backup, or import an incident CSV exported from this dashboard. Files are reviewed before authorized records are imported into the shared database.
Import CAD reports and archives
Import a single Columbia County closed-incident email/PDF or a collection of messages from a .mbox file. Review duplicates, responses, drills and details before saving structured records to the shared database.
Workspace mode
About data storage
Operational records are shared between authorized officers. Full database backup and recovery remain under Administrator settings.
Import and archive migration tools
Review your backup for cloud transfer
Choose the full JSON backup you just downloaded. We'll check its record counts, duplicate IDs and common compatibility issues right here on your device. This check does not upload the file, restore data or write to Cloudflare.
Your backup remains on your device during the initial check. Nothing is sent until you separately confirm a staging import below. Production databases remain untouched.
Controlled import to testing database
After reviewing your file, we'll compare every existing staging record before enabling import. Emergency calls, drills, special details, responses, apparatus information, maintenance schedules, service history and compatible personnel records are covered. Attendance credits and annual training requirements need separate cloud features; you can hold those records in your full backup and choose a clearly identified partial staging import. Inventory or certification records still block import.
Any accepted write goes only to stockport-command-staging through your Google-authorized Worker. This is a one-time migration, not ongoing cloud synchronization. Browser-only colors, layout, draft permissions and local change logs are not migrated; the original JSON backup keeps them. The original backup and browser-local records remain unchanged.
Next phase · training record compatibility
After the main import is complete, check the deferred training session, member attendance and annual-hour requirements against the staging roster. This is a read-only review of your saved JSON and district records; it cannot change either database.
One-time OSHA duplicate cleanup · staging only
The original browser backup contains Osha hours, Osha, and Osha, all set to eight hours for all classes. You confirmed that the intended rule is OSHA Annual Training · 8 hours · Interior, Exterior, Fire Police. This process retains one original source ID, archives the extra imported staging rule with an audit entry, and removes duplicate rules only from a new corrected backup. Your existing local data and original JSON file are not changed automatically.
Controlled import of deferred training records
Once the separate staging Worker has been upgraded, compare the final training items with existing cloud records. The linked session and attendance are saved together; annual rules are separately audited. No production writes are allowed.
Report previews and exports use authorized shared district records. Full cloud database backups and restores are restricted to Administrator.
Version & update history
The version shown here identifies the dashboard frontend package. Backend Worker deployments and D1 migration numbers are tracked separately.
View the latest 3 updates
- V36.9.18 Current
Added a shared district calendar, unified database-backed tabs and reports, moved advanced controls into their regular tabs, and simplified operational wording.
- V36.8
Added the D1 officer activity explorer, audit filters and exports, hourly authenticated-session observations, and server-side permission consistency checks.
- V36.7.1
Added an expandable release history to Data & Settings and clarified the shared D1 versus browser-local storage notice.
Administrator.
Verify Firebase officer access, then prepare shared storage and reliable backups.
Field Management
Manage dropdown choices and identifiers used throughout the district dashboard. Changes are shared between authorized users. Existing records and service history are preserved.
Choose a field category to manage its shared values.
Officer access & permissions
Manage linked Google sign-in accounts and per-user rights. These controls update officer permissions through the authenticated D1 API.
Loading administrator access controls…
Officer activity
Authenticated database actions, account changes, and periodically observed sign-ins. Sign-in observations are limited to one per officer per hour; they are not a complete Firebase sign-in or failed-login history. Filters and exports include only authorized audit entries.
Full D1 backup & restore
Full-system backups belong here. A complete backup must include shared records, every officer account, permissions, personal color schemes, tile selections, and all other saved user preferences from the database. Restore will require a database-wide preview and explicit confirmation.
The database backup and restore endpoints are not yet available. Browser-local backups are not a substitute for a D1 backup. No database will be changed from this panel until server-side restore safeguards are completed.
Officer accounts
Each officer can have custom access to individual functions. Starting presets are optional; explicit Allow or Deny settings override them. The Worker enforces actual permissions, but these editor controls still save local planning drafts only and do not change any officer account in staging.
Permission editor
Select a planned officer to choose exactly which actions they may take. You can also register new permission definitions in the backend as future dashboard modules are added.
Change history
This is a basic activity list from this browser only. It cannot identify or verify individual users. In production, incident, apparatus, maintenance, and permission changes will include the authenticated actor, timestamp, and before/after values in a server-side audit table.
ADVANCED ADMINISTRATION · PRIMARY ADMIN ONLYCloud services & database linkingExpand connection status
Effective deployment configuration, shown read-only. Verify the authenticated Worker and its D1 binding below. Database connections cannot be changed from browser settings, and production remains untouched.