> For the complete documentation index, see [llms.txt](https://docs.appfarm.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.appfarm.io/reference/dashboard.md). # Dashboard The dashboard is the first thing you see when you open Appfarm Create. It provides important information about your solution's status, upcoming maintenance, resource usage and access to release notes.

## Release info Get information on the latest Appfarm release with a full changelog available. ## Cluster status See the aggregated health status of all your active environments. In the case of any issues, you can find more details under [Deploy](/reference/operations/deploy.md). ## Appfarm platform status See the latest Appfarm platform status and information about any upcoming maintenance. More details and status history are available on [status.appfarm.io](https://status.appfarm.io/). ## Resource usage Get an overview of the number of apps, number of users, available storage, and sent SMS for your solution. --- # 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://docs.appfarm.io/reference/dashboard.md?ask=&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.