> 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/building-dashboard.md).

# Building Dashboard

This is your main Building view and it contains several sections with a good amount of data. You can navigate to any subsection of the Enterprise platform from here, each of which has its separate chapter of the documentation, so read on.

For now let us look at a summary of the different parts of the Building Dashboard before going into detail in each one:

1. Connectivity center - this is where you can keep an eye on the health of your network. 
2. Mold detection summary - this section gives you an overview of the overall Mold index (the likelihood of mod developing).
3. Floor plans - if you have created any floor plans this is where they will be listed.
4. Dashboards - a Dashboard is a functional component that allows you do customize your data visualization.
5. Devices - this is the area where a list of all devices that are currently in the Building is displayed.

Proceed to the next chapter to explore each of the portions of the Building Dashboard in details.


---

# 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/building-dashboard.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.