> 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/policies/room-booking-policies.md).

# Room booking policies

UMA has a number of meeting room booking policies that can be implemented to control your hybrid working environment for your employees.

### <mark style="color:blue;">Booking duration</mark>

Use this setting to enter a maximum duration for meeting room bookings.

To configure, enter a number and choose **days** or **hours**.

***

### <mark style="color:blue;">Room booking threshold</mark>

This setting is used to restrict users from booking meeting rooms too far in advance.&#x20;

Enter in a numerical digit and select 'Days', 'Weeks' or 'Months' from the drop down to create a restriction for meeting room bookings in the future.

***

### <mark style="color:blue;">Meeting room check in</mark>

This setting is used to allow users to check into their meeting room booking to confirm their booking.

Enter in a numerical digit (in minutes) to allow users to check in before a meeting starts.

If you don't want users to check in before the meeting starts then use '0'.


---

# 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/policies/room-booking-policies.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.