Release Guide

What's New in B.3.4.23

Major department-facing changes since the previous B.3.4.23 Help Center.

Documentation baseline

This Help Center was previously verified against B.3.4.23. The current documentation is now aligned to B.3.4.23.

Installer-managed items remain out of scope. Server deployment, database deployment, OAuth client creation, SSO provider setup, and Railway infrastructure are still handled by the StationCommand operator rather than department-facing documentation.

Credentials & Certification Verification

B.3.4 adds a complete responder credential-verification system tied to Personnel.

Public verificationHuman-readable IDs such as FF45/MFR45, public /verify/<ID> pages, credential photos, affiliation status, issuer proof links, and optional public evidence.

Physical badge QR codesMultiple managed badge codes per person, independent revocation/reactivation, permanent deletion, immutable printed QR paths, and scan analytics.

Member self-serviceMembers can submit certifications, evidence, renewals, pending updates, badge requests where permitted, and reminder preferences.

Approval workflowAdmins/Training Admins review new submissions and pending changes while the previously verified record stays public until approved.

Certification categories & Michigan EMS

B.3.4.21–B.3.4.23 add category labels and optional Michigan EMS expiration synchronization.

Built-in categories: EMS, Fire, Emergency Management, Other; custom categories are supported.
Full Administrators decide which categories are Michigan EMS sync capable. EMS defaults on; other categories default off.
Michigan EMS uses the certification's existing Issuer Verification Link, not a second URL.
The approved URL format is https://www.mi-emsis.org/lms/public/portal#/lookup/user/detail/<id>.
Credential managers can use Check Michigan EMS Now; failed/ambiguous reads never overwrite the stored expiration date.
Members, Administrators, and Training Admins can control certification presentation order with Move Up/Move Down where permitted.

Email & Notifications

Email now has a dedicated Administration page with reminder policy, approval workflow, SMTP diagnostics, and branded StationCommand email templates.

Training Admin permission and reviewer notifications.
Personal member reminders with milestone preferences.
Approval-request emails for member submissions.
Immediate member approval/denial emails.
SMTP connection test and Advanced Email Delivery Diagnostic.
Recipient previews for reviewers, department summaries, and personal warnings.

Personnel & Apparatus changes

People and login authorization are unified into Personnel; login email is optional.
StationCommand can email invitations and resend them.
Custom rank hierarchy supports names, abbreviations, public titles, drag order, and tied hierarchy levels.
Added Member, Probationary Firefighter, and Probationary MFR ranks.
Members can be deactivated without deleting historical incident/certification data or badge QRs.
Active911 devices are assigned directly on Personnel cards; Apparatus has its own Administration page and also supports multiple devices.
Assigned devices are exclusive and disappear from other assignment pickers.

Operations, statistics & security

Department Statistics provides Month, Full Year, and Overall views with operational comparisons and current-year projection.
Department Time Zone is configurable under Department Branding.
Manual incidents can be created from Incident Records.
Incident history can match exact units, whole buildings, or selected buildings.
Member sessions default to 30 days; admins can configure maximum lifetime, inactivity timeout, and recent-auth protection.
Users can Sign Out of All Sessions; admins can revoke another account's sessions.
Public incident location generalization recognizes more CAD address formats while continuing to withhold exact incident location/details.

Mapping updates since B.3.4.23

Google Street View now defaults to the lower-cost Static image mode; Dynamic Panorama remains available.
Street View diagnostics distinguish local ZERO_RESULTS coverage from API/key/referrer problems.
Normal response maps keep diagnostic labels hidden unless explicitly enabled.
CAD agencies now have a Nearby GPS tolerance (default 10 miles, 0–50 configurable) for neighboring-jurisdiction incidents while still rejecting wrong-state or far-away points.