> 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/user-guides/resource-scheduling/book-a-desk.md).

# Book a desk

To book a desk, navigate to **my floor** within the **workspace** group and use either the map, calendar or list view to identify the desk you want to book.

<figure><img src="https://627748108-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F0shDrJltbdGiCRz6ip4Z%2Fuploads%2FV6YXPXAB7Z5f2vq46FPd%2FBook%20a%20desk.gif?alt=media&amp;token=9130901d-f98b-4609-bde1-d9eaea4ab682" alt=""><figcaption><p>Click on GIF to enlarge</p></figcaption></figure>

If you hover over the desk, you will see the following information:

* <mark style="color:blue;">**The availability of the desk**</mark>
* <mark style="color:blue;">**The organiser of the desk booking (if it's busy)**</mark>
* <mark style="color:blue;">**Any relevant description added by an admin**</mark>
* <mark style="color:blue;">**If the desk is assigned to a specific employee**</mark>

To book on behalf of another user, check out this handy guide [here](/uma-knowledgebase/user-guides/resource-scheduling/book-on-behalf-of.md).

{% hint style="info" %}
Are you an UMA admin? Check out our desk booking policies [here](/uma-knowledgebase/getting-started/policies/desk-booking-policies.md).
{% 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/user-guides/resource-scheduling/book-a-desk.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.