> For the complete documentation index, see [llms.txt](https://support.meetuma.ai/uma-knowledgebase/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://support.meetuma.ai/uma-knowledgebase/release-notes/web/2026/v3.4.1-25th-june-2026.md). # v3.4.1 - 25th June 2026 ### Neighbourhood and Team Columns in Analytics Pro Data Table **Who this is for:** Analytics Pro Users, Workplace Managers The reservations data table in Space Usage & Trends now includes **Neighbourhood Name** and **Team Name** columns alongside each booking row — making it easier to analyse booking patterns by location zone and team without needing to cross-reference separate reports. #### Why it matters * Filter and sort booking data by neighbourhood to understand how different zones are being used across your floors * See which teams are driving demand for specific resource types or locations * Export the enriched data to CSV for reporting and capacity planning with full neighbourhood and team context included *** ### Improved Daily Usage Heatmap Layout **Who this is for:** Analytics Pro Users The Daily Usage Heatmap pivot table has been restructured for easier reading. Month names now appear as a left-side grouping column rather than spanning across the top as wide column headers — making the table narrower and easier to scan vertically. #### Why it matters * All resources for a given date are visible in a single row without horizontal scrolling * Month context is always visible on the left as you scroll through the data * The cleaner layout makes it quicker to spot usage patterns across days and resources *** ### Bug Fixes * **Vendor cancellation email times corrected during DST** — When an admin cancelled a service task, the vendor notification email showed the cancellation time one hour behind the actual time during Daylight Saving Time. Cancellation times now correctly reflect the tenant's local timezone. * **Booking policies now enforced in Visitor Management** — Booking resources through Visitor Management was bypassing booking policies such as advance booking thresholds, assigned desk restrictions, and neighbourhood access rules. All booking policies are now consistently enforced across every booking entry point, including Visitor Management. * **Duplicate resource types removed from Visitor Management filters** — Searching or filtering by resource type within Visitor Management was showing each type twice. Resource types now appear exactly once, consistent with the rest of the platform. * **All-day room booking utilisation now capped correctly** — Analytics Pro was displaying inflated utilisation for all-day room bookings (e.g. 184% instead of 100%) because all-day bookings were not being capped to working hours. Utilisation is now correctly calculated against configured working hours for all resource types. * **Building-specific working hours used in Analytics Pro** — Utilisation calculations were using company-level working hours even when filtering by a building with its own configured hours. Analytics Pro now correctly applies building-specific working hours, producing accurate utilisation figures for each location. * **AI explanations and reports improved** — AI-generated chart explanations and report summaries now distinguish correctly between sensor and calendar utilisation, avoid recommending unsupported features, and handle weekend data appropriately — producing clearer, more accurate insights. * **Proxy bookings with services no longer trigger spurious room approval** — Making a booking on behalf of another user with service items requiring approval was incorrectly raising a room resource approval request even when no resource approver was configured. Only the service request is now raised as expected. * **Vehicle details and meeting visibility persist on parking space edits** — Editing a parking space booking was silently discarding changes to vehicle information and meeting visibility settings. These fields now save correctly. * **Sensor utilisation restored on Space Utilisation dashboard** — Following a previous release, the sensor utilisation series on the Space Utilisation dashboard stopped showing data for occupancy and PIR sensors. Calendar-based utilisation was unaffected. Sensor data now displays correctly once again. --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter: ``` GET https://support.meetuma.ai/uma-knowledgebase/release-notes/web/2026/v3.4.1-25th-june-2026.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.