# v3.3.4 - 8th April 2026

## Building level permissions

**Who this is for:** Company Admins

Admins can now restrict which buildings a user has access to, ensuring they only see and interact with the buildings relevant to them.

#### What's new

* A new **Buildings** multi-select field is available when adding or editing a user.
* When one or more buildings are selected, the user is restricted to only those buildings across the entire platform — including calendars, dashboards, floor plans, and visitor management.
* If no buildings are selected, the user retains access to all buildings (the default behaviour).

#### Who it applies to

* Advanced Manager, Manager, Hidden User, and User roles.
* Admin roles are unaffected and continue to have access to all buildings.

***

### Device downlink capabilities

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

Admins can now send supported commands to IoT devices directly from within UMA, removing the need for vendor tools or physical access.

#### What's new

* A **Downlinks** tab is now available on supported LoRaWAN IoT devices (Milesight and Netvox).
* Supported commands include rebooting the device, changing the reporting interval, and configuring the time-to-vacancy setting.

#### How it works

* Navigate to a supported device and open the **Downlinks** tab.
* Select a command from the available options and submit it.
* Commands are delivered to the device via UMA's downlink pipeline.

***

### People counting device group

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

When multiple people-counting sensors are assigned to a single resource, UMA now aggregates their IN and OUT counts to provide an accurate total for that space.

Assigning multiple people-counting sensors to one resource now produces a combined occupancy count.

{% hint style="info" %}
This feature is only available for Milesight VS121, VS133 and VS135 devices.
{% endhint %}

***

### Update visit host field

**Who this is for:** All Users (visit creators)

The host selection field when creating a visit has been updated for better performance and usability.

#### What's changed

* The host field no longer attempts to load the entire company directory on open.
* You now **type to search** for a host, which is significantly faster for large organisations.
* A new **"Assign myself as host"** button has been added, covering the most common scenario where the logged-in user is the meeting host.

***

### Booking reminder improvements

**Who this is for:** All Users (event organisers)

Booking reminder emails have been simplified to make them clearer and more concise.

#### What's changed

* The **green "Confirm" button** has been removed from the reminder email.
* The **email subject line now includes the booking date**, making it easier to identify which event the reminder is for at a glance.
* All other reminder content and the existing reminder schedule remain unchanged.

***

### Change auto-book subject

**Who this is for:** All Users

The subject of resource events created via Auto-Book has been changed from "Booked by UMA" to **"Auto-booked"**, making it clearer how the booking was created and reducing confusion.

***

### Bug fixes

* **Google Calendar declined events** — Fixed an issue where a resource that declined a Google Calendar event still appeared as unavailable in the booking drawer on the My Floor page.