> 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/release-notes/web/2021/v.2.1.0-16th-july-2021.md).

# v.2.1.0 - 16th July 2021

**Book For Other Users**

From a manager's perspective, it's important to be able to book a desk on behalf of your team members if you're planning a day in the office.

To book a desk on behalf of other users you need to be given the 'Manager', 'Advanced Manager' or 'Admin' role.

Navigate to the Floor Maps page and click on any desk and you'll be shown a 'Book on Behalf of' option.

<figure><img src="https://627748108-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F0shDrJltbdGiCRz6ip4Z%2Fuploads%2FzbTb1QryMMcKgUQCfbSN%2F_Book%20a%20desk%20on%20behalf%20of%20-%202.png?alt=media&amp;token=3e133dc9-17c4-4ef0-b1f8-9455827a335c" alt=""><figcaption></figcaption></figure>

If you toggle this on you'll be able to search for and select a user to book on behalf of.

The booking process from there on is identical to normal. The booking will appear in the specified user's calendar and allow the user to edit or cancel the booking should they wish.

**Note that some users may be hidden from this search if they've been given the 'Hidden User' role.**


---

# 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/release-notes/web/2021/v.2.1.0-16th-july-2021.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.
