> 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/area-management/areas-auditing/area-management-set-up.md).
# Area Management Set Up
Version number dffe1ef on 25 August
Area Management supports two workflows:
* **Cardholder Addition**
* **Cardholder Removal**
You can configure either workflow, both workflows, or neither workflow.
{% stepper %}
{% step %}
### Go to Settings module
The settings module contains two tabs for configuring system settings: the Command Centre tab and the Area Management tab.
{% endstep %}
{% step %}
### Configure common Area workflow settings
\
Select the **Area Management** tab. Configure the workflow and cardholder quick view common settings:
* Select the **Access Group List**.
* Select the **Cardholder PDF List**.
* Use the **Cardholder PDF Filter** to select fields for both the workflow and cardholder quick view.
* Select **Show Cardholder Competencies** to display all competencies in the cardholder quick view.
*Cardholder Quick view*
.png?alt=media\&token=916748dc-93cf-4934-abc1-2d1b8b2736a4)
Select a **Cardholder Addition Workflow**, a **Cardholder Removal Workflow**, both, or neither.
{% endstep %}
{% step %}
### Configure Cardholder Addition
Configure the addition settings:
* Set the button name for the **Cardholder Addition Label**.
* Select your workflow for **Cardholder Addition Workflow**.
{% endstep %}
{% step %}
### Configure Cardholder Removal
Configure the removal settings:
* Set the button name for the **Cardholder Removal Label**.
* Select your workflow for **Cardholder Removal Workflow**.
{% endstep %}
{% step %}
### Click Save
{% 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/area-management/areas-auditing/area-management-set-up.md?ask=&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.