The new Spaces section in Insights is where you stop guessing and start seeing exactly how every desk and room in your building is used. Floor and building reports tell you a floor is quiet; Spaces tells you which areas, desks, or rooms are behind that number, so you can act with confidence instead of averages. It's split into two pages, Desks and Meeting Rooms, each tuned to the questions that matter for that kind of space. It's the quickest way to turn raw usage data into a decision you can stand behind.
What you'll find in Spaces
Spaces lives in Insights and is made up of two pages. Both lay out every space in a building with booking and sensor use side by side, so you can see at a glance how what people reserve compares to what sensors actually pick up. The two pages share the same toolkit: summary cards, a filter status row, sortable columns, column toggles, and CSV export. But they group and measure spaces in different ways, because desks and rooms work differently, and it's worth knowing how before you dive in.
The Desks page
The Desks page lays out every desk in the building, grouped floors → areas → desks, with each row showing name, location, seat count, booking policy, booking use, and sensor use, so you can move from "this floor is quiet" to "these two areas are barely touched while the rest is overbooked" in a few clicks.
The Meeting Rooms page
The Meeting Rooms page works the same way but groups its table floors → rooms, since rooms don't sit inside areas, with each row showing room name, location, seat count, booking policy, booking use, and sensor use, so you can quickly see the real story behind a building average, such as a few rooms that are always full while others sit empty.
How Desks and Meeting Rooms differ
The two pages look alike, but a few differences are worth knowing before you read the numbers:
Table layout. Desks are grouped floors → areas → desks. Rooms are grouped floors → rooms, with no area layer.
How rates are averaged. Desk rates are capacity-weighted, so bigger areas carry more weight. Room rates use a simple average, so every room counts the same.
What the filters cover. Both pages share the same core filters, but the Desks filter adds amenities and activity types, while the Meeting Rooms filter adds activities and equipment. See Filtering the Spaces tables below for the full list.
Where to go deeper on rooms. Since room rates aren't capacity-weighted, use the Meeting Room Seat Utilization deep dive report when you need seat-level detail.
Working with the Spaces tables
This is where Spaces really earns its place: both tables are built so you can get to the exact subset you care about without ever opening a spreadsheet. A global search filters rows by name across every level of the table. Every numeric column can be sorted, with options for default floor order, highest on top, or lowest on top, and rows with no data always sit at the bottom. You can show or hide each column, and that choice is saved in the link you share.
When a filter removes rows, the parent rows recalculate from the spaces that remain. So the totals always match what you're looking at, not the full building. A Reset filters button clears everything, including the search field, in one click. When you find something worth sharing, the share button creates a link that opens the same filtered view for whoever gets it.
Filtering the Spaces tables
Filters are where a long table turns into a precise answer. Want to know which bookable rooms with video conferencing sit below 20% sensor use? You can have it on screen in seconds, without leaving the page. Both pages share a core set of filters:
Use range — Show only spaces whose sensor use falls within a percentage band you choose.
Booking rate range — The same band, applied to booking use.
Policy — Show only spaces with the booking policies you select.
Capacity range — Filter by seat count.
The Desks filter adds amenities, such as a standing desk, locker, or monitor, and activity types set for areas. The Meeting Rooms filter adds activities and equipment, such as AV, video conferencing, or a whiteboard.
The key thing to know is how filters change the numbers. When a filter removes spaces, every parent row recalculates from the spaces that remain, not the full unfiltered set. If a capacity filter removes two of four desks in an area, that area's rate is worked out from the remaining two desks as a capacity-weighted average. The summary cards update the same way. So the rates you see always describe the filtered subset, which keeps the totals honest no matter how you narrow the view.
Behind the scenes
Multiple data sources per page — Each page runs two separate queries, one for bookings and one for sensors, then merges them, so a space still appears when only one source has data.
Counts come from configured capacity — The desk and room counts come from the seat capacity set up in Mapiq, not from live sensor readings.
Totals follow the filters — Summary cards and parent-row totals always reflect the active filters. Spaces with no data for a metric are left out of that figure.
The view lives in the URL — Filters, sort, columns, and search are all held in the URL, so a shared link opens your exact view.
Mid-period room changes are flagged — A room that was created, deleted, or had its mailbox changed mid-period shows a note explaining why its data may look odd. Rooms deleted during the period appear dimmed and can't be opened.
Area sensors fill a former gap — Areas with people count sensors but no per-desk sensors used to show no sensor data at all. They now appear with sensor use populated at area level.
The CSV export is self-documenting — The file starts with a header listing the date range, office hours, and filters, so it explains itself when shared.
💬 Need More Help?
If you'd like some extra assistance, reach out via the Messenger (question mark in the corner) and chat with our support team, or send us an email at [email protected].
We're always ready to help! 😉