> 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/command-centre-client/configuring-command-centre/configuring-licensable-features/mobile-client-configuration/mobile-devices-global-settings/access-reader-tab-ngc/add-access-zones.md).

# Add Access Zones

1. Add Access Zones as follows:
   1. Click the **Add Access Zones** button.

      A browse tool displays.

      ![](https://2455150842-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fi6UYAoyykM6nimMN9yss%2Fuploads%2Fgit-blob-9fe180e829c073bef378ed2d0721791b615a987d%2Fmobileclient_addaccesszonepopup.png?alt=media)
   2. Select the Access Zone(s) you want, and click the **Add Selection** button.

      The browse tool closes, and the selected Access Zone(s) appear in the grid. These Access Zone(s) will now be available for selection in the 'Search' feature within the Access Reader Application.
2. A Cardholder granted into an Access Zone may need to trigger a personalised action, (e.g. opening a boom gate when a Cardholder is granted entry to a compound). Therefore, Mobile Access Zones can have doors and macros assigned to them, which trigger once access is granted.

   Assign an 'Access Action' for a Zone as follows:

   1. Select (highlight) the Access Zone in the grid.

      A **Select Item** button appears in the "Grant Access Action" column.
   2. Click the **Select Item** button.

      A browse tool displays.

      ![](https://2455150842-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fi6UYAoyykM6nimMN9yss%2Fuploads%2Fgit-blob-ca4a04a15b39f3f52d4b0329052cecfae950a3f4%2Fmobileclient_grantaccessaction.png?alt=media)
   3. Click the radio button next to the access action you require, and click the **OK** button.

      The browse tool closes, and the **Select Item** button changes to the name of the access action you selected.


---

# 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/command-centre-client/configuring-command-centre/configuring-licensable-features/mobile-client-configuration/mobile-devices-global-settings/access-reader-tab-ngc/add-access-zones.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.
