Operators and Sign-In Codes
The Team page in CleverCommand shows your control-room roster and lets Supervisors hand out sign-in codes mid-shift -- the everyday "she's locked out, read her a new code" job. The roster itself is managed in CleverOps: adding an operator, renaming them, changing their role or capabilities, and removing them all happen there. The same page also has a Responder app codes section for minting CleverResponder sign-in codes for field responders.
CleverOps is the single registry for people and their login codes. CleverCommand used to carry its own Add operator button writing the same records, which produced half-configured operators that CleverOps then reported as having no CleverCommand access. That button has been removed -- create operators in CleverOps → Control Room instead.
Team is a tab of the supervisor toolbox page at /more, which has no sidebar entry — supervisors browse to the address (why). It requires the Advanced Alarm Handling module, and Controllers and Viewers cannot reach it.
What the page shows
Go to /more, then open the Team tab. You see a list of every control-room operator on your roster except other Supervisors -- those are hidden so a Supervisor cannot accidentally reset another Supervisor from inside CleverCommand.
Each row shows:
| Column | What it is |
|---|---|
| Login ID | The 6-character login code the operator uses to sign in on the desktop. Read-only. |
| Name | The operator's label (e.g. their name or shift). Read-only here -- rename in CleverOps. |
| OTP | The current 4-digit desktop one-time password. Click the refresh icon to generate a new one. |
| Mobile Code | A 4-digit code for signing in on the CleverResponder mobile app. Click the send icon to generate one -- it is valid for 15 minutes. |
| Role | The operator's role, shown as a chip. Controllers also show how many of the ten capabilities are switched on (e.g. Controller 6/10). Read-only -- change it in CleverOps. |
The list refreshes itself every 45 seconds while the tab is visible, so a second Supervisor's changes and code expiry stay current. The chip in the panel header tells you how fresh the view is.
Walkthrough
Regenerate a desktop OTP
Click the refresh button in the OTP column to rotate that operator's 4-digit code. The new code appears immediately and is what they will use on their next sign-in.
Refreshing the OTP ends the operator's open sessions. If they are working events right now, they will be returned to the sign-in screen and will need the new code to get back in.
Generate a mobile code
Click the send button in the Mobile Code column to create a fresh 4-digit code for CleverResponder login. The code is valid for 15 minutes and is shown inline so you can read it out over the phone or radio.
Add, rename, or remove an operator
All three are done in CleverOps under Control Room. Changes appear here within 45 seconds without a page reload.
Controller capabilities
A Controller starts with everyday control-room work -- opening events, dispatching, working the timeline. Anything beyond that baseline is governed by capability toggles, set in CleverOps. When a capability is off, the matching control is hidden or disabled for that operator throughout CleverCommand. Supervisors always have every capability; Viewers have none.
The Team page shows the count (6/12) so you can sanity-check an operator's setup at a glance, but the toggles themselves are set in CleverOps.
| Capability | What it unlocks when on |
|---|---|
| Provide site access | The Provide Access button on an event -- firing a site's PGM outputs (gate, door, etc.). |
| Snooze cameras | Snoozing and un-snoozing cameras from the snapshot wall. |
| Live view | The Live view button on camera snapshots and guard-tour cards. |
| Create manual event | Raising an event by hand from a site. |
| Bulk close events | The "Close related site events" prompt shown after completing an event. |
| Reorder call list | The Reorder button on an event's call list. |
| Edit call list notes | The per-contact note field on the call list. Without it, existing notes stay visible but read-only. |
| Use AI Caller | Placing Vapi or Twilio AI calls. Without it, only manual (tel:) calling is available. |
| Edit monitoring/responder notes | The operator and monitoring note fields on a site. Without it, the notes are read-only. |
| Attest customer over-limit consent | Marking "Customer authorized over-limit dispatch" in the consent modal without going through the call flow. |
| Issue responder app codes | Get code / New code for a responder's CleverResponder sign-in code, in the Units → Responders view and on a crew card's menu on the Manage board. Without it the code is not shown and the button is locked. |
Denied actions are hidden or disabled in the interface, and every attempt is recorded in the permission audit log. A capability change takes effect the next time the operator signs in.
What Supervisors cannot do from here
- Add, rename, or remove an operator. Do this in CleverOps → Control Room.
- Change a role or its capabilities. Also CleverOps → Control Room. The role is displayed here, never edited.
- View, edit, or reset another Supervisor. Other Supervisor rows are hidden by design.
- Add or manage responders and technicians. The Team page can issue responder app codes, but the responder and technician rosters themselves (adding, renaming, crewing, permissions) live in CleverOps. See Issuing Responder App Codes.
- Change a control room's name, billing, or response areas. Those settings are in CleverOps.
Related
- CleverOps -- Roles and Permissions -- full overview of what each role and permission grants.
- CleverOps -- Operator Management -- adding, renaming, and removing control-room operators.