> 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.5.2-4th-november-2026.md).

# v3.5.2 - 4th November 2026

### Meeting Type Colours on the Calendar

**Who this is for:** All users

Bookings on the calendar can now be colour-coded by meeting type, so you can tell a client meeting from an internal stand-up at a glance — without opening the booking.

#### Why it matters

* **Admin-assigned colours** — admins can assign a colour to any meeting type from a preset palette in Meeting Type settings. A new Colour column in the meeting-type list shows the current choice
* **Calendar views updated** — day, timeline and single-room week views all show the meeting type colour as a solid colour bar with a lighter fill, keeping text legible in both light and dark mode
* **Everyone sees it** — colours are visible to all users, not just admins
* **Works everywhere** — recurring bookings, multi-room bookings and bookings with buffer time all display the colour consistently. Changing or removing a meeting type updates the colour on the next calendar load
* **No colour option** — setting a meeting type to "No colour" returns its bookings to the default style
* **Graceful fallback** — if meeting-type data is unavailable the calendar still loads promptly with default styling, so there is never a blank screen

***

### Analytics Pro Multi-Building Selection and Date Range Limits

**Who this is for:** Admins, Workplace Managers (Analytics Pro)

Analytics Pro now lets you select multiple buildings — or all of them — in a single view, giving you a cross-estate picture without switching between buildings one at a time. To keep dashboards fast at this scale, sensible date range limits are introduced alongside.

#### Why it matters

* **Select several buildings** — the Building filter now supports multi-select and an "All buildings" option. Floor, Neighbourhood and Resource filters work across the selected buildings, with floors of the same name grouped together
* **Smart filter hierarchy** — picking a floor or neighbourhood narrows the building selection to the buildings it belongs to, and the Resource dropdown follows the same hierarchy so you always see relevant options
* **Per-building accuracy** — utilisation is measured against each building's own working hours, and Energy & Water costs use each building's own tariff and emission factor. Budget lines are hidden when multiple buildings are selected, since budgets are set per building
* **Resources disambiguated** — resources with the same name in different buildings are shown separately, e.g. "Meeting Room 1 (Halifax)"
* **Date range limits** — one building allows up to one year; multiple buildings up to six months; hourly utilisation views and the daily usage heatmap hourly breakdown up to three months with a single building. Dates past the limit are greyed out in the date picker and a clear message explains the restriction
* **Building admin scope** — building admins now see analytics only for the buildings they manage, keeping data appropriately scoped
* **Neighbourhood chart accuracy** — neighbourhood charts now show only the neighbourhoods you selected, and the AI summary of People Count Trend charts in reports uses whole numbers to match the chart

***

### Bug Fixes

* **Cancelling a meeting via Outlook or Google Calendar now cancels linked service requests** — Previously, cancelling a room booking from Outlook or Google Calendar left associated service requests and vendor tasks active in UMA Vision. The cancellation now cascades correctly, so vendors are not left with tasks for meetings that no longer exist.
* **Buffer time validated against the current time** — Creating a booking with a short lead time could allow the setup or teardown buffer to fall entirely in the past without warning. Buffer times are now validated so they cannot be scheduled before the current time.
* **Drag-and-drop booking extension respects working hours** — Dragging a booking to extend it past configured working hours was silently allowed, bypassing the validation that blocks this in other booking flows. The working-hours boundary is now enforced on drag-and-drop.
* **Video meeting URL validation tightened** — The video meeting URL field now validates that the entered URL belongs to a recognised meeting provider, preventing unexpected navigation when using the click-to-join icon.
* **Google Meet join button restored for Google Workspace companies** — The Google Meet icon was not appearing on booking rows in My Bookings for companies on Google Workspace. The icon now renders correctly and opens the Meet link.
* **Calendar print shows correct booking times** — Printing the calendar view could show booking times drifting progressively — up to fifteen minutes before noon and over an hour after. The print layout now renders times accurately.
* **Neat Bar Gen 2 and Neat Board 50 device settings can now be saved** — Saving device settings for newer Neat models (Bar Gen 2, Board 50, Pad) failed with a validation error. These models have been added to the validation schema.
* **Quick Book room availability checks the correct time** — The "Add room to meeting" tab in Quick Book was checking room availability against the start of working hours instead of the selected meeting's actual time, showing incorrect availability. It now checks against the meeting's real time window.


---

# 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.5.2-4th-november-2026.md?ask=<question>&goal=<user_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.
