> For the complete documentation index, see [llms.txt](https://help.glpi-project.org/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.glpi-project.org/faq/glpi/reports.md). # Reports *** ### Is it possible to use reports in GLPI? GLPI allows the generation of a number of reports related to your equipment, financial data, etc.: * **The default report**: This report lists the equipment present in the park sorted by operating system for computers and bytype for other equipment. * **Equipment under maintenance contract**: Equipment under maintenance contract with a third party. It is possible to obtain adetailed report by type of equipment and by date of purchase. Multiple selection is allowed. * **Equipment report by year**: Information on the purchase date, warranty and associated contracts for one or more years.Multiple selection is allowed. * **Hardware Inventory Financial Information Report**: Summary financial information for computers, printers, network hardware,monitors and peripherals as well as the total value and net book value of your assets. * **Other Financial Information Report**: Summary financial information for cartridges, licenses and consumables. * **Network Report**: Network information by location, network equipment or network outlets. * **Loan report**: Summary of current, future or past loans for a given user. * **Status report**: Summary by type of equipment of the different statuses. You can also use the "more reporting" plugin to obtain additional reports --- # 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://help.glpi-project.org/faq/glpi/reports.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.