> 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/tutorials/knowledge/overview.md).

# Overview

The knowledge base of GLPI allows to answer the following needs:

* The first is to centralize internal knowledge to the various technicians.
* The second is to provide users with information (public FAQ) allowing them to solve simple problems alone.

Only the elements of the public FAQ are visible to the users of the simplified interface. Items that are not defined as being part of the public FAQ are only visible within the central console by technicians for example.

It is necessary to select one or more targets for each item in the knowledge base or the FAQ. The target(s) correspond to the entities, profiles, groups or users who can consult the article. As long as no target has been selected for an article, it is only visible to its editor. The article is considered as "unpublished" and appears in the "Unpublished articles" table on the home page of the knowledge base.

It is possible to associate one or more documents to the articles of the knowledge base.


---

# 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:

```
GET https://help.glpi-project.org/tutorials/knowledge/overview.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.