> 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/administration/profiles/toolstab.md).

# Tools tab

## Tools Permissions

The 7 standard permissions will not be listed (see [Permissions descriptions](/documentation/modules/administration/profiles/profiles.md)).

### Simplified Interface

<figure><img src="https://3503800744-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FIiEHKRx5AeABNDLcRlWX%2Fuploads%2F8rw4Lgs1FFJL7lD6gQGA%2Fauthorizations_tools_self_service.png?alt=media&amp;token=f0c8e842-2b91-4aa9-8418-daf995272f74" alt="../images/toolsPO.png"><figcaption></figcaption></figure>

* **Knowledge base :**
  * **Read the FAQ**: see the knowledge base articles which are published in the FAQ.
* **Reservation:**
  * **Read:** can list reservation asset;
  * **Make a Reservation**: reserve an asset;
* [**Reminders**](/documentation/modules/tools/reminders.md): can read reminders
* [**RSS Feed**](/documentation/modules/tools/rssfeed.md): can read RSS Feed

### Standard Interface

Common fields with the simplified interface will not be detailed.

<figure><img src="https://3503800744-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FIiEHKRx5AeABNDLcRlWX%2Fuploads%2F3jJuxO0dGAOGbk0zvIOj%2Fauthorizations_tools_standard.png?alt=media&amp;token=1ee4d9ce-2c82-4dc9-b1e3-34f37ce52d0c" alt="../images/tools_standard.png"><figcaption><p>Tools permissions</p></figcaption></figure>

#### Knowledge Base Permissions:

* **Knowledge Base Administration**: administer knowledge base access;
* **Publish in the FAQ**: add or remove an article from the FAQ;
* **Comment KB entries**: allows to add a comment in every article ine the knowledge base

**Public saved searches**:

* **manage personnal**: allows to add/update/delete [personnal saved searches](/documentation/readme-1-1/saved-searches.md)

**Report**:

* **read**: can read and export [reports](/documentation/modules/tools/reports.md)

#### Projects Permissions

<figure><img src="https://3503800744-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FIiEHKRx5AeABNDLcRlWX%2Fuploads%2FQt9O0pw7TJR9odvHji8g%2Fauthorizations_projects.png?alt=media&amp;token=a9eedc04-f29e-4cbe-a2f3-77b9083a0402" alt="../images/projects.png"><figcaption></figcaption></figure>

* **See (Actor)**: see the projects I have created or for which I am the supervisor or member of the supervisor group.
* **See All**: see all the entity's projects.

#### Tasks Permissions

* **See (Actor)**: see the tasks I created.
* **Update (Actor)**: modify the tasks that I have created or for which I am a member of the team.


---

# 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/administration/profiles/toolstab.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.