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

# General policies

### <mark style="color:blue;">Working days/hours</mark>

Please utilise this option to verify the standard work hours adhered to by your staff.&#x20;

This feature serves a dual purpose:&#x20;

UMA relies on this information for precise reporting on occupancy, while also employing the working hours for scheduling start and end times for bookings.

***

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

This configuration establishes a default time frame for direct bookings made through the UMA booking panel interface.&#x20;

{% hint style="info" %}
Please note that this setting exclusively impacts booking panels.
{% endhint %}

***

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

This configuration enables automatic cancellation of a reserved resource if it remains unoccupied for a predefined period.&#x20;

{% hint style="info" %}
Please ensure that an occupancy sensor is linked to the respective resource for this setting to take effect.
{% endhint %}

***

### <mark style="color:blue;">Book rounding</mark>

This feature aims to optimise booking slots for greater efficiency.&#x20;

It allows for rounding up meeting durations to the nearest 5, 10, or 15 minutes, preventing odd time slots like 10:17 - 10:47.

***

### <mark style="color:blue;">Book rounding type</mark>

This setting decides whether to round up or down meetings when using **book rounding**.

***

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

This configuration establishes a default duration for automatic bookings made through an occupancy sensor.&#x20;

{% hint style="info" %}
Please ensure that an occupancy sensor is linked to the respective resource for this setting to take effect.
{% endhint %}

***

### <mark style="color:blue;">Auto book after duration</mark>

This configuration determines the default duration for booking a resource after detecting occupancy.&#x20;

{% hint style="info" %}
Please ensure that an occupancy sensor is linked to the respective resource for this setting to take effect.
{% endhint %}

***

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

This setting is used to enable users the ability to check in to Zones on the UMA floor maps.

Navigate to **My Floor** and hover over the Zone you wish to record your attendance within.

Users are able to check in to Zones either on the day or in the future.

{% hint style="info" %}
Please note when Zone Booking is enabled, desk booking is automatically disabled.
{% endhint %}


---

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