> 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.3.9-4th-june-2026.md). # v3.3.9 - 4th June 2026 ### Analytics Pro - Building-Level Energy & Water Dashboard Settings **Who this is for:** Admins, Building Admins Admins can now configure and save energy and water dashboard settings — tariffs, standing charges, emission factors, and monthly budgets — per building. These settings persist across sessions and are automatically applied for all users viewing that building's dashboard, so there's no need to re-enter values on every visit. #### Why it matters * Settings are saved once and shared across all users, ensuring consistent reporting across the organisation * Each building can have its own tariff and budget values, reflecting real-world cost differences between locations * Dashboards load with the correct values already applied, saving time and reducing the risk of incorrect figures in reports *** ### Manual Service Task Cancellation **Who this is for:** Admins Admins can now manually cancel an active service task directly from the task list or detail panel — useful when plans change and a vendor delivery is no longer needed. #### Why it matters * A confirmation step prevents accidental cancellations * Each cancellation is fully auditable, recording who cancelled the task and when * The assigned vendor team is automatically notified, so they don't prepare for a delivery that's no longer required * The cancel option is only available on active tasks — it's hidden on tasks that have already been delivered or completed *** ### Bug Fixes * **Starred users now persist as favourites on My Bookings** — Favouriting a user on the My Bookings page was not being saved for companies with a sizeable amount of users, so the selection was lost when you navigated away. Starred users now persist across sessions. * **Teams meetings preserved when moving bookings between rooms** — Dragging a room booking to a different room was deleting the associated Microsoft Teams meeting from both UMA and Outlook. Moving a booking now correctly preserves the Teams meeting link. * **Service item delivery time validation fixed** — Editing the time of a booking with service items triggered a false validation error on the delivery time, even when it was within the updated meeting window. This no longer blocks valid changes. * **Booking duration no longer resets when changing the date** — When editing a booking and changing its date, the time duration was silently reset to 30 minutes. The original start and end times are now preserved. * **Capacity vs Average Occupancy chart works for zone-only customers** — The chart in Basic Analytics showed no data for customers using zones with people-count sensors but no calendar bookings. It now correctly displays occupancy data from sensor readings. * **O365 Meeting type now appears in Resource Booking Report CSV** — The Meeting Type column was always empty despite bookings having a type selected. The report now correctly includes the meeting type value. * **Booking card renders correctly with Teams calls** — Opening a booking card for a room booking with an attached Microsoft Teams call produced a broken layout. The card now displays all details 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 dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter: ``` GET https://support.meetuma.ai/uma-knowledgebase/release-notes/web/2026/v3.3.9-4th-june-2026.md?ask= ``` The question should be specific, self-contained, and written in natural language. 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.