> 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/adding-a-person-to-an-area.md).

# Adding a Person to an Area

Add a person to an area through the access group membership audit.

This function enables approvers to add people to the areas they manage. It updates the relevant Command Centre Access Group.

{% hint style="warning" %}
To ensure this function operates correctly, first [**set up the access removal workflow**](/knowledge-hub/accessnow-user-guide/area-management/areas-auditing/area-management-set-up.md) in the system.
{% endhint %}

{% hint style="info" %}
This function is restricted to approvers. They can manage only their authorised areas.
{% endhint %}

## Adding a person to an area

{% stepper %}
{% step %}

### Go to the Areas module

It shows the areas you are privileged to manage.

<figure><img src="https://3605010251-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FHOxYzVrszbXcNBUauC0e%2Fuploads%2FCys5FiR8GMrAs71G1ChG%2FScreenshot%202025-09-04%20at%2013.14.26.png?alt=media&amp;token=93d48efa-e82c-4fe9-a641-766f91cf1547" alt=""><figcaption></figcaption></figure>
{% endstep %}

{% step %}

### Click the selected area

The area auditing feature provides two tabs:

* The **Approvers** tab lists people who can approve area access.
* The **Cardholders** tab shows everyone with area access.
  {% endstep %}

{% step %}

### Click the Cardholders tab

The tab displays all people with access to the area.
{% endstep %}

{% step %}

### Click the Add Access action button

<figure><img src="https://3605010251-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FHOxYzVrszbXcNBUauC0e%2Fuploads%2F2WC7hOmeL6v2w0P3a5aK%2FAreas_at_Aug_2026_with_add_selection_names_blurred.png?alt=media&amp;token=205bbe64-cc9e-4b62-853b-68b5e39b1401" alt=""><figcaption></figcaption></figure>
{% endstep %}

{% step %}

### Enter the person's identifier

The system searches Gallagher Command Centre for the person.

It shows whether a matching person was found.

From here, configure the workflow to meet client requirements.
{% 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/adding-a-person-to-an-area.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.