> 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/doc-plugins/plugin-glpi-network/gdpr.md).

# GDPR Tools

## Requirements (self-hosted)

| GLPI Version | Minimum PHP | Recommended |
| ------------ | ----------- | ----------- |
| 11.0.x       | 8.2         | 8.4         |
| 12.0.X       | 8.3         | 8.5         |

{% hint style="info" %}
A [GLPI Network BASIC](https://services.glpi-network.com/#offers) subscription (or higher) is required. This plugin is also available for all GLPI Network [Cloud instances](https://glpi-network.cloud).
{% endhint %}

***

## Install the plugin

* Go to the marketplace. Download and install the **GDPR Tools** plugin.

<div align="left"><figure><img src="https://3573604317-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FuUCcURk2xlvtpVGbiRZf%2Fuploads%2Fv1qvUgNTVofJskyvl5uN%2FGDPR-Tools.png?alt=media&amp;token=772dda36-6b8a-4b05-ae74-8b0f6c51e596" alt="images/GDRP-1.png"><figcaption></figcaption></figure></div>

***

## Configure the plugin

* From **`Setup` > `General > GDPR tools`**

### Cleaning up inactive users

There are two possible ways of managing inactive users:

* Clearing the user's data
* Deleting the user

### Cleaning up user data

When the plugin is configured in **Clean** mode, the following actions will be performed:

* Delete all references to the user from the GLPI history
* Delete all associated emails
* Reset all user fields and profiles
* Move the user to the recycle bin

### Delete the user

When the plugin is configured in "Delete" mode, the following actions will be performed:

* Delete all references to the user from the GLPI history
* Delete all associated emails
* Delete the user

{% hint style="warning" %}
Deletion is permanent, the user cannot be recovered
{% endhint %}

### Scope restriction

The automated deletion process can be restricted to the following scopes:

* All inactive users
* Inactive users with no current tickets
* Inactive users without tickets

<figure><img src="https://3573604317-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FuUCcURk2xlvtpVGbiRZf%2Fuploads%2Fgit-blob-302b1d61a2aff3e8f450823c60ac6732c7e8fb04%2FGDRP-2.png?alt=media" alt="images/GDRP-2.png"><figcaption></figcaption></figure>

### Automated action

Deletion will take place via a standard GLPI automatic action that can be configured to run as often as you like.

* Go to **`Setup` > `Automatic actions`**, and select the **`cleaninactiveuser`** action then configure it according to your needs.

<figure><img src="https://3573604317-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FuUCcURk2xlvtpVGbiRZf%2Fuploads%2Fgit-blob-571c53ee585cc02b719f9636b2abaad2b9deb829%2FGDRP-3.png?alt=media" alt="images/GDRP-3.png"><figcaption></figcaption></figure>

***

## FAQ

If you have any questions about using the plugin, please consult our FAQ

<a href="/faq/plugins/gdpr-tools.md" class="button secondary">Go to FAQ</a>


---

# 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/doc-plugins/plugin-glpi-network/gdpr.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.