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

# Desk booking policies

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

### <mark style="color:blue;">Desk release</mark>

This setting is used to automatically cancel desk bookings that a user hasn't checked into after a configurable period of time after the start of the booking.

To configure, use the following format: **1h 30m**

***

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

This setting is used to restrict users from booking desks 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 desk bookings in the future.

***

### <mark style="color:blue;">Half day bookings</mark>

This setting is used to enable morning and afternoon slots for desk bookings.&#x20;

This setting uses the working hours in **booking policies** to determine the AM start time and PM end time.&#x20;

To configure the AM end time and PM start time just enter in the desired time value in each of the fields.&#x20;

For example, if your working hours are 9am - 5:30pm and you want to enable a morning slot for 9am - 12pm and an afternoon slot for 12:30pm - 5:30pm just enter 12pm as the AM end time and 12:30pm as the PM start time.&#x20;

***

### <mark style="color:blue;">Multiple day bookings</mark>

This setting is used to allow employees to book the same desk for multiple days in the future.


---

# 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/desk-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.