Responders Roster
The Responders view on the Units page is where shifts are started, and the control room's live read of the response pool: one row per responder showing which unit they are crewed on, whether they are on duty, and — for operators allowed to issue responder app codes — a generator for the 4-digit code responders use to sign in to the CleverResponder mobile app.
A unit has no on/off switch. It comes on duty with its first crew member and goes off duty when the last one leaves. So putting somebody on a unit — here, or on the Manage board — is what starts that unit's shift.
Opening the roster
- Click Units in the left sidebar.
- Switch to the Responders view (the fourth mode button, next to Map / Manage / Plan).
What the roster shows
The header counts the pool at a glance — On duty, Off duty, and Not crewed — and a search box filters by name, login ID, or unit. Each row displays:
- Responder -- the responder's name with their login ID underneath.
- Unit -- a picker holding the unit they are currently crewed on (with a driver marker for the unit's assigned driver), or Not crewed. Choosing a unit puts them on it; choosing Not crewed takes them off. Units already on duty are listed first; the ones below are marked off duty, and picking one of those starts its shift.
- Duty -- a pill derived from their unit's shift:
- On duty -- crewed on a unit whose shift is running.
- Off duty -- crewed on a unit that is not on shift.
- Not crewed -- in the pool but not assigned to any unit.
- App login code -- Get code generates a 4-digit CleverResponder sign-in code (valid 15 minutes, with a live countdown and a copy button); New code replaces a live one. This is the same code mechanism as Responder app codes under More → Team and the per-card button on the Manage board — issued from wherever the operator already is.
The roster refreshes automatically every 30 seconds while the tab is visible, so duty states follow shift starts and stops without a manual reload.
Putting a responder on a unit
Choose a unit in that responder's Unit picker. One move does everything: they leave whatever unit they were on, they join the new one, and the units on both ends of the move update their duty state — the unit they joined comes on duty if it was not already, and the one they left goes off duty if they were its last crew member. A responder can only be on one unit at a time, so moving somebody across is a single pick, not an unassign followed by an assign.
Choosing Not crewed clocks them off. If they were the last member of their unit, that unit's shift ends and its shift_end is stamped.
The message that follows reports what the board actually says afterwards, not what was asked for — so if a change is refused it is reported as refused, not as done.
Without the permissions
Crewing units needs supervisor permission. Without it the Unit column is read-only — the picker is replaced by plain text, and hovering it explains that a supervisor has to put the responder on.
Issuing codes needs the Issue responder app codes permission. Supervisors always have it; a Controller has it when that capability is switched on for them in CleverOps (Control Room → the operator's Role dropdown). The column is shown to everyone so operators can see that the capability exists. Without the permission the Get code button carries a padlock and is disabled, and the code itself is never displayed — the cell reads No permission instead. Hovering the button, the cell, or the column heading explains that a supervisor has to issue the code, and the note above the table says the same. Ask a supervisor to issue the code from here, from the Manage board card, or from More → Team.
Where responders are managed
Crewing happens here and on the Manage board, but responders themselves are added, renamed, and given profiles in CleverOps under Response → Responders. If the roster is empty, add responders in CleverOps first.