Skip to main content

Partitioned Premises

Some sites are one alarm panel shared by several households -- cottages on a farm, a house and its garden flat, a small block of units. When the site has been set up that way in CleverOps (Partitions are separate premises, see Alarm zones → Partitions as separate premises), each partition is its own premises with a name, and optionally its own pin, photo, directions and keyholders.

CleverCommand then treats an event from one of those partitions as an event at that premises: the premises name leads wherever the site used to be named, and the site becomes the sub-line. Nothing changes for ordinary sites, and nothing changes for panel-wide signals on a premises site (mains power, battery, comms, tamper, test -- they name no partition), which carry on showing the site exactly as before.

In the queue​

  • Cards -- the card headline is the premises name (for example Cottage 3) instead of the site address; the site address moves down into the card's meta line, ahead of the Updated … text.
  • Table / rows -- the site column shows the premises name with the site address as muted text after it (Cottage 3 · 14 Farm Rd).
  • Search -- the search bar matches premises names as well as site names, event types and titles, so typing a household's name finds only that household's events on a shared panel.
  • Active Events Map -- the marker title reads Cottage 3 · Farm name and the marker sits on the premises' own pin when it has one.

Vehicle and Mobile Panic headlines are unchanged -- a premises is always a fixed site.

In the event workspace​

  • Breadcrumb -- Events / Cottage 3 · 14 Farm Rd / Burglary zone 2.
  • Premises row -- the Event panel gains a Premises row directly under Event: the premises name, its address line if one was given (second gate on the left), and the panel partition number (Partition 2) when the site's partition mapping resolves it.
  • Site visual -- the premises' own photo is shown when it has one; otherwise the site photo, as before.
  • Map -- the red site pin is the premises: on the premises' own pin when it has one (the site entrance then shows as a second, grey pin so you can still send a unit there), otherwise on the site pin labelled with the premises name and the site as sub-label. The map thumbnail follows the same location.
  • Notes -- when the premises has Directions for responders, a Premises directions · Cottage 3 block appears above the site-wide Site notes.
  • View zones & partitions -- the partition this event came from is highlighted and tagged this event.

Dispatch​

When the premises has a pin of its own, it becomes the default Respond to target: override → vehicle tracker → live panic position → premises pin → site address. The Respond to picker in the dispatch panel, and the destination dropdown on the map, both offer Premises pin next to Site address, so the operator can still send a unit to the shared entrance. Distance sorting and the ETA in the dispatch note are calculated against whichever target is selected -- see Dispatch Management.

Call list and customer messages​

The Call List narrows to the premises' own keyholders: people scoped to that premises in CleverOps plus the site's Whole site keyholders. A muted caption says which list you are looking at -- Keyholders for Cottage 3 · 2 of 5 site keyholders -- and a Show whole site button in the panel header lifts the filter for this event. If nobody is scoped to the premises the whole site is shown and the caption says so. The filter resets when you open another event.

The same rule decides who is messaged: the kanban Call customer picker and Send customer message flyout use the premises' keyholders, and the automatic customer notifications (app push and WhatsApp first contact) go to the same people, with the premises named in the text (Cottage 3 (Farm name)). Two things deliberately keep the whole site: Client phoned in (a caller may be any keyholder on the panel) and the group Call site app ring, which is resolved server-side for the whole site.