> 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/maps/assign-resources-to-map.md).

# Assign resources to map

Prior to being able to access real-time occupancy information and enable users to reserve resources via the map view, you must first allocate resources to areas of the map.

To create resources, check out this [guide](/uma-knowledgebase/getting-started/set-up-your-organisation/add-resources.md).

Navigate to your floor map and click on **edit map**.

{% hint style="info" %}
Only an admin can assign resources to a map.
{% endhint %}

![](https://help.meetuma.ai/rest/api/content/986939399/child/attachment/att992903185/download)

Select a region on the map to allocate a resource and select the resource from the drop down on the left hand menu.

![](https://help.meetuma.ai/rest/api/content/986939399/child/attachment/att993329153/download)

Switch off the map editing mode, then you can either hover over or click on the resource to access additional information or book the space.


---

# 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/maps/assign-resources-to-map.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.