> For the complete documentation index, see [llms.txt](https://docs.bluestorm.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.bluestorm.io/dashboards/platform.md).

# Platform

The platform dashboard provides an aggregated view of your entire Mendix app landscape managed by AppControl. The dashboard is visible to all users and is not limited to the specific apps that a person has access to. The dashbaord metrics are updated dynamically when loaded.

The dashboard has the following tiles:

<details>

<summary>Apps</summary>

This tile shows the number of apps that you have that are licensed or are free apps. Additionally, it shows the number and type of environments that you are using.

</details>

<details>

<summary>Alerts</summary>

The Alerts tile shows you the number of apps with a specific alert status. Click on the tile to open the Alerts dashboard.

</details>

<details>

<summary>Components</summary>

This tile shows the Mendix version in use by your production environments, as well as the number of and support status of the components in use by all apps in production environments.

</details>

<details>

<summary>Policies</summary>

This tile shows the state of the policies that apply to your production environments. The breakdown of categories shows the number of policy checks for each category that have failed. For instance if you see that there are 114 security check failures, it means that in total 114 policy checks have failed across all apps in your production environments.

</details>

<details>

<summary>Development</summary>

This tile shows a summary of your development activity: the number of commits, builds, and deploys. Note: Builds and deploy information is only available if you use the build and deploy tasks in pipelines in AppControl to build and deploy your apps.

</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.bluestorm.io/dashboards/platform.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.