The Sensors table is your overview of every sensor connected to a building. Whether a sensor comes from a known occupancy integration such as Elsys or PointGrab, or reaches Mapiq through the Public API or a custom integration, it shows up here. From this one page you can check what each sensor reports, see where it sits in your building, and jump to the tools that keep your sensor network healthy.

Open the Buildings tab, select a building, and click Manage on the Sensors tile of the building overview. The breadcrumb at the top lets you switch to another building or another building service without going back.

Three cards above the table give you the state of the building's sensors at a glance:

When an integration posts sensors to your environment that are not linked to a building yet, a banner tells you how many there are. Read New sensors waiting for a building below for what to do with them.

Every row is one sensor ID. The columns tell you what it is, where it is, and how actively it reports.

Search by sensor ID or location in the search field above the table. Open Filters to narrow the list by Location type or Floor, or turn on No sensor data received to see only the sensors that have gone quiet. At the bottom of the table you choose how many rows to show per page, from 10 to 200, and move between pages.

A sensor gets flagged when a building publish removes the location it was linked to. The sensor stays in the table, but it is decommissioned and no longer counts towards that space. This often happens while editing a floor, when desks are deleted and drawn again instead of moved, or when a meeting room is deleted. Check the Flag column after a publish, and link flagged sensors to their new location. The Impact tab in Review & publish tells you before you publish whether the change affects any sensors.

Click any row to open the sensor's details on the right:

The buttons in the top right take you to the other sensor tools:

Not every sensor arrives the same way, and not every row is a single device by default.

Depending on the active integration, sensors are imported for you (as with PointGrab), or wait for you to import them manually (e.g. Elsys or third party integrations).

Depending on the integration, sensors can start posting data to your environment before they belong to any building. Mapiq knows these sensors exist, but not where they are. When that happens, the Sensors page shows a banner with the number of new sensors. The sensor list link in the banner downloads a CSV file with all their unique sensor IDs. Use it to find the right sensors, then import and link them to the correct building yourself. The CSV is the same in every building, because the sensors don't belong to any building yet.

Depending on the type of sensor, the integration can send one combined ID for a space that holds several sensors. For example, when devices A and B both sit in space C, the integration combines their readings into one occupancy value and sends it under a single ID. You then see one row for space C, not two.

Areas, meeting rooms, and facilities can hold as many sensors as you need. A desk holds exactly one. When you link a sensor to a location that already has one, Mapiq asks whether to keep, decommission, or remove the existing sensor. In case multiple sensors are linked to a single space, the occupancy within the app is based on the combined readings of the sensors.

Every sensor has its own ID, and that ID can only be used once across your whole subscription, not just within one building. If you move a sensor from building A to building B, remove it from building A first. Only then can you link it to a location in building B.