> 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/readme-1-1/discovery.md).

# Understanding the interface

Depending on the user's profile, some menus and content may differ, but the logic of the interface remains the same.

The GLPI interface is made up of different areas grouping together the application's functionalities according to their nature.

![General interface of GLPI](https://3503800744-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FIiEHKRx5AeABNDLcRlWX%2Fuploads%2FWmAfFhO3TKT8yCX7TkxA%2Fmain_menu.png?alt=media\&token=36b8b5a3-407b-4331-bdf8-bc3fb8a2964f)

1. The user menu allows you to manage your preferences, access help, change the current language, change your current profile and entity, and disconnect.
2. The main menu allows you to navigate through the different modules.
3. The breadcrumb trail allows you to locate the context of use of the main work area.
4. The main working area is the privileged space for interaction with the application.
5. The search box allows you to perform a global search at any time.


---

# 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/readme-1-1/discovery.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.