> 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/neighbourhoods/booking-in-a-neighbourhood.md).

# Booking in a neighbourhood

To book a resource within a neighbourhood, you can still book using our web or mobile applications.

To understand how resource booking is affected by neighbourhood policies for each application type you can check below.

### **UMA Vision - Map or List View**

When booking using the map or list view in UMA Vision, if you hover over a resource that has a neighbourhood policy applied you will see information appear on the tool tip related to the teams that are allowed to book that space for the day selected.

If you click on a resource that you don't have access to book, you will receive a message that this resource is assigned to a different team and you aren't able to book.

### UMA Mobile Application

When booking using the map view, if you tap on a resource that you don't have access to book, you will receive a message that this resource is assigned to a different team and you aren't able to book.

When booking using the list view, any resources that you can't book will be filtered out of the view.

### UMA Booking Panel Application

Only the team members/managers will be able to book the room directly from the panel as per the neighbourhood policy.

{% hint style="info" %}
To enforce this we recommend turning **book anonymously** off or even turn booking off completely.
{% endhint %}

### UMA Office Map Application

Only the team members/managers will be able to book the room directly from the display as per the neighbourhood policy.

{% hint style="info" %}
You can disable booking from the office map if required.
{% 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/neighbourhoods/booking-in-a-neighbourhood.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.