> 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.7-9th-september-2026.md). # v3.4.7 - 9th September 2026 ### Check In on Behalf of Another User **Who this is for:** Advanced Managers, PAs, EAs Authorised users — such as Personal Assistants and Executive Assistants — can now check in to a desk booking on behalf of the person they support, directly from the My Bookings page. #### Why it matters * Search for and select another user on My Bookings to see their upcoming bookings * If a booking is currently eligible for check-in, you can complete the check-in on their behalf — no need for the person to do it themselves * Ideal for PAs and EAs who already manage bookings on behalf of others and now need to handle the check-in step too *** ### Working Hours Toggle for Utilisation Analytics **Who this is for:** Admins, Workplace Managers (Analytics Pro) A new "Working hours" toggle on Analytics Pro dashboards lets you filter utilisation calculations to only count time within your building's configured office hours, giving you a more accurate picture of how spaces are actually used during the working day. #### Why it matters * **More meaningful percentages** — without the filter, a room occupied all day could show 300%+ utilisation because the calculation included evenings and weekends. With the toggle on, utilisation is measured against working hours only * **Per-building accuracy** — each resource's utilisation is clipped against its own building's working hours, so multi-site organisations get correct figures even when buildings have different schedules * **Works across the platform** — the toggle appears on Analytics Pro Space Usage, the Calendar Events table, Free Analytics, AI Reports, and custom dashboards * **Non-destructive** — the toggle is off by default, so existing numbers are unchanged until you choose to filter. Turn it on and off to compare both views *** ### Cisco Room Navigator LED Integration **Who this is for:** Facilities Managers, IT Admins When the UMA room-booking app runs on a Cisco Room Navigator, it now controls the Navigator's LED strip to show room availability at a glance — mirroring Cisco's standard availability colours. #### Why it matters * **Green** — the room is free and no meeting starts within the next 10 minutes * **Yellow** — the room is free but a meeting starts within the next 10 minutes, or the room is booked but no one has arrived yet * **Red** — a meeting is in progress or the occupancy sensor detects people in the room * The LED updates in real time as bookings start and end, new bookings are made, and occupancy changes — no delay, no manual refresh * Works automatically when the app runs on a Cisco Navigator; all other devices are unaffected *** ### Optional Host Field for Walk-In Check-Ins **Who this is for:** Admins, Receptionists Admins can now remove the host field from the ad hoc check-in flow — both for visitors and employees — in organisations where walk-in visitors have no nominated host. #### Why it matters * **New setting** — "Hide Host on Unplanned Visits" in Visitor Management settings, defaulting to on so existing tenants see no change * **Company and building level** — set it once at company level, or override per building. A staffed head office can keep the host field while walk-in sites remove it * **Covers both visitor and employee check-in** — when the setting is off, the host field is removed entirely from the ad hoc flow, not just made optional * **Pre-booked visits unaffected** — the host field remains mandatory for pre-booked visits regardless of the setting * **Clean reporting** — host-less check-ins appear in visitor reports as "No host" rather than blank or error states *** ### Bug Fixes * **"Other" resource type bookings now display correctly in Calendar View** — Bookings for resources with the "Other" type previously appeared as blank blocks without the organiser's name. The organiser is now displayed consistently across all resource types. * **"Book on behalf of" selection preserved when navigating back** — When booking on behalf of another user for a resource with services and approvals, navigating back from the service selection step cleared the selected person. The selection is now retained. * **Desk check-in notifications now appear for time-specific bookings** — Check-in notifications were only appearing for all-day desk bookings, not for bookings with a specific time slot. Notifications now appear for all desk booking types. * **Environmental sensor data reliability improved** — Sensor readings (CO₂, temperature, humidity) could occasionally be missing from meeting event records for long or all-day meetings, and environmental data could disappear from the My Floor view when a resource had multiple sensors. Both issues have been resolved — sensor data is now reliably captured and merged across all sensor types. * **EnOcean sensors can now be assigned to Zones** — Clicking Add after selecting a Zone on the Manage Devices page had no effect for EnOcean sensors. EnOcean devices can now be assigned to Zones successfully. * **All-day desk approvals now display correct times** — All-day desk bookings requiring approval were shown to approvers with a time of 1:00 AM to 1:00 AM instead of the building's configured working hours. The correct working hours are now displayed. * **Calendar Events table now supports full pagination** — The Analytics Pro Calendar Events table was limited to 1,000 rows, silently hiding reservations beyond that threshold. The table now supports full pagination and CSV exports retrieve the complete dataset. * **Drag and drop no longer creates apparent double bookings** — Dragging an auto-booked resource in Calendar View could result in both the original and new time slots appearing occupied. The original slot is now correctly released when a booking is moved. * **AI chart explanations improved** — AI-generated explanations in Analytics could incorrectly describe unused sensor or calendar data as meaningful findings. The AI analysis now correctly identifies when a data source is not configured and excludes it from its commentary. * **Buffer time display fixes** — Buffer time calculations could add 24 hours per day of offset when booking for a future date, and buffered bookings were not appearing in the Insights "Show Meetings" overlay. Both issues have been corrected, and the overlay now also displays bookings at the correct time during daylight saving time. * **Room panels now recover automatically from service interruptions** — Wall-mounted room panels could become permanently unresponsive after a brief service outage, requiring physical access to recover. Panels now automatically reconnect and return to a usable state without manual intervention. * **Building Admin access restored** — Building Admins were receiving an "Access Denied" error when attempting to open building records they were assigned to manage. This has been resolved. * **Service item reliability improved** — Removing all service items from a booking appeared to save but silently reverted, and service requests could be dropped when booking a room group where the service category wasn't configured for all rooms. Both issues have been fixed with proper persistence and clear feedback. * **Visitor and Signage app device settings can now be saved** — Administrators were unable to save settings for Visitor app and Signage app devices, with changes failing silently on save. Device settings for these device types now persist correctly. * **Save button validation tightened** — When editing a booking and changing the duration, the Save button could become enabled without a valid time slot selected, resulting in a false confirmation. The button now remains disabled until a valid selection is made. * **Meeting type now persists correctly** — Changing or clearing the meeting type on an existing room booking appeared to save but silently reverted to the original value. Additionally, clearing a meeting type or deleting a booking did not remove the meeting type from the analytics database. Both issues have been fixed — meeting type edits persist and stale data is cleaned up. --- # 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.7-9th-september-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.