> 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.md).

# Configuration and Management

This chapter will expand on the possibilities of configuring a building in a functional way, so that the user can get the most of the management platform. The following topics will be covered:

1. Buildings
   * Building Dashboard - a summary of the main components of the Building
   * Users - how to manage data visibility and device control via user levels
   * Heating Profiles - timeslot based automated control of heating/cooling over the week
2. Building Management
   * Floors and Floor plans - the base layer of building partitioning
   * Spaces and Rooms - a lower level layer structure that allows for better allocation of resource and data representation
   * Moving a device between Buildings
3. Device
   * Monitor
   * Dashboard
   * Control
   * Battery Estimation
   * Command Logs
   * Uplink Data
   * Bulk Device Management


---

# 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.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.