# v3.2.7 - 29th January 2026

### Manage other users’ bookings from '*My Bookings'*

**Who this is for:** Admins, Building Admins, Advanced Managers, Managers

You can now **view and manage resource bookings made by other users** directly from the **My Bookings** page, without losing visibility or context.

#### What’s changed

* A **User Select menu** has been added at the top of *My Bookings*
  * Search for a user to find their calendar. Role based access only.
  * Supports favouriting users for quick access
* Selecting a user updates the bookings list to show **their resource bookings**

#### What you can do

* **Edit bookings**
  * Changes are saved in UMA
  * Updates sync to the booked-for user’s Outlook or Google Calendar
* **Cancel bookings**
  * Booking is removed from UMA
  * Event is deleted from the booked-for user’s calendar

#### Permissions & visibility

* **Admins, Building Admins & Advanced Managers**
  * Can view and manage *all resource* bookings on behalf of users
* **Managers**
  * Can manage desk, parking, and other resource bookings
* Only **resource bookings** are shown, general calendar events are excluded

> Existing booking logic is reused; this update adds new UI and user-selection capabilities only.

***

### Neighbourhood colours for floor maps

**Who this is for:** Admins, Building Admins

You can now assign a **colour to each neighbourhood** to visually distinguish departments or areas on floor maps.

#### What’s new

* A **Colour selector** is available when creating or editing a neighbourhood
* Multiple colour options are provided
* Colours are designed to work in both **light and dark mode**

This makes it easier to visually group and identify neighbourhoods across large floors.

***

### Show neighbourhoods on the floor map

**Who this is for:** All users

Users can now visually see **where neighbourhoods are located** directly on the floor map.

#### How it works

* A new toggle **“Show Neighbourhoods”** is available in the *Map View* section
* When enabled:
  * Resources are highlighted using their neighbourhood colour
  * A **colour legend** appears, mapping colours to neighbourhood names
* Designed with accessibility in mind to ensure availability states remain clear

This helps users quickly understand where teams or departments are located.

***

### Cisco Spaces firehose integration

<figure><img src="/files/j4gBIGYxopoa0DFoTwHw" alt=""><figcaption></figcaption></figure>

**Who this is for:** UMA Admins

UMA now supports ingesting **real-time sensor and event data** from the **Cisco Spaces Firehose API**.

#### Supported metrics (initial release)

* Occupancy / people count (zone, room, desk level)
* Presence
* Environmental data where available:
  * Temperature
  * Humidity
  * CO₂
  * VOC
  * Particulate matter
  * Water metrics

#### Admin experience

* New flow: **Admin → Add Devices → Add from Cisco Spaces**
* Sensors appear like native UMA devices:
  * Online/offline status
  * Device cards
  * Statistics & analytics support
* Metrics are mapped into UMA’s normalised telemetry schema for use across:
  * Analytics
  * Automations
  * Booking flows

Cisco Firehose API - <https://developer.cisco.com/docs/cisco-spaces-firehose/api/>

***

### Visitor log & reports: email and phone numbers

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

Visitor contact details are now more complete and actionable.

#### What’s new

* **Visitor log** now displays:
  * Email address
  * Phone number
* **Visitor Reports exports (CSV / Excel)** now include:
  * A Phone Number column
  * Correct mapping per visitor

This makes it easier to contact visitors, meet compliance needs, and export complete records for reporting.


---

# Agent Instructions: 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:

```
GET https://support.meetuma.ai/uma-knowledgebase/release-notes/web/2026/v3.2.7-29th-january-2026.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.