> For the complete documentation index, see [llms.txt](https://help.security.gallagher.com/knowledge-hub/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.security.gallagher.com/knowledge-hub/configuration-client/licensable-features/pii-redaction.md).

# PII Redaction

### Introduction

The Redaction functionality enables the removal of cardholder personal identifiable information (PII) from Command Centre system to protect client data in European countries and the UK. This feature is provided to users as a set of REST API calls in Command Centre.

In vEL8.80, automatic redactions are configured in Configuration Client, but manual redactions are available only via the REST API. You will need to use a tool like Postman to get this feature to work for manual redactions.

**Note:** Archive and operator events cannot be redacted in this version.

![](https://3000903572-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FfCvaxj3suxNBzdwQndVT%2Fuploads%2Fgit-blob-e5bd68fa0cdeeea84402f57a6195380203235b37%2Fredactiondiagram.png?alt=media)

There are two types of redaction, as follows:

**Cardholder Event Redaction:**

* Can redact Cardholder events, including movement events. The Cardholder’s details are also redacted from all operator events, except for where the Cardholder’s name is specified as being the operator who performed the operator event. You can optionally specify to only redact events that occurred before a specified time.
* The redaction can be scheduled for a future time and date (a pending redaction).
* There can be multiple pending event redactions for one Cardholder at the same time.
* Includes Cardholder-related events generated by the Command Centre system (e.g. an event where Command Centre automatically expired the Cardholder’s Competency).

**Cardholder Information Redaction:**

* Deletes the Cardholder (removes their PDFs, cards, and relationships - e.g. the Cardholder’s Access Group or Operator Group assignments).
* The redaction can be scheduled for a future time and date (a pending redaction).
* Only one pending information redaction can exist for a Cardholder. If a new information redaction is requested while another is already pending for the same Cardholder, the pending one is cancelled and the new one becomes pending.

***

### Licensing

Redaction functionality is a licensable feature. Your license file must contain the following option:

`[Features]`\
`PIIRedaction=1`

***

### Operator Privileges

An operator requires the appropriate privileges to perform redaction tasks. The privileges only apply within the Division assigned to that Operator Group.

<table><thead><tr><th width="391">Operator Privilege</th><th>is required for...</th></tr></thead><tbody><tr><td>"Delete Cardholder History"</td><td>event redactions.</td></tr><tr><td>"Delete Cardholder History" and "Delete Cardholders"</td><td>cardholder redactions.</td></tr><tr><td>"Manage Redaction Settings"</td><td>changing redaction settings.</td></tr></tbody></table>

***

This section covers the following topics:

![](https://3000903572-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FfCvaxj3suxNBzdwQndVT%2Fuploads%2Fgit-blob-f30c70c9dfd07493527af00bd979539606de5d30%2Ftopiclink.png?alt=media) [Redaction Configuration in Command Centre](https://help.security.gallagher.com/knowledge-hub/configuration-client/licensable-features/pii-redaction/redaction-configuration-in-command-centre.md)

![](https://3000903572-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FfCvaxj3suxNBzdwQndVT%2Fuploads%2Fgit-blob-f30c70c9dfd07493527af00bd979539606de5d30%2Ftopiclink.png?alt=media) [Requesting a Cardholder Event Redaction](https://help.security.gallagher.com/knowledge-hub/configuration-client/licensable-features/pii-redaction/requesting-a-cardholder-event-redaction.md)

![](https://3000903572-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FfCvaxj3suxNBzdwQndVT%2Fuploads%2Fgit-blob-f30c70c9dfd07493527af00bd979539606de5d30%2Ftopiclink.png?alt=media) [Requesting a Cardholder Information Redaction](https://help.security.gallagher.com/knowledge-hub/configuration-client/licensable-features/pii-redaction/requesting-a-cardholder-information-redaction.md)

![](https://3000903572-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FfCvaxj3suxNBzdwQndVT%2Fuploads%2Fgit-blob-f30c70c9dfd07493527af00bd979539606de5d30%2Ftopiclink.png?alt=media) [Redacted Cardholders](https://help.security.gallagher.com/knowledge-hub/configuration-client/licensable-features/pii-redaction/redacted-cardholders.md)

![](https://3000903572-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FfCvaxj3suxNBzdwQndVT%2Fuploads%2Fgit-blob-f30c70c9dfd07493527af00bd979539606de5d30%2Ftopiclink.png?alt=media) [Redaction events](https://help.security.gallagher.com/knowledge-hub/configuration-client/licensable-features/pii-redaction/redaction-events.md)


---

# 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.security.gallagher.com/knowledge-hub/configuration-client/licensable-features/pii-redaction.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.
