> For the complete documentation index, see [llms.txt](https://docs.parallels.com/landing/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.parallels.com/landing/daas-guides/daas-administrators-guide/parallels-daas-interface/insights.md).

# Insights

The **Insights** category allows you to inspect usage statistics.

## Licenses

The **Licenses** category shows key metrics on license usage.

This category contains the following information:

* **License usage**: The percentage of the currently assigned licenses. 
* **Available:** The number of available user seats. 
* **Total licenses:** The total number of user seats. 
* **License expires:** The number of days until the license expires and the expiration date.
* **License type:** One of the license types described in [**Parallels DaaS licensing**](/landing/daas-guides/daas-administrators-guide/parallels-daas-licensing.md).
* **License usage per month:** The number of allocated seats per month.
* **Allocated seats:** Information about all added users and whether they have a seat allocated to them. You can deallocate a seat by right-clicking user and selecting **Deallocate seat**.

{% hint style="info" %}
License usage charts are updated every 24 hours.
{% endhint %}


---

# 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.parallels.com/landing/daas-guides/daas-administrators-guide/parallels-daas-interface/insights.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.