> For the complete documentation index, see [llms.txt](https://docs.platform9.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.platform9.com/managed-kubernetes/5.9/getting-started/pmk-dashboard.md).
# Pmk Dashboard
The PMK account dashboard is the main view which shows a summary of all your Kubernetes clusters, nodes, pods, and cloud accounts that are associated with your Platform9 instance. If you have just created a new account with us, there may not be anything showing in the dashboard. Click on the image below to see further details on each section.
The three main graphical cards seen when opening the dashboard detail the total number of clusters, the total number of nodes, and the total number of cloud providers.
## Editing
To the right of the username is a small pencil icon. Clicking that will open the dashboard editor which allows the user to add, modify, or remove different aspects of information available to the user.
Clicking on any card will add that card to the main dashboard view. To save your choices, click on the *Save* button. Lastly, once the configuration is saved, we can now add Deployments, Services, Users, and Tenants.
---
# 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.platform9.com/managed-kubernetes/5.9/getting-started/pmk-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.
