> For the complete documentation index, see [llms.txt](https://docs.mclimate.eu/mclimate-enterprise/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.mclimate.eu/mclimate-enterprise/configuration-and-management/buildings/users.md).

# Users

A Building can have one or more users with different levels of control. This is especially useful if you want to segment the data and control between different users.

For example you can limit what tenants in a building can do, you can also assign users only to a certain levels of the structure in order to separate them.

Entering the Users panel is done via the button in the top area of a Building page, where the Billing, Heating profiles, etc. are.

<figure><img src="/files/uAaYYz9QCZnxRBgi7bgJ" alt=""><figcaption><p>Building User area</p></figcaption></figure>

One you open up the User Management page you have a structure view with a search bard to add users and a list of the existing ones at the bottom, where you can edit them.

<figure><img src="/files/pGTYprq7pPQTngU7pgdh" alt=""><figcaption><p>Adding Users on multiple levels</p></figcaption></figure>

{% hint style="info" %}
Users can be added on multiple levels, where the structure is hierarchical. A user on a top level has control over all levels below and not control over those above.
{% endhint %}

For example in order to add an User at the highest level (the Building itself) you can press on the blue icon with the plus (see image below). This will open up a window where you add an email to associate with the user (an invite will be sent to them if they are not in the MClimate system already.) Select the role, the Admin is the most capable, Moderators have some, but not all control and End-Users can observe data.

<figure><img src="/files/xpiBhoneY1HyMNVWG7wj" alt=""><figcaption><p>Creating a Building Administrator</p></figcaption></figure>

You can have as many users as you need to segment control of the Building in the best way for your use-case. You can have different rights depending on the role, also depending on the level you put the user at.

For example you can have the following structure, with the newly created Administrator at the top and supplement users on lower levels.

<figure><img src="/files/8PhVAIJOtweEBmiqSHtS" alt=""><figcaption><p>Example Users structure</p></figcaption></figure>

You can see the full structure with its levels if you expand it on top, where you can also delete users.

There is also a full list of all users and their status in a table at the bottom of the screen where you can delete/edit a user's role via the pen icon in the Manage section.

<figure><img src="/files/pDWIwI1rRI9pfiE8jmqD" alt=""><figcaption><p>Editing a User</p></figcaption></figure>

Now that we have the User management figured out we are going to discuss Heating Profiles in the next section. They are a great way to manage your building and optimize its heating capabilities, which is especially helpful for Managers and Maintenance staff.


---

# 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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.mclimate.eu/mclimate-enterprise/configuration-and-management/buildings/users.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.
