> 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/site-installation/access-zones/anti-passback/forgive-a-specific-cardholder.md).

# Forgive a specific Cardholder

### Introduction

This procedure describes how to set up "Anti-Passback Forgive" for a specific cardholder, which will allow that cardholder to re-enter an anti-passback zone even though they have not made a valid exit.

You must have the "Override" operator privilege, and be in the same Division (or a parent Division) as both the Access Zone and the Cardholder.

### Procedure

1. Click **Manage** from the menu bar, then **Cardholders**.

   The **Cardholder** List Window opens (in [grid view](https://help.security.gallagher.com/knowledge-hub/configuration-client/introduction-to-command-centre/knowing-your-way-around/list-windows/grid-view.md)).
2. Highlight the Cardholder you require.
3. **Right click** and select **Properties**.
4. Click the **Status and Overrides** tab.

   ![](https://3000903572-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FfCvaxj3suxNBzdwQndVT%2Fuploads%2Fgit-blob-56e43c9b67fdde8bdd7fb6fc1ce8310ef5bc6ffc%2Fcholdoverride.png?alt=media)
5. Select the Access Zone you want to override from the drop-down list, then click the **Forgive** button.

   **Note:**

   If the Access Zone selected is a member of an Access Zone Group, the following message will display beside the **Forgive** button:

   *Forgive applies to the master zone: \<Master Zone Name>*

### Result

The next time this cardholder presents their card at a door leading into this Access Zone, they will be granted access if they have that privilege.


---

# 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/site-installation/access-zones/anti-passback/forgive-a-specific-cardholder.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.
