> 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/enterprise-data-interface/configuring-an-interface/excluding-access-groups.md).

# Excluding Access Groups

### Introduction

This procedure describes how to exclude specific Access Groups when assigning and removing access.

### Procedure

1. Click the **Mappings and Operator** tab.

   ![](https://3000903572-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FfCvaxj3suxNBzdwQndVT%2Fuploads%2Fgit-blob-1b96e08007da2c347b841ce4e2ebb8c096caabab%2Fmappingsandoperatortab_new.png?alt=media)
2. Select the Access Group you want to exclude when processing a cardholder's access from the **Access Groups to Exclude** drop-down list.
3. Click the **Add** button. The Access Group is added to the exclusion list below.
4. To remove an Access Group from the grid, click the **Remove** button.
5. You can type the name of an Access Group to exclude in the field below. This field accepts wildcard characters. By using wildcard characters you can specify multiple Access Groups to exclude. Refer to [Wildcard characters](https://help.security.gallagher.com/knowledge-hub/configuration-client/licensable-features/enterprise-data-interface/configuring-an-interface/defining-the-source-data-location/wildcard-characters.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/enterprise-data-interface/configuring-an-interface/excluding-access-groups.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.
