> 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/glpi-12/welcome-to-glpi-12/browse-the-modules.md).

# Browse the modules

The different GLPI functions have been grouped into several modules, built around similar usage contexts. The vertical menu on the left of the interface allows you to navigate between these modules.

<table data-view="cards"><thead><tr><th></th><th></th><th></th><th data-hidden data-card-cover data-type="image">Cover image</th><th data-hidden data-card-target data-type="content-ref"></th></tr></thead><tbody><tr><td><h3><i class="fa-box-isometric">:box-isometric:</i></h3></td><td><h4>Assets</h4></td><td>The assets module provides access to the different inventoried hardware.</td><td></td><td><a href="https://help.glpi-project.org/glpi-12/assets/overview.md">ASSETS</a></td></tr><tr><td><h3><i class="fa-headset">:headset:</i></h3></td><td><h4>Assistance</h4></td><td>The assistance module allows you to create and track tickets, problems, and changes; as well as view statistics.</td><td></td><td><a href="https://help.glpi-project.org/glpi-12/assistance/overview.md">ASSISTANCE</a></td></tr><tr><td><h3><i class="fa-wallet">:wallet:</i></h3></td><td><h4>Management</h4></td><td>The management module allows you to manage contacts, suppliers, budgets, contracts, and documents.</td><td></td><td><a href="https://help.glpi-project.org/glpi-12/management/licenses.md">MANAGEMENT</a></td></tr><tr><td><h3><i class="fa-briefcase">:briefcase:</i></h3></td><td><h4>Tools</h4></td><td>The tools module allows you to manage projects, notes, the knowledge base, reservations, RSS feeds, and consult reports.</td><td></td><td><a href="https://help.glpi-project.org/glpi-12/tools/projects.md">TOOLS</a></td></tr><tr><td><h3><i class="fa-shield-check">:shield-check:</i></h3></td><td><h4>Administration</h4></td><td>The administration module allows you to administer users, groups, entities, profiles, rules, and dictionaries. It also allows for the management of the email queue.</td><td></td><td><a href="https://help.glpi-project.org/glpi-12/administration/users.md">ADMINISTRATION</a></td></tr><tr><td><h3><i class="fa-gear">:gear:</i></h3></td><td><h4>Setup</h4></td><td>The setup module provides access to GLPI's general configuration options: notifications, collectors, automatic tasks, authentication, plugins, external links, SLAs, title management, component management, as well as field uniqueness control.</td><td></td><td><a href="https://help.glpi-project.org/glpi-12/setup/asset-definitions.md">SETUP</a></td></tr></tbody></table>

{% hint style="warning" %}
The menus presented vary depending on the permissions of the logged-in user. The navigation context is presented to the user in the breadcrumb trail.
{% 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://help.glpi-project.org/glpi-12/welcome-to-glpi-12/browse-the-modules.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.
