> 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/inventory/advanced-usage/using-blacklist.md).
# Using blacklist
{% hint style="danger" %}
**This is for advanced use only**
{% endhint %}
The blacklist identifies the information that will not be retrieved when a PC is inventoried or when users are synchronised.
It is possible to prohibit a certain amount of information, such as IP addresses in 0.0.0.0 or a user with an @yopmail.com email address.
{% hint style="success" %}
You can blacklist the following items:
* IP
* MAC
* Serial number
* UUID
* Email (for users)
* Model
* Manufacturer
* Manufacturer
{% endhint %}
## Add a new blaclist
For our example, we will block IPv6 forwarding
* To configure a blacklist, go to **`Setup`** > **`Dropdowns`** > **`Blacklists`**
* Click on **`+ADD`**
* Name your new blacklist
* Indicate the value (**`::1`** for IPv6)
* Select the expected value (IP for our example)
View of blacklist
## Delete a Blacklist
* To delete a blacklist, click on **`Delete permanently`**
Delete a blacklist
* You can use massive action to delete one or more blaclists
---
# 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/inventory/advanced-usage/using-blacklist.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.
