> For the complete documentation index, see [llms.txt](https://developer.emporix.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://developer.emporix.io/partner-library/customers-flow/customer-dashboard.md).

# Customer Dashboard

View the usage metrics of the installed Partner components.

On a customer tenant, the Dashboard is where you can check information related to the partner components available on the tenant. See the usage volumes, control costs efficiency and verify your licenses validity.

The Dashboard provides you with visual representation of the following metrics:

* **Licences expiry dates** - The components which licences are about to expire and need your attention, or already expired within the last 30 days.
* **Your components** - The components that are ready to be installed or were recently installed on your tenant.
* **Installed by component type** - The number of components installed on the tenant in each type category.
* **Executions** - The number of components executions in a yearly timeline.
* **Monthly Fee** - The fees due in the current month for the installed components.
* **One-time Fees** - The one time fees the you owe to pay.
* **Fee estimation** - Estimation of yearly fees to pay, calculated based on the currently installed licenses.

All charts support filtering - you can deselect individual components to focus on the data most relevant to you.

<figure><img src="https://270962768-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FaAxCFK0JJRlhIPufuXz8%2Fuploads%2Fgit-blob-089b505dce02b5d0525770dc10fa2f11a691d29c%2Fpartner_library_customer_dashboard.png?alt=media" alt="Emporix Partner Library - Customer Dashboard"><figcaption><p>Get the overview on the installed components in the Customer Dashboard</p></figcaption></figure>


---

# 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://developer.emporix.io/partner-library/customers-flow/customer-dashboard.md?ask=<question>&goal=<user_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.