> 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.9-1st-october-2026.md). # v3.4.9 - 1st October 2026 ### Key Contacts on the Floor Map **Who this is for:** Admins, Facilities Managers, All Users Admins can now assign key contacts — first aiders, fire wardens, emergency coordinators, building managers, IT support, health and safety officers, facilities staff, and security — to each building. Everyone in the organisation can then switch on a Key Contact View on the floor map to see exactly where those people are right now. #### Why it matters * **Eight built-in roles** — First Aiders, Fire Wardens, Emergency Coordinators, Building Managers, IT Support, Health and Safety, Facilities, and Security. Each role has its own colour and icon so you can identify them at a glance * **Live location pins** — when Key Contact View is on, the map shows a pin on the desk or room where each key contact is currently booked. Pins update automatically as bookings start and end, so the view always reflects who is in the building right now * **Works across resource types** — a key contact booked into a meeting room or at a desk all show up. If they hold two bookings at the same time (a desk and a room), both locations are pinned * **Multi-role support** — a person can hold more than one role (e.g. First Aider and Fire Warden). Hovering their pin shows all assigned roles. When multiple key contacts share a location, the pin shows a group badge with a count * **Per-building configuration** — key contacts are managed in Building Settings → Key Contacts. Each building has its own roster, and changes to one building don't affect another * **Simple to use** — any user can toggle Key Contact View on from the map side panel. The date picker is locked to "now" so the view always shows current locations. Switching it off returns to the normal booking view *** ### Logitech Sync Cloud Integration **Who this is for:** IT Admins, Facilities Managers UMA Vision now integrates with Logitech Sync Cloud, pulling occupancy and environmental telemetry from Logitech devices directly into your existing dashboards, reports, and live floor map insights — no additional configuration on the analytics side. #### Why it matters * **Connect once, see everywhere** — provide your Logitech Sync Cloud certificate and Org ID on the Integrations page and UMA auto-scans your connected org for devices. Assign them to UMA resources (individually or in bulk) and telemetry starts flowing into the same pipeline used by Milesight, EnOcean, and other supported sensors * **Auto-book and auto-release** — Rally Bar, Rally Bar Mini, Rally Board 65, and Spot all support automatic booking and release based on real-time occupancy, so rooms are freed up the moment they're vacated #### Supported devices | Device | Presence | People count | CO₂ | Temp | Humidity | TVOC / VOC | PM2.5 | Auto-book / release | | -------------- | -------- | ------------ | --- | ---- | -------- | ---------- | ----- | ------------------- | | Rally Bar | ✅ | ✅ | – | – | – | – | – | ✅ | | Rally Bar Mini | ✅ | ✅ | – | – | – | – | – | ✅ | | Rally Board 65 | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | | Spot | ✅ | – | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | | Rally | – | – | – | – | – | – | – | – | | Sight | – | – | – | – | – | – | – | – | | Tap | – | – | – | – | – | – | – | – | | Tap IP | – | – | – | – | – | – | – | – | | Tap Scheduler | – | – | – | – | – | – | – | – | | Logi Dock Flex | – | – | – | – | – | – | – | – | | Brio 505 | – | – | – | – | – | – | – | – | Rally Bar and Rally Bar Mini provide occupancy data (presence and people count). Rally Board 65 and Spot add a full environmental suite — CO₂, temperature, humidity, TVOC, and PM2.5 — giving you room-level air quality alongside occupancy in a single device. Devices without telemetry columns are discovered and visible in your device list but do not currently report data to UMA. *** ### Reservations by Meeting Type Chart **Who this is for:** Admins, Workplace Managers (Analytics Pro) A new "Reservations by Meeting Type" chart on the Analytics Pro dashboard visualises how your room bookings break down by meeting type, and a Meeting Type column has been added to the Calendar Events table. #### Why it matters * **See booking patterns by purpose** — understand whether your rooms are used primarily for client meetings, internal syncs, interviews, or other types, and how that mix changes over time * **Drill into the data** — the new Meeting Type column in the Calendar Events table lets you filter, sort, and export reservations by meeting type for deeper analysis *** ### Bug Fixes * **Floor map hover panels no longer flicker during background data refreshes** — Hovering a marker on the floor map (key contacts, searched users, or your own booking avatar) could cause the hover panel to briefly disappear and not return until you moved your cursor away and back. This happened because every background data change rebuilt all markers from scratch. Markers are now diffed and only updated when their content actually changes, so hover panels stay visible as long as your cursor remains over them. * **Meeting type no longer cleared when adding buffer times** — Editing an existing room booking to add or change a buffer time preset silently removed the previously selected meeting type. The meeting type is now preserved through buffer time edits. * **Neighbourhood restrictions now shown before drag-and-drop confirmation** — Dragging a booking onto a neighbourhood-restricted resource in Calendar View previously showed the confirmation modal as normal, then returned a generic "Booking failed" error after confirming. The restriction is now surfaced before the modal appears, matching the existing Floor Map behaviour, so you know immediately why the move isn't allowed. * **Descriptive error when dragging a buffered booking to a slot that's too short** — Dragging a buffered booking to a time slot shorter than the full buffer window (setup + meeting + teardown) returned a generic "Booking failed" message with no explanation. A clear validation message now explains that the target slot cannot accommodate the buffer time window. * **Drag and drop of buffered bookings no longer creates duplicate entries** — Dragging a buffered room booking to a different resource in Calendar View could leave the original booking visible at its old position while also creating the moved copy, making it appear as though the room was double-booked. The original entry is now correctly removed when the booking is moved. --- # 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.9-1st-october-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.