Two PIN kinds
Unit PINs are bound to a single resource (one truck, one badge). Supervisor PINs are scoped, optionally filtered to one agency or one resource type.
Mobile companion · ships inside ctHelixCAD™
A mobile companion that doesn’t need accounts.
Field units shouldn’t fight a login screen. ctHelixCAD™ ships with a built-in mobile surface (/m) that runs in any phone browser — no app store, no installs, no usernames to maintain.
/m is the early surface of ctHelixMobile™ — the broader field-mobile platform in development across the suite.
For units
A single status board, in their pocket.
- Log in with call sign and a PIN issued at the start of shift.
- Self-set status from the field — available, en route, on scene, out of service.
- See the incident you’re assigned to, with destination and notes.
- Add notes that flow back to dispatch in real time.
- Sessions auto-extend while you’re busy, age out when you’re not.
For supervisors
Read-only board, scoped to their span of control.
- Scoped, read-only board of the operation.
- Filter by agency or resource type.
- One tap, no clutter — designed for a phone in a pocket between radio calls.
- PIN issued and rotated by dispatch in seconds, not days.
How the PIN model works
A small, well-scoped auth surface.
PINs are designed for shift work — short-lived, easy to rotate, and isolated from the dispatcher console’s identity model.
Issued by dispatch
Cleartext is shown once at issue or rotate — then never again. Dispatch can rotate any PIN at any time without ending the shift.
Argon2 at rest
PINs are hashed with Argon2 in the database. The cleartext exists only in the moment of issuance.
Separate auth surface
Mobile sessions live in short-lived tokens — they never share the dispatcher console’s auth surface. A compromised PIN never grants console access.
Sliding expiry
24-hour base expiry with sliding extension while the unit is active. Idle sessions age out on their own.
Why no accounts
Accounts assume continuity. Field shifts don’t.
A roster of 40 officers for a one-day event shouldn’t require 40 emails, 40 password resets, and 40 onboarding flows. PINs match the way real shift work actually runs — issued at briefing, rotated when needed, retired at end of detail.
The dispatcher console keeps a real identity model for staff who need it. The mobile surface stays as light as the work it supports.
Want to see the mobile flow live?
We’ll spin up a unit PIN and a supervisor PIN, hand you a phone, and let you drive.