> 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.8-21st-september-2026.md). # v3.4.8 - 21st September 2026 ### Pressac Indoor Air Quality Sensor Support **Who this is for:** Facilities Managers, Admins UMA Vision now supports the Pressac Indoor Air Quality sensor, giving you comprehensive air quality monitoring from a single device — temperature, humidity, CO₂, total volatile organic compounds (TVOC), and particulate matter (PM1, PM2.5, PM4, and PM10). #### Why it matters * **All-in-one air quality** — one sensor delivers temperature, humidity, CO₂, TVOC and four particulate matter readings, reducing the number of devices needed per space * **TVOC as a distinct metric** — TVOC is tracked in its own unit (µg/m³) with dedicated thresholds, clearly separated from the existing VOC Index used by other sensors * **Slots into your existing setup** — commission it like any other Pressac sensor, assign it to a resource, and readings flow through to device pages, insights, and historic data exports *** ### Neighbourhood Filter in Analytics Pro **Who this is for:** Admins, Workplace Managers (Analytics Pro) A new Neighbourhood filter on Analytics Pro dashboards lets you scope any chart or table to one or more Neighbourhoods — sitting alongside the existing building, floor, and resource type filters. #### Why it matters * **Drill into team-level data** — filter the Space Usage & Trends dashboard by Neighbourhood to see how a specific team or department uses its allocated spaces, without noise from the rest of the building * **Works across the platform** — the filter appears on the main Space Usage dashboard, Custom Dashboards, and AI Reports, so your Neighbourhood-scoped analysis carries through wherever you work * **Neighbourhood utilisation chart improvements** — the Utilisation by Neighbourhood chart now respects building and floor filters, and is available in AI Reporting and Custom Dashboards for the first time *** ### Refreshed, More Compact Interface **Who this is for:** All users The UMA Vision interface has been refined to render more compactly at 100% browser zoom. If you've been running your browser at 80–90% zoom to make the app feel tighter, you should no longer need to. #### Why it matters * **More content, less scrolling** — tighter spacing across tables, forms, sidebars, and toolbars means you see more data on screen without shrinking your browser * **Consistent density** — inputs, buttons, and data grids all follow the same compact sizing, replacing the previous mix of default and manually overridden sizes * **Nothing changes functionally** — this is a visual refinement only. All features, workflows, and data are exactly as before, just with less whitespace * **Works in light and dark mode** — both themes benefit from the updated spacing *** ### Bug Fixes * **Room no longer declines when a buffered booking is extended or moved** — On Microsoft 365 tenants, extending or moving a room booking that included buffer times caused the room mailbox to decline the updated meeting request, effectively unbooking the room. Buffer events are now repositioned atomically so no temporary overlap triggers a decline from Exchange. * **Buffered room group bookings now handle drag and drop correctly** — Dragging a room group booking with buffer times in Calendar View could sever the moved room from its group or detach the setup and teardown buffer events, leaving orphaned entries blocking the room. Drag and drop now moves the entire booking — all grouped rooms and all buffer events — as a single unit. * **Deleting a buffered room group booking now removes all buffer events** — Deleting a booking with both buffer times and room groups removed the core booking but left orphaned setup and teardown events blocking the room. All associated events are now removed atomically. * **Buffer time events now clear "Pending Approval" after approval** — When a buffered booking requiring approval was approved, the setup and teardown events in Outlook retained the "Pending Approval" prefix in their subject lines. All events — main meeting, setup, and teardown — now update consistently when a booking is approved. * **Editing the time of a buffered booking no longer fails** — Changing the start or end time of a booking with buffer times could return a "Booking failed" error, particularly for bookings on future dates. Time edits now save correctly regardless of date. * **Services now save correctly when creating or updating bookings** — Services selected during booking creation could fail to save — showing a "Booking failed" error while the booking itself was created without the services attached. This affected bookings with buffer times and UMA Calendar-integrated tenants. Services are now persisted reliably in all booking flows. * **Removing services from a pending booking now cancels the service request** — Removing all service items from a booking in Pending Approval status left the associated service request active. The service request is now cancelled automatically, consistent with the behaviour for approved bookings. * **AI Explanation now analyses the active tab** — The AI Explanation feature on the Space Usage dashboard was always analysing the daily trend chart regardless of which tab (Hourly, Daily, Weekly, or Monthly) was selected. Explanations now target the data from the active tab. * **Resources page pagination fixed** — The Manage > Resources list was showing duplicate entries across pages, with the last page inaccessible. Pagination now returns unique records across all pages. * **Pressac Room Conditions Sensor can now be assigned to zones** — Adding a Pressac Room Conditions Sensor and assigning it to a zone resource type failed with an error preventing the device from being saved. Zone assignment now works correctly. --- # 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 by asking a question. Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters: ``` GET https://support.meetuma.ai/uma-knowledgebase/release-notes/web/2026/v3.4.8-21st-september-2026.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case. 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.