> 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/configuring-no-alone-zones.md).

# Configuring No-Alone Zones

### Introduction

Access Zones can be configured to prevent a single Cardholder being alone in a Zone. Command Centre counts the number of Cardholders in a Zone and sets the access mode to Dual Authorisation when the Zone is empty (i.e. two Cardholders are required to access the Zone). When there are only two Cardholders in the Zone, dual authorisation is required to exit the Zone.

This feature also allows multiple No-Alone Zones to be configured adjacent to each other. Whenever access is requested into a No-Alone Zone, Command Centre will check the count of Cardholders in each Zone to ensure no Cardholder is alone.

If all three remaining Cardholders in a No-Alone Zone need to move to an adjacent and empty No-Alone Zone, the third Cardholder will be given a configured grace period to leave the Zone before an alarm is raised. If the third Cardholder does not leave within the grace period, the exit access Zone will change to dual authorisation (i.e. the Cardholder will not be able to exit).

This procedure describes how to configure an Access Zone as a 'No-Alone Zone'.

**Notes:**

* 'No-alone zone' is not functional for Access Zone Groups, (i.e. an Access Zone that is already a Master Zone cannot then be configured as a 'No-alone zone'. Likewise, you cannot select an already configured 'No-alone zone' as a Master Zone).
* The minimum Zone count should be set to two for this feature to function as described.

***

### Recommendations

* The 'No-alone Zone' feature is not recommended for turnstiles or pushbutton release, and cannot be used for elevator control.
* The situation may arise where an individual cardholder is trapped in a 'No-alone Zone' on their own, and is therefore unable to leave. It is recommended that a panic button be installed so operators can be alerted if this occurs.
* It is recommended that your site has procedures in place for correcting the zone count when events occur that may render the zone count inaccurate, (i.e. override Access Zones to free, open door override or emergency release).
* It is recommended that your site has procedures in place so tailgating is not allowed when physically exiting a 'No-alone Zone'.

***

### Configuration

To configure an Access Zone as a 'No-Alone Zone', perform the following procedures in Gallagher Configuration Client:

<details>

<summary>Door Set-up</summary>

This part of the procedure needs to be repeated for each Door.

1. Click **Configure** from the menu bar, then **Doors**.

   The **Door** List Window opens (in [grid view](https://help.security.gallagher.com/knowledge-hub/configuration-client/introduction-to-command-centre/knowing-your-way-around/list-windows/grid-view.md)).
2. Open the properties of the Door.
3. Click the **Devices** tab and select Inputs for the open sensor, lock sensor and an Output for the unlock output, as required.
4. Click the **Entry Zone** tab and select an Entry Access Zone and an Entry Reader.
5. Click the **Exit Zone** tab and select an Exit Access Zone and an Exit Reader.
6. Click **OK** to exit and save your changes.
7. Repeat Steps 2-6 for each Door.

</details>

<details>

<summary>Entry Access Zone Set-up</summary>

This part of the procedure needs to be repeated for each Access Zone you want to configure as a 'No-alone Zone' Entry Access Zone.

1. Click **Configure** from the menu bar, then **Access Zones**.

   The **Access Zone** List Window opens (in [tree view](https://help.security.gallagher.com/knowledge-hub/configuration-client/introduction-to-command-centre/knowing-your-way-around/list-windows/tree-view.md)).
2. Highlight the Access Zone to be configured as a 'No-alone Zone'.
3. **Right click** and select **Properties**.
4. Click the **Access Mode** tab.

   ![](https://3000903572-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FfCvaxj3suxNBzdwQndVT%2Fuploads%2Fgit-blob-58b83f66766678ba1d9a8be094f8b409287e2026%2Faczone_amode2.png?alt=media)
5. From the **Schedule** drop-down list, select an appropriate Schedule for the hours you require 'No-alone Zone' to be enabled for.

   Ideally a 24 hour dual-authorisation Schedule should be used.

   **Note:** Dual Authorisation is not supported for Elevator use.
6. In the 'Cardholder Overrides' section change the Mode 2 Access mode to Secure.
7. Click the **Advanced** tab.
8. Check the **Zone Counting enabled** checkbox.

   The **No-alone zone** checkbox and the **Controller** drop-down list become enabled, and two new tabs appear, (i.e. **Zone Counting** and **Zone Count Outputs** ).

   ![](https://3000903572-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FfCvaxj3suxNBzdwQndVT%2Fuploads%2Fgit-blob-10c3b680e96f1a779751d8d4d892cb1654b54687%2Faczone_zc.png?alt=media)
9. Check the **No-alone zone** checkbox.
10. Select a **Controller** from the drop-down list.
11. Click the **Zone Count Outputs** tab.

    ![](https://3000903572-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FfCvaxj3suxNBzdwQndVT%2Fuploads%2Fgit-blob-7c94268f85da5c8e743acf76de228e29b5d88dfb%2Faczone_zc3.png?alt=media)
12. Drag (or copy and paste) the required outputs to use for reflecting the zone count states.
13. Click **OK** to exit and save your changes.

    **Note:**

    The 'Save' will fail if **No-alone Zone** has been checked without a Controller being selected. In this case you have to re-enable the checkbox before removing the outputs from the **Zone Count Outputs** tab.
14. Repeat Steps 2-13 for each Access Zone to be configured as a 'No-alone Zone' Entry Access Zone.

</details>

<details>

<summary>Exit Access Zone Set-up</summary>

This part of the procedure needs to be repeated for each Access Zone you want to configure as an Exit Access Zone.

1. Open the properties of the Access Zone you want to configure as an Exit Access Zone.
2. Click the **Access Mode** tab.
3. From the **Schedule** drop-down list, select an appropriate Schedule for the hours you require 'No-alone Zone' to be enabled for.

   Ideally a 24 hour dual-authorisation Schedule should be used.

   **Note:** Dual Authorisation is not supported for Elevator use.
4. In the 'Cardholder Overrides' section change the Mode 2 Access mode to Secure.
5. Click **OK** to exit and save your changes.
6. Repeat Steps 1-5 for each Access Zone to be configured as an Exit Access Zone.

</details>

### Result

An Access Zone has been configured as a 'No-alone Zone'.


---

# 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/configuring-no-alone-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.
