> For the complete documentation index, see [llms.txt](https://docs.mluvii.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.mluvii.com/en/for-administrators/company-management/licences.md).

# Licences

In the Licenses tab you can **find comprehensive information about the use of your licenses**. You can also freely filter the data in the chart at the bottom of the page. In addition to the data about the company you are in, you will find, for example, the groups to which you are simultaneously assigned.

In Dashboard, you can also monitor the following information about **company licenses**:

* **the current use of licenses** - how many operators are simultaneously logged in mluvii (across tenants).
* **use of licenses over the course of time** - in the timeline, you can also set the graphic representation of the licenses used for the precise time period.


---

# 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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.mluvii.com/en/for-administrators/company-management/licences.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.