> 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/site-installation/access-zones/understanding-access-zones.md).

# Understanding Access Zones

The following example provides further detail regarding nested access zones.

A store room may have an access-controlled door connecting it to the rest of the building. There is no other way in or out of the store room. There are times during which the store room door should be locked, regardless of the state of the main building, however at other times this is not required, as long as the main building is secure. If the store room door were to be configured with the entry zone being the store room and the exit zone being the main building, then the store room door would always be locked whenever the main building is in secure access mode. To achieve the effect that the store room door can be unlocked when the main building is secure, the store room door should have its exit zone set to "None Selected". This will mean that the door is only locked when the store room is in secure access mode, regardless of the state of the main building.

![](https://3000903572-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FfCvaxj3suxNBzdwQndVT%2Fuploads%2Fgit-blob-9605dd7a69f5666d869b7389e021175e9796a21a%2Fazdiagram.png?alt=media)

There is nothing to be gained by configuring an exit zone on a door that has an entry reader, but no exit reader, unless you really want the door to be locked whenever the exit zone is secure. This is because the main purpose of the access zone is to determine how card access attempts are processed and for tracking purposes (which only works when access cards are used). Avoiding unnecessary assignment of exit zones will often avoid the above problem because the store room probably doesn't have an exit reader.


---

# 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/site-installation/access-zones/understanding-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.
