> 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/enabling-zone-counting.md).

# Enabling Zone Counting

### Introduction

Zone Counting enables sites to keep a continuous count of the number of cardholders in an Access Zone, or [*Access Zone*](https://help.security.gallagher.com/knowledge-hub/configuration-client/glossary-of-terms.md#access-zone-group)[*Group*](https://help.security.gallagher.com/knowledge-hub/configuration-client/glossary-of-terms.md#access-zone-group). "No-alone zones", which are sometimes required for security or safety reasons, use zone counting in conjunction with dual authorisation.

**Notes:**

* A [*count zone*](https://help.security.gallagher.com/knowledge-hub/configuration-client/glossary-of-terms.md#count-zone) may span multiple Controllers, however this may reduce the accuracy of the count.
* If a door is configured for auto-forgive (on an Access Zones **Anti-passback** tab) and zone counting is also configured for the same Access Zone, then if a cardholder exits via that door, the zone count will not be updated.
* Dual Authorisation is not supported for Elevator use.
* If the Controller is restarted, zone counting will be persisted.

***

### Configuration

To enable zone counting for an Access Zone, perform the following procedures in Gallagher Configuration Client:

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 you want to configure zone counting for.

   **Note:**

   If the Access Zone is a member of an Access Zone Group, zone counting needs to be defined on the Master Zone for the group. If this is the case, you will need to open the properties of the Master Zone, and the zone counting properties configured for the Master Zone will apply to all Access Zones in the group.
3. **Right click** and select **Properties**.
4. Click the **Advanced** tab.
5. Check the **Zone Counting enabled** checkbox.

   The **No-alone zone** checkbox becomes enabled and three new tabs appear, (i.e. **Zone Counting**, **Zone Count Inputs** and **Zone Count Outputs** ).

   ![](https://3000903572-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FfCvaxj3suxNBzdwQndVT%2Fuploads%2Fgit-blob-a33254d0e41280dbdbc91db395f33897fbed80bd%2Faczone_enablingzc.png?alt=media)
6. Check the **No-alone zone** checkbox if cardholders are not allowed to be in this zone alone.

   If this is to be a 'No-alone Zone', see [Configuring No-alone Zones](https://help.security.gallagher.com/knowledge-hub/configuration-client/site-installation/access-zones/configuring-no-alone-zones.md) for complete procedure.
7. Select a **Controller** from the drop-down list.

   **Note:**

   There are no specific rules for selecting a Controller, but for optimum performance you should select the Controller that manages the largest part of the system, (i.e. the one that has the most doors).
8. Click each of the new tabs in turn and configure as required:

<details>

<summary>Zone Counting tab</summary>

1. Click the **Zone Counting** tab.

   ![](https://3000903572-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FfCvaxj3suxNBzdwQndVT%2Fuploads%2Fgit-blob-25e5273d669336ea6ccbaeb43bc236c4c5f20b03%2Faczone_zc2.png?alt=media)
2. Configure zone counting as required.

   <table><thead><tr><th width="174">Option</th><th>Description</th></tr></thead><tbody><tr><td>Thresholds</td><td>Sets the minimum and maximum threshold for the count zone. The two threshold values define three ranges: low, medium and high, which mean respectively, below-minimum, mid-range and above-maximum.</td></tr><tr><td>Grace Time</td><td>This is the period that must elapse before generating an event because the zone count has reached a threshold value or zero.<br><br><strong>Note:</strong><br>This allows short transition periods for people to change places between zones, (e.g. with dual-authorisation when a zone must have a minimum of two people, but zero is OK, we cannot expect two cardholders to enter or leave simultaneously). This gives time for two people to leave or enter without generating an alarm.</td></tr><tr><td>Event Messages</td><td>Allows messages to be defined for display in event or alarm, (e.g. "Carpark full").</td></tr><tr><td>Zero is Mid-range</td><td>Ticking this checkbox will mean that the zone count of zero will be treated in the same way as mid-range.</td></tr><tr><td>When last person exits alarms are Armed</td><td>Ticking this checkbox will mean that when the last person leaves the Access Zone the alarms will be armed.<br></td></tr></tbody></table>

</details>

<details>

<summary>Zone Count Inputs tab</summary>

1. Click the **Zone Count Inputs** tab.

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

   Inputs, outputs and/or logic blocks can be configured to increment and/or decrement the zone count for this Access Zone.

   **Examples of when this could be used:**

   1. When a sensor is used to count people passing by, (i.e. the zone count is not actually associated with access control, just counting people in or out of an area).
   2. In a multi-tenanted car park, when an owner wants to restrict entry to a particular tenant once they have used all the car parks allocated to them. In this case, the input will in fact be a virtual output that is triggered when a particular tenant leaves the car park. Refer to [Logic Blocks and Virtual Outputs](https://help.security.gallagher.com/knowledge-hub/configuration-client/site-installation/logic-blocks-and-virtual-outputs.md) for further detail regarding virtual outputs.
2. From the **Hardware** List Window, select the input(s) and/or output(s) to be used for incrementing the zone count.

   **Note:** The number of inputs, outputs and logic blocks that can be configured to increment the zone count is unlimited.
3. Drag and drop them into the 'Increment Inputs' grid on the **Zone Count Inputs** tab.

   **Note:** If an input is not inverted (via the **Advanced** tab of the input's properties), then when the input transitions from closed to open the zone count for this Access Zone is incremented.

   If an input is inverted, then the reverse occurs, (i.e. when the input transitions from open to closed the zone count is incremented).
4. Repeat Steps 2 and 3 for the input(s) to be used for decrementing the zone count.

   **Notes:**

   * The number of inputs, outputs and logic blocks that can be configured to decrement the zone count is unlimited.
   * If an input is not inverted (via the **Advanced** tab of the input's properties), then when the input transitions from closed to open the zone count for this Access Zone is decremented.

     If an input is inverted, then the reverse occurs, (i.e. when the input transitions from open to closed the zone count is decremented).

</details>

<details>

<summary>Zone Count Outputs tab</summary>

1. 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)

   This tab allows at least four relays per zone count range to be configured to reflect the zone count state being in each of the three ranges and/or zero. The relays will reflect when the zone count reaches the following values:

   <table><thead><tr><th width="144">Value</th><th>Description</th></tr></thead><tbody><tr><td>Above maximum:</td><td>This relay will be on when the zone count exceeds the maximum threshold value, otherwise it will be off.</td></tr><tr><td>Mid-range:</td><td>This relay will be on when the zone count is not greater than the maximum threshold value and not less than the minimum threshold value.</td></tr><tr><td>Below minimum:</td><td>This relay will be on when the zone count is less than the minimum threshold value, otherwise it will be off.</td></tr><tr><td>Zero:</td><td>This relay will be on when the zone count is zero, otherwise it will be off. This relay will never be on by itself because either the 'Mid-range' or the 'Below Minimum' relay will also be on depending on the 'Zero is Mid-range' setting on the <strong>Zone Counting</strong> tab, (i.e. if 'Zero is Mid-range' is checked, then the Mid-range and Zero relays will be on together, otherwise it will be the Zero and Below minimum relays that are on together).</td></tr></tbody></table>

   **Notes:**

   * All relays can be set up to operate in reverse, the same as any other relay.
   * The output will not necessarily reflect the correct state immediately after being configured, but it will after the next zone count state change.

     It is possible to force a state change by manually setting the zone count to a different threshold. See [Manually Resetting Zone Counts](https://help.security.gallagher.com/knowledge-hub/configuration-client/site-installation/access-zones/manually-resetting-zone-counts.md) for the procedure.
2. Drag and drop the outputs to use for reflecting the zone count states.

</details>

9. Click **OK** to exit and save your changes.

   Click **Cancel** to exit without saving your changes.

   Click **Apply** to save your changes and stay in this window.

### Result

Zone counting has been enabled for the Access Zone, or Access Zone Group.


---

# 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/enabling-zone-counting.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.
