> 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.6-20th-august-2026.md).

# v3.4.6 - 20th August 2026

### Neighbourhoods Can Now Span Multiple Buildings and Floors

**Who this is for:** Admins, Workplace Managers

Neighbourhoods are no longer limited to a single building and floor. You can now create a Neighbourhood that includes resources from across multiple buildings and floors — making Neighbourhoods a true organisation-wide grouping for departments, teams, or functions.

#### Why it matters

* **Accurate departmental reporting** — if your Sales team sits across three buildings, you can now create a single "Sales" Neighbourhood containing all their desks, and the Utilisation by Neighbourhood chart in Analytics Pro reflects the full picture
* **Simple to set up** — when creating or editing a Neighbourhood, select resources from any building and floor in your organisation. Existing single-floor Neighbourhoods continue to work unchanged
* **Floor map works as expected** — when viewing a floor map filtered by Neighbourhood, you see the resources belonging to that Neighbourhood on the floor you're currently viewing. The map experience is unchanged; the grouping is simply no longer constrained to one floor

***

### Bug Fixes

* **Bookings with buffer times now appear correctly on My Bookings** — Adding buffer times to an existing meeting could cause it to disappear from the My Bookings list until the date filter was set to the meeting's own date. Buffered meetings now display reliably regardless of the selected date filter.
* **Buffer times can now be added when editing from My Bookings** — Selecting a buffer time preset when editing a room booking from the My Bookings page had no effect — the selection was captured but not saved. Buffer times are now applied correctly from both My Bookings and the Calendar view.
* **Buffer time teardown block no longer flickers on drag and drop** — When dragging a buffered booking on the Calendar view, the teardown block briefly disappeared before reappearing. The buffer blocks now remain visible throughout the drag.
* **Kontakt.io asset tracking now shows all assets on the floor map** — Floors with more than 20 tracked Kontakt devices were only displaying the first 20 asset markers, with the remainder silently missing. All tracked assets now appear regardless of how many are on the floor.
* **Kontakt.io device type support expanded** — Several Kontakt tag models (including Bracelet Tag, Lanyard Tag, Sticker Tag, Card Beacon, and others) were not appearing on floor maps despite reporting positions correctly. Support has been extended to cover all current Kontakt trackable tag and wearable models.
* **Building Admins can now book rooms via the Booking Panel** — Building Admin users received a "Booking Failed" error when attempting to book a room using the "Use Your Account" option on the Booking Panel application. This role-based access issue has been resolved.
* **Building Admin team management fixed** — Building Admins were intermittently unable to add team members to teams. Additionally, creating a team without setting a manager showed a success message but silently failed. Both issues have been resolved with proper validation and error handling.
* **Check-in confirmation no longer reappears after page refresh** — After checking in to a desk via the reminder email link, refreshing the page caused the check-in confirmation dialog to reappear. The system now redirects after a successful check-in, preventing the dialog from being retriggered.


---

# 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.6-20th-august-2026.md?ask=<question>&goal=<endgoal>
```

`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.