> 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.5.0-7th-october-2026.md).

# v3.5.0 - 7th October 2026

### Xovis PC2SE People Counting Integration

**Who this is for:** Facilities Managers, IT Admins

UMA Vision now supports the Xovis PC2SE people-counting sensor, giving you accurate real-time occupancy data from a proven overhead sensor — whether mounted in the centre of a room or over a building entrance.

#### Why it matters

* **Room occupancy** — a single sensor in the centre of a room counts how many people are present, feeding live occupancy into the floor map, device pages, and insights
* **Floor and building occupancy** — mount several sensors over the entrances to a floor or building, assign them all to the same resource, and UMA combines their counts into a single total. Adding or removing a sensor takes effect immediately
* **Auto-book and auto-release** — enable automatic booking when people enter and automatic release when a room empties, just as you can with other occupancy sensors
* **Slots into your existing setup** — add the sensor by serial number, assign it to a resource, and occupancy data flows into the same dashboards, reports, and analytics used by Milesight, Logitech, and other supported sensors

***

### Visitor Kiosk Calendar Employee Directory Search

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

Admins can now let the visitor kiosk search the connected calendar directory (Microsoft 365 or Google Workspace) when employees check in — so staff who aren't provisioned as UMA users can still find themselves by name.

#### Why it matters

* **New company setting** — "Search visitor kiosk employees from" (Calendar / UMA), found alongside the existing booking panel setting in Company Settings. It only appears for companies on a non-UMA calendar
* **Separate from the booking panel setting** — the existing "Search booking panel users from" setting is unchanged and has no effect on the kiosk, so you can enable calendar search on the kiosk without changing how booking panels work
* **Host field unaffected** — the host lookup on the same kiosk screen continues to use UMA users regardless of this setting


---

# 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.5.0-7th-october-2026.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.
