> 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.1-15th-october-2026.md).

# v3.5.1 - 15th October 2026

### My Bookings Refresh

**Who this is for:** All users

My Bookings has been refreshed with a cleaner card layout, a new Quick Book modal for booking directly from the page, and the ability to add a room to a calendar meeting that doesn't have one yet — so you can manage your entire day from a single screen.

#### Why it matters

* **Quick Book** — tap the Quick Book action on any day to open a modal showing available resources for that day. Filter by resource type (room, desk, parking, and more), capacity, amenities, and name, then select a resource to complete the booking without leaving My Bookings
* **Add room to a meeting** — for companies on Microsoft 365 or Google Calendar, a second tab in Quick Book lists your upcoming meetings that have attendees but no room. Pick a meeting, pick an available room, and the room is added in one step
* **Join meetings in one click** — meeting provider icons (Teams, Google Meet, Zoom, Webex) on booking rows are now clickable, opening the meeting join link in a new tab
* **Refreshed booking cards** — booking rows have been re-laid out with better spacing, icon positioning, and text handling so that long resource names and subjects display cleanly at any screen size
* **Cleaner labels** — desk and parking bookings now show a friendly label ("Desk booking", "Parking booking") instead of the raw auto-generated subject
* **Renamed toggle** — the all-bookings toggle has been renamed to "Include external events" for clarity; behaviour is unchanged

***

### Hourly Utilisation and People Count Analytics

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

Two Analytics Pro dashboards now support hourly granularity, letting you see exactly when spaces are busiest during the working day — not just which days are busiest during the week.

#### Why it matters

* **Hourly utilisation heatmap** — each date row on the Daily Usage Heatmap now expands to show that date's hours, per resource, with sensor and calendar data side by side on the same colour scale. Expanding is instant — hours for the full selected range load in one request
* **Utilisation table improvements** — a new Daily/Hourly toggle, plus three new columns: Calendar Duration (minutes), Calendar Utilisation %, and Unused Booked Time (booked minutes less sensor minutes). The table is now paginated server-side and exports return every row, not just the page on screen
* **Hourly people count** — the People Count Trend chart on the Occupancy dashboard now includes an Hourly tab alongside Daily and Weekly. The Average People Count KPI card gains an hour-vs-hour comparison, and the People Count data table adds a Capacity Utilisation column (average people count as a percentage of resource capacity)
* **Exports updated** — "View underlying data" on both the KPI card and the trend chart reflects whichever granularity is selected, and shows whole-number people counts instead of decimals

***

### Booking Details on Hover in Calendar View

**Who this is for:** All users

Hovering over a booking in the Calendar day, timeline, or single-room week view now shows a small card with the booking's title, start and end time, organiser, and — if one is set — the meeting type name and colour swatch.

#### Why it matters

* **See details without clicking** — short bookings often truncate the title and organiser. The hover card shows the full information without opening the booking drawer
* **Meeting type at a glance** — if your organisation uses meeting-type colours on the calendar, the hover card also names the meeting type, so you don't have to rely on colour alone — particularly helpful for colour-blind users
* **Privacy respected** — private bookings and bookings hidden by your role show "Busy" and the time only, with no meeting type. The card never reveals more than the booking block itself
* **Stays out of the way** — the card disappears when you drag or resize a booking, and never blocks clicks on the calendar

***

### Analytics Pro Resource Display Limit Raised

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

The Top N / Bottom N chart limit in Analytics Pro has been raised from 50 to 2,000, so organisations with large estates can now see all their resources in a single chart view. CSV and JSON exports continue to return the full dataset regardless of the on-screen limit.

***

### Bug Fixes

* **Service request decline now correctly checks permissions** — Users without approval permission could open the Decline screen on a service request task and enter a reason, but submitting silently failed with no feedback. The same permission check that blocks unapproved users from approving now also blocks them from declining, with a clear message.
* **Replacing a resource image now saves correctly** — Selecting a new image to replace an existing one appeared to work during the edit session but did not persist on save — the old image remained. Directly selecting a replacement image now saves without needing to manually remove the old one first.


---

# 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.1-15th-october-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.
