> 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/documentation/modules/assets.md).
# Assets
The GLPI Asset module is used to manage all the assets that are part of your IT infrastructure, whether they have been added manually or brought up by automatic inventory
## Asset management in GLPI
In order to manage hardwares and software of an IT infrastructure, GLPI allows natively to list all the assets that are used inside the managed organization.
However, it is possible to automate information pushing from the assets thanks to the native inventory and GLPI Agent.
More information on the GLPI Agent can be found in its dedicated [documentation](https://github.com/glpi-network/gitbook/tree/main/manual/modules/assets/broken-reference/README.md).
{% hint style="info" %}
if you were using Fusion Inventory on your previous versions, this plugin is no longer supported. We advise you to install the GLPI Inventory plugin for tasks such as deploying packages, SNMP inventory and data collection, or to use GLPI's native inventory for simple reporting of your equipment.
{% endhint %}
## Available types
---
# 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/documentation/modules/assets.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.
.png?alt=media){kind=link}
