> 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/accessnow-user-guide/workflow-creation/creating-and-managing-workflows/working-with-workflow-templates/area-management-cardholder-removal-workflow.md).

# Area Management: Cardholder Removal Workflow

## Use Case Overview

The Cardholder Removal Workflow is an example of a **System** workflow. It is used to automatically remove selected cardholders from an access group during an access audit. It is available to approvers of the respective Access Groups.

When configured, it is triggered by clicking the removal button in the **Cardholder tab** within the **Areas module.**

<div data-with-frame="true"><figure><img src="https://3605010251-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FHOxYzVrszbXcNBUauC0e%2Fuploads%2F8qu06oCD6CD0jAvawiWq%2FScreenshot%202026-05-08%20at%2013.13.27%20%E2%80%93%20ScreenClip.png?alt=media&amp;token=302855c1-41d9-4da2-b6ec-5e27085c5b81" alt=""><figcaption></figcaption></figure></div>

## Workflow Configuration

This workflow does not require any additional configuration unless the customer wants to customize it, for example, by sending notification emails to cardholders whose access has been removed.

{% stepper %}
{% step %}

### [Create a New System Workflow](/knowledge-hub/accessnow-user-guide/workflow-creation/creating-and-managing-workflows/workflow-management/creating-a-new-workflow.md)

To create a workflow from a template, first manually create an empty workflow.
{% endstep %}

{% step %}

### [Import a Template](/knowledge-hub/accessnow-user-guide/workflow-creation/creating-and-managing-workflows/working-with-workflow-templates/importing-workflows.md)

Download the Area Management Cardholder Removal workflow template you want to customize and import it into the empty workflow created earlier.

This workflow template does not need additional configuration in its default setup.

<figure><img src="https://3605010251-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FHOxYzVrszbXcNBUauC0e%2Fuploads%2FF5DtCEwpAhAQYVUOKmNG%2Fimage.png?alt=media&amp;token=77a04c8f-840a-4fad-9d57-f34214ad1227" alt=""><figcaption></figcaption></figure>
{% endstep %}

{% step %}

### [Publish the Workflow](/knowledge-hub/accessnow-user-guide/workflow-creation/creating-and-managing-workflows/workflow-management/publishing-a-workflow-version.md)

After testing and confirming the results, publish the workflow to make it visible in the system's configuration drop-down lists.
{% endstep %}

{% step %}

### [Select the Workflow in the Area Management Settings](/knowledge-hub/accessnow-user-guide/area-management/areas-auditing/area-management-set-up.md#configure-the-removal-workflow)

Follow the instructions in the [Set up the Access Removal Workflow](/knowledge-hub/accessnow-user-guide/area-management/areas-auditing/area-management-set-up.md) and select the workflow during the Area Management configuration.
{% endstep %}
{% endstepper %}


---

# 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/accessnow-user-guide/workflow-creation/creating-and-managing-workflows/working-with-workflow-templates/area-management-cardholder-removal-workflow.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.