Modules & Capabilities
The Modules & capabilities board is what you see on Settings → General (the first entry in the Operations group of the Settings navigation, with a control room selected). It answers one question in one place: what can this control room actually do?
Settings uses a grouped navigation on the left (on narrow screens it becomes a horizontal scrollable list): Workspace (Profile, Branding, Contact details, CleverCam subscription), Operations (General, Dispatch, Telephony, Cost model), Alarm (Alarm Handling, Alarm Receivers, Deterrence), Customer messaging (Automations, Messaging, Monthly Summary, Customer experience), Sales & CRM (Quotes, Ticket templates), Reminders, and Data & audit (Site fields, Audit). A Find a setting… box at the top filters the navigation by what a setting is about — "vat", "logo", "chat id" — and Enter opens the first match. The old Config tab is gone — its cards are now the named Operations entries — but old ?tab=config links still land on General. A Modules row (Company section) appears only for super admins and jumps to Company Settings → Modules.
Everything is grouped into the six capability suburbs below. The first five are modules — each a single master switch with its own card on the board, revealing or hiding a whole suburb of the app. The sixth, AI Telephony, has no master here; it shows a single read-only status, configured in the Telephony card lower down. All five module masters are also listed under Company Settings → Modules, a tab visible only to super admins.
Everyone sees the On/Off status — the board is readable by any VCR manager, and the sidebar suburbs each module unlocks still follow these flags. But only a super admin with Super-admin mode on can change a module. Modules describe what your control room has subscribed to, so they are set by CleverCam rather than self-served: owners, company admins and supervisors see read-only On/Off badges, and the Company Settings → Modules tab is visible only to super admins.
This is enforced by the platform, not just the interface — the database rejects any change to a has_*_module flag from anyone who is not a super admin, whichever route it comes through. The same goes for a new control room: anyone else who creates one gets every module at its default, and only CleverCam can create a room with modules already on. To change your subscription, contact CleverCam support.
AI Telephony and the back-of-house flags are set elsewhere (see below).
1 · Advanced Alarm Handling
The master switch for smart alarm handling — the dispatch / response layer. Turning it on unlocks the Alarm Handling entry and the Review Queue — turning it off hides both. It also gates the other Operations entries in the Settings navigation — Dispatch (Dispatch branch & priority and Dispatch limit policy), Telephony (Telephony) and Cost model (with the module off, Operations shows only General — this capabilities board, the Control room clock and the Installation hold, which are never gated) — plus the per-site Monitoring → Alarm handling sub-tab in Site details.
On Performance & Reports it gates only the dispatch-derived parts — the Dispatch tab, the False alarms sub-tab, the Dispatches / False alarm rate columns on Sites → Overview, and the four operator / responder reports. Everything measured from dispatch records is meaningless for a control room that dispatches from other software, which is exactly what these rooms do.
What it deliberately does not gate — anything describing the site or CCU itself, which every control room needs whether or not it dispatches:
- the per-site Monitoring → Scheduling sub-tab (arm/disarm scheduling)
- the Monitoring and Arm status filters on the Sites page
- the Performance & Reports page as a whole, including camera health and the site / keyholder / open-close reports
It is a single switch: turning Advanced Alarm Handling on also arms the whole Brain runtime — it enforces the per-type Action Plans, runs Clava / Maven mode, and arms autonomous handling (the Brain may self-phone or dispatch a response unit without an operator, per each alarm type's plan). Turning it off stands the whole stack down. Because this one switch can arm autonomous action, only a super admin (in Super-admin mode) can flip it — it is not a self-service VCR toggle — and new control rooms start with it off. This lock is enforced by the platform itself, not just the interface: the database rejects any change to the master or the Brain flags from anyone who is not a super admin.
There are no per-feature sub-switches to manage: the platform keeps the underlying Brain runtime flags permanently equal to the master, so they cannot be set individually or drift apart. The only thing shown beneath the master (to a super admin in Super-admin mode) is the Brain kill switch — an independent emergency stop that a super admin can flip right there. While it is on, the Brain is fully disabled regardless of the master. It is off by default and off for every control room in normal operation.
See Action Plans for how the plans themselves are built.
2 · Allow 3rd Party Alarm Receivers
Master switch for inbound integrations with 3rd-party alarm panels (Olarm, Ajax, FSK, RDC, FinMon, SpotBot, Hyyp, Onyyx). Turning it on reveals the Settings → Alarm Receivers entry (in the Alarm group), the per-site Zone structure card (Site details → Hardware → Inventory), and the Identity & Signals tab on the Hubs page (identity conflicts / unlinked signals from those same receivers); off hides all three.
3 · Customer Relationship Manager (CRM)
The whole customer lifecycle in one switch. Turning it on reveals Sales (the leads pipeline and quotes, together), Customers, Tickets, Service Ops (jobs, scheduling, technicians, catalog, recurring maintenance) and Billing (invoices, subscriptions, payments, statements, monthly run) — the entire CRM sidebar group, as a single unit.
4 · Onboarding journeys
The Lead-to-Live acquisition journey, currently at alpha stage. Turning it on reveals the Onboarding item in the Sales switcher (sidebar → CRM → Sales, then Onboarding alongside Overview, Leads and Quotes): one board that takes a deal from enquiry to a live monitored site, with the customer-facing Getting Started link (tasks, e-sign, keyholders, debit order), automatic prospect-customer and pending-site creation, and per-VCR task packs and gates. It pairs naturally with the CRM module — journeys pick up where the Leads board leaves off — though it has its own independent switch.
Like every module master, it is switched on by CleverCam (a super admin) rather than self-served. See Onboarding for the full walkthrough: the board, the per-company settings (task pack, gates, SLAs), and the customer's Getting Started link.
5 · Multiple billing entities
At alpha stage and off by default. This is the opt-in for control rooms whose company operates as more than one legal entity — for example an armed-response company and a separate technical/installations company, each with its own VAT registration, CIPC number and letterhead — while everything still runs in one control room with one customer list and one customer portal.
Every control room already carries a default billing entity behind the scenes (mirroring its Branding identity), and every invoice, quote and payment records which entity issued it — so switching the module on adds entities alongside that one rather than changing anything that exists. With it on you get a Billing entities section under Settings, per-entity letterheads, VAT registration and invoice numbering, an entity scope switcher across the Billing page, and a separate accounting connection (its own Xero organisation, for instance) per entity. See Billing entities for the full walkthrough.
Two platform rules apply, enforced by the database: the module requires the CRM module (billing itself lives inside CRM, so the switch is refused without it), and like every module master it is set by CleverCam (a super admin) rather than self-served.
6 · AI Telephony
AI Telephony is not a module master — it shows a single read-only status: whether AI-placed calls (conversational or pre-recorded) are live for this control room. It reads On when AI calling is enabled, not suppressed to manual-only, and at least one provider (Vapi or Twilio AI) is active.
The actual calling methods — providers, caller-ID, provisioning and pricing — are edited on the richer Telephony card below, or set by CleverCam.
Keeping Telephony's only editor on its own card avoids two switches writing the same setting out of sync. The underlying flags are back-of-house and not self-service.
Three modules that are not on this board
Roster, Asset register & inspections and Site Layout are modules like the rest, but they are switched on the company's own module panel rather than here, so the board above does not list them.
| Module | What it opens |
|---|---|
| Roster | The Roster entry under Operate — shift patterns, per-site guarding requirements with PSIRA-grade and MCA-hours warnings, the day-of board, check calls and tiered shift offers. It also puts the Postings board in CleverCommand. |
| Asset register & inspections | Equipment → Assets — your own asset categories with custom fields and inspection checklists, QR tags, and scored inspections that schedule the next one. Vehicles, Firearms and Trackers keep their own registers and are unaffected. |
| Site Layout (alpha) | Sites → Hardware → Layout — pin every camera, zone and marker at its real coordinates with a mounting height, aim and field of view, on satellite imagery you can pan and zoom, with a default framing saved per site. Floorplans (images or PDF pages) and drone photos can be added as extra views beside the map. Map pins are placed by technicians in CleverTech too, and CleverCommand reads the layout as a mimic board during an alarm. |
All three are switched by a super admin on Company Settings → Modules, the same place every other module master is flipped. See Roster, Assets and Site Layout.
App panic
Below the capability suburbs, the App panic card sets what app users on your connected sites may send from their phones. It has its own page — App panic — because there is more to it than a single switch.
In short:
- Offer location panic (My Location Panic) is this control room's opt-in to the location-panic lane. While it is off, nobody can send you a location panic, not even a person granted “Site + location” on a site's People tab. It is per control room on purpose: on a site several control rooms share, one company's grant never turns another company into a location-panic destination.
- The default below it — Site panic only (the default), Site + location panic, or No app panic — applies to every app user on your sites, with per-person exceptions on each site's People tab (Edit → App panic). Under the choices, a summary line counts the app users on your sites, how many currently have location panic, and how many carry a per-person override.
- Nothing is approved any more. Photos, medical alerts, vehicle details and emergency contacts are self-service: people fill in My emergency profile in the app (staff can also edit them per site under People), and whatever exists is snapshotted into each panic for your operators and responders. The Emergency profiles register button on the card lists everyone on your sites who has one — photo, medical read-out, vehicle, contact, last updated — read-only, nothing to action. The old allow-per-connection search and the approve/reject enrolment queue are gone.
Location-only people. A person with no premises (the no fixed address option on Add personal cover, or Anywhere only in the onboarding wizard) carries Location panic only instead of Site + location panic. Their location panic works exactly the same; a premises panic from that person is refused, because their base has no address to dispatch to. Everything else here applies unchanged.
Site eligibility. A user can only enrol through a site that has a linked hub of any type — hub-less sites are not eligible. If a site has no other hub, it can carry the existing R5-per-user “Panic App” hub to unlock this (and other app-only features) without a full camera install. For a person with no premises at all, Sites → Add personal cover sets this up in one go — a base site at their home address, the Panic App hub, and the person with location panic already allowed (how it works).
Any VCR manager can change both — they are operational choices, not super-admin gated. See App panic for the interlocks between the switch and the default, the “selected people only” mode, site eligibility, and the register.
Installation hold
Below App panic, the Installation hold card sets how long a site's alarms stay on hold while it is being installed — 2 hours unless you pick another length. It has its own page: Installation hold.