> 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/getting-started/settings/auto-book-release.md).

# Auto book / release

UMA is equipped to autonomously schedule or cancel meetings by detecting occupancy through a range of integrated sensors. 

To set up automatic booking or release, start by incorporating an occupancy sensor from our list of integration partners. 

Once integrated, you can customise the device settings to automatically schedule or release based on a predefined duration of occupancy or lack thereof in the area. 

{% hint style="warning" %}
If employing a basic PIR sensor, it's advisable to maximise data transmission frequency to minimise potential hiccups. For optimal results, we suggest utilising this feature in conjunction with a real-time counting device like a people counting sensor.
{% endhint %}

{% hint style="danger" %}
Private meetings and private organisers are not supported with this feature.
{% endhint %}

For more information on these settings click [here](/uma-knowledgebase/getting-started/policies/general-policies.md).

Follow our sensor deployment guides [here](/uma-knowledgebase/integrations/iot-sensors.md).


---

# 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/getting-started/settings/auto-book-release.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.