> 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/partners-flow/partner-dashboard.md).

# Partner Dashboard

Monitor your components sales rates insing the convenient metrics dashboard view.

Partner Dashboard is where you get insights into the components sales trends, usage volumes and health checks.

The Dashboard on the partner side offers you to monitor the following metrics for a selected year:

* **Month - Active licences** - A total number of active licences for your components in the current month.
* **Year - Active licences** - A total number of active licenses for your components in the current year.
* **Total Number of Installations** - A yearly timeline chart with number of installed components on customer tenants divided by type.
* **Total Number of Downloads** - A yearly timeline chart with number of your components bought by customers divided by type.

<figure><img src="https://270962768-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FaAxCFK0JJRlhIPufuXz8%2Fuploads%2Fgit-blob-179d841df61c5d63501dd09362d070cd9698b0e4%2Fpartner_library_partner_dashboard.png?alt=media" alt="Emporix Partner Library - Partner Dashboard"><figcaption><p>Monitor components statistics in the Partner 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/partners-flow/partner-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.