> 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/2025/v3.2.3-4th-september-2025.md).

# v3.2.3 - 4th September 2025

## **Show only bookable resources**

We’ve added a powerful new filter to make finding the right workspace even easier. With the new **“Show only bookable resources”** option, users can instantly hide spaces they aren’t eligible to book — ensuring the workspace view shows only what’s relevant to them.

<figure><img src="https://627748108-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F0shDrJltbdGiCRz6ip4Z%2Fuploads%2FWfed6nA7P0cufsKatu4v%2FScreenshot%202025-09-04%20140750.png?alt=media&amp;token=a2bf3b79-8619-49f8-92c5-14fefc892d71" alt=""><figcaption></figcaption></figure>

**How it works:**

* A new checkbox labelled **“Show only bookable resources”** has been added to the filter on the 'My Floor' page.
* By default, the checkbox is **unchecked**, so all resources are shown.
* When checked, UMA evaluates each resource against:
  * **Assigned desks**
  * **Neighbourhood policies**
* Only resources you’re eligible to book on the selected date will be displayed.

**Why it matters:**\
This feature helps users:

* Quickly identify which spaces are truly available to them
* Avoid confusion from resources outside their booking permissions
* Make faster, smarter booking decisions with a cleaner, tailored view

***

## **Booking release email notifications**

We’ve introduced a new automated notification to keep you informed whenever one of your bookings is released due to **no activity detected by sensors**.

<figure><img src="https://627748108-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F0shDrJltbdGiCRz6ip4Z%2Fuploads%2FcOktH8gN0oJXbsYgYHQG%2FScreenshot%202025-09-04%20141230.png?alt=media&amp;token=f478550f-b60c-4719-a8a5-ee5b025fc7b5" alt="" width="479"><figcaption></figcaption></figure>

**How it works:**

{% hint style="warning" %}
In order for this feature to work, you will need an occupancy sensor and the release setting needs to be turned on.
{% endhint %}

* UMA uses occupancy sensors to monitor activity in booked spaces.
* If no activity is detected during the configured time, UMA will automatically **release the booking** so the resource can be made available to others.
* If you are the organiser of that booking, you’ll receive an **automatic email notification**.

**What the email includes:**

* **Resource name**
* **Date and time** of the booking
* **Meeting subject** (for rooms only)
* A clear explanation of why the booking was released (no activity detected)
* Guidance on what this means:
  * **Rooms:** The room has been unassigned from your booking, but the meeting may still appear in your calendar.
  * **Desks, parking, or other resources:** The booking is removed from your calendar.
* A link back to UMA so you can rebook if needed.

**Why it matters:**

* Ensures organisers are never left wondering why an event disappeared.
* Increases workspace efficiency by freeing up unused spaces.
* Helps teams make better use of shared resources in real time.

This feature runs automatically — no setup or configuration needed.


---

# 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/2025/v3.2.3-4th-september-2025.md?ask=<question>&goal=<user_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.