> 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/adding-a-new-access-zone.md).

# Adding a new Access Zone

### Introduction

Details about the different Access Zones the cardholders can access must be set up within Command Centre.

Ensure the following components have already been set up:

*Divisions*

Refer to "[Setting up System Division](https://help.security.gallagher.com/knowledge-hub/configuration-client/site-installation/system-division/setting-up-system-divisions.md)".

*Schedules*

Refer to "[Schedule](https://help.security.gallagher.com/knowledge-hub/configuration-client/site-installation/schedules.md)".

***

### Considerations

Access Zones (and hence their attached Access Zone Schedule) are one of the three elements of setting up Access Groups.

***

### Configuration

To configure 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. **Right click** and select **New\...Access Zone**.

   By default the **General** tab displays.
3. Complete the fields as required.

   For further detail see [General tab](https://help.security.gallagher.com/knowledge-hub/configuration-client/introduction-to-command-centre/knowing-your-way-around/generic-properties-configuration/general-tab.md).

   **Note:**

   In a multi-level building, it is useful to include the number of the floor level in the access zone name and/or description. This is so an operator can quickly identify the floor an access zone is on.
4. Click the **Event Response** tab, and configure as required.

   For further detail see [Event Response tab](https://help.security.gallagher.com/knowledge-hub/configuration-client/introduction-to-command-centre/knowing-your-way-around/generic-properties-configuration/event-response-tab.md).

   **Notes:**

   * Only assign Alarm Zones to Access Zones if there is alarm functionality in that zone, (e.g. PIR). Otherwise, leave the "Alarm Zone for all Events" in the default setting of --None Selected--.
   * If the Access Zone is required to unset an Alarm Zone this is where this relationship should be defined. This is often the case when the Access Zone and Alarm Zone cover the same geographical area.

     The Alarm Zone may contain a movement detector, or a safe reed switch, etc.

     If a cardholder badges to enter this Access Zone and the Alarm Zone is armed then the cardholder must have the "Change to the Disarmed state" Access Group privilege before being allowed into the Access Zone. This prevents cardholders from entering the Access Zone when the Alarm Zone is armed. Cardholders are then able to arm the Alarm Zone associated with this Access Zone, as they leave the Access Zone by performing a local override at a reader.
5. Click each tab in turn and configure the Access Zone properties as required:

<details>

<summary>Access Mode tab</summary>

One property of an Access Zone is the access mode. The access mode defines the method of access to the zone, (i.e. how the doors in this specific zone behave).

1. Click the **Access Mode** tab.

   ![](https://3000903572-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FfCvaxj3suxNBzdwQndVT%2Fuploads%2Fgit-blob-00b126aacdbbd188ecbc4c395a15e293894694ce%2Faczone_amode.png?alt=media)
2. Click within the **Schedule** field.
3. A drop-down menu displays all the Access Zone Schedule types you are allowed to see. Select the Access Zone Schedule that is to apply to this Access Zone.

   **Note:** Clicking the **View Schedule** button opens the **View Calendar** tab of the selected Schedule.
4. First Card unlock mode allows an Access Zone to remain in a SECURE state until a member of a selected access group is granted access on or after the scheduled FREE state change.

   Configure the **First Card Unlock** options as required.

   <table><thead><tr><th width="240">Checkbox</th><th>Description</th></tr></thead><tbody><tr><td>Scheduled 'Free' state is secure until privileged cardholder is granted access</td><td>When checked the operator has the ability to select the secure access mode the 'free' will be until a cardholder with the required privileges is granted access.<br><br><strong>Note:</strong> Checking this option enables the PIN Required option.</td></tr><tr><td>PIN Required</td><td>The Operator has the ability to additionally enforce that a PIN be required when the First Card Unlock mode is in force.</td></tr></tbody></table>
5. The 'Cardholder Overrides' area of this screen determines what happens when a cardholder overrides the access mode for the zone. Otherwise the access mode is determined by the Schedule. It relates to Access Groups with the "Lock and unlock access zones" privilege. This privilege enables members to override the access mode, (e.g. from secure to free), by performing a local override at a reader. (For further details refer to "[Configuring Local Overrides at Card Readers](https://help.security.gallagher.com/knowledge-hub/configuration-client/site-monitoring/status-and-overrides/configuring-local-overrides-at-card-readers.md).)

   **Note:** The default Action Plan for **Access Zone State Change** events is "Log an event". It is possible however to change the default to "No event recorded", which can be configured from either the Server Properties ( **Event Defaults** tab), the Door properties ( **Event Response** tab), or the Alarm Zone properties ( **Event Defaults** tab).
6. Specify the methods of access to this zone, when the access mode is overridden to Mode 1 or Mode 2.

   **Notes:**

   * The 'Display Name' is viewed on the HBUS Terminal only. The 'Display Name' enables you to describe the access mode, (e.g. After Hours). If using an HBUS Terminal, enter the Display Name for each access mode.
   * If the access mode is "Code or Card", you need to enter an appropriate four digit number in the 'Code only code' field on this screen. This means anyone will be able to gain access through a door by entering the four digit code and then pressing the **IN/Enter** button on the reader.

</details>

<details>

<summary>Dual Authorisation tab</summary>

Dual Authorisation is an access mode that requires two different valid credentials to be presented at an Access Zone's entry reader(s), in order to be granted access.

### Examples:

* Two separate authorised Cardholders must present a valid credential at the reader to open the door.
* One authorised Cardholder must present two separate valid credentials at the reader to open the door.

If required, perform the following procedure to configure Dual Authorisation for this Access Zone:

**Notes:**

* Dual Authorisation is not supported for Elevator use.
* Dual Authorisation functionality is not enabled unless the Access Zone is in either of the 'Dual Auth - No PIN' or 'Dual Auth - PIN' access modes. An Access Zone can be put into a Dual Auth access mode using Access Zone Schedules or Overrides.

1. Click the **Dual Authorisation** tab.

   ![](https://3000903572-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FfCvaxj3suxNBzdwQndVT%2Fuploads%2Fgit-blob-2db8beea3b848bfceee38d61673408d919876e54%2Faz_dualauth.png?alt=media)
2. Configure the Dual Authorisation tab as required.

   <table><thead><tr><th width="198">Field</th><th>Description</th></tr></thead><tbody><tr><td>1st Card Access Group</td><td><p>From the <strong>1st Card Access Group</strong> drop-down list:</p><ul><li>select the Access Group that the 1st credential must belong to, or</li><li>select <em>-- Any Group --</em> to let the 1st credential belong to any valid Access Group.</li></ul></td></tr><tr><td>1st Card Type</td><td><p>From the <strong>1st Card Type</strong> drop-down list:</p><ul><li>select the Card Type, Mobile Credential Type, or Morpho Biometric Type that the 1st credential must be, or</li><li>select <em>-- Any Card Type --</em> to let the 1st credential be any valid Card Type.</li></ul></td></tr><tr><td>2nd Card Access Group</td><td><p>From the <strong>2nd Card Access Group</strong> drop-down list:</p><ul><li>select the Access Group that the 2nd credential must belong to, or</li><li>select <em>-- Any Group --</em> to let the 2nd credential belong to any valid Access Group.</li></ul></td></tr><tr><td>2nd Card Type</td><td><p>From the <strong>2nd Card Type</strong> drop-down list:</p><ul><li>select the Card Type, Mobile Credential Type, or Morpho Biometric Type that the 2nd credential must be, or</li><li>select <em>-- Any Card Type --</em> to let the 2nd credential be any valid Card Type.</li></ul><p><strong>Note:</strong> The <strong>2nd Card Type</strong> can be the same as the <strong>1st Card Type</strong> if required.</p></td></tr><tr><td>Dual Authorisation Mode</td><td><p>Select the required <strong>Dual Authorisation Mode</strong>:</p><ul><li><strong>Not Enforced</strong><br>The first and second credential badges can come from the same Cardholder or different Cardholders. The zone count will increase by 1 if both credentials belong to the same Cardholder. The zone count will increase by 2 if the credentials belong to different Cardholders.</li><li><strong>Different Cardholders</strong><br>In this mode, the first and second credentials must belong to different Cardholders. The zone count will increase by 2.</li><li><strong>Same Cardholder</strong><br>In this mode, the first and second credentials must belong to the same Cardholder. The zone count will increase by 1.</li></ul><p><strong>Note:</strong> While one Cardholder can perform both badges (depending on which option you select), the Cardholder must badge two different credentials; not the same one twice.</p></td></tr></tbody></table>

</details>

<details>

<summary>Advanced tab</summary>

If you want this Access Zone to be a member of an [*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), perform the following procedure:

1. Click the **Advanced** tab.

   ![](https://3000903572-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FfCvaxj3suxNBzdwQndVT%2Fuploads%2Fgit-blob-a9544e401e969fee6df1a671798f3e69c85aded4%2Faczone_advanced.png?alt=media)
2. Click within the **Master Zone** field and select the appropriate Access Zone from the drop-down list.

   The Anti-passback and Zone Counting sections disappear from this tab, as these properties will be defined on the Master Zone.

   ![](https://3000903572-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FfCvaxj3suxNBzdwQndVT%2Fuploads%2Fgit-blob-3cd8c03f6c9f46137efe79a29bbd3409db04c800%2Faz_masterzone.png?alt=media)
3. Configure [*anti-passback*](https://help.security.gallagher.com/knowledge-hub/configuration-client/glossary-of-terms.md#anti-passback) for this Access Zone if required. (See [Configuring Anti-passback](https://help.security.gallagher.com/knowledge-hub/configuration-client/site-installation/access-zones/anti-passback/configuring-anti-passback.md) for procedure.)
4. Configure Zone Counting for this Access Zone if required. (See [Enabling Zone Counting](https://help.security.gallagher.com/knowledge-hub/configuration-client/site-installation/access-zones/enabling-zone-counting.md) for procedure.)

</details>

<details>

<summary>Alarm Zones tab</summary>

If you want configure the Alarm Zones to be armed/disarmed upon access or prevent access if the Alarm Zones are disarmed or outputs are on, perform the following procedure:

1. Click the **Alarm Zones** tab.

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

   In this tab you can add Access Groups, then for each Access Group you can:

   * Specify Alarm Zone(s) to be armed/disarmed when access is granted (in the top grid). The Alarm Zones will be armed when a Cardholder batches twice and disarmed upon access.
   * Specify Alarm Zone(s), and/or Output(s) that will result in denial of access if the Alarm Zone is disarmed, or the output is on (in the bottom grid).

   **Notes:**

   * This feature uses the Access Group privileges to arm/disarm the Alarm Zones. Therefore, to enable the Cardholders to arm/disarm the Alarm Zones specified here, the Alarm Zones must be assigned to the Cardholders’ Access Group.
   * If any Alarm Zone or Output specified in the bottom grid is offline, then the Cardholders will be denied access, and an offline event will be raised.
2. Click **Manage** from the menu bar, then **Access Groups**.

   The Access Group List Window opens.

   Select the appropriate Access Group(s), and drag and drop them into the **Access Groups** grid.
3. Click on the appropriate Access Group to select it.

   The Alarm Zone grid is displayed.
4. Click **Configure** from the menu bar, then **Alarm Zones**.

   The Alarm Zone List Window opens.

   Select the required Alarm Zones, and drag and drop them into the appropriate **Alarm Zones** grids as follows:

   * Top grid, to arm (via double badge) and disarm upon access.
   * Bottom grid, to prevent access if the Alarm Zones are disarmed or outputs are on.
5. Open the **Hardware** List Window, and drag and drop the Output(s) required into the **Alarm Zones** bottom grid.

</details>

<details>

<summary>Triggered Overrides tab</summary>

This tab allows you to configure pushbutton overrrides or lockdown functionality for this Access Zone. (See [Configuring Pushbutton Overrides](https://help.security.gallagher.com/knowledge-hub/configuration-client/site-installation/access-zones/configuring-pushbutton-overrides.md) or [Setting a Lockdown Source](https://help.security.gallagher.com/knowledge-hub/configuration-client/site-installation/access-zones/access-zone-lockdown/setting-a-lockdown-source.md) for procedure.)

**Note:** You can configure EITHER pushbutton overrides OR lockdown functionality for an Access Zone, (i.e. you cannot use both features for the one zone).

</details>

<details>

<summary>Personalised Actions tab</summary>

This tab allows you to configure cardholder specific actions for this Access Zone.

See [Configuring Personalised Actions for Access Zones](https://help.security.gallagher.com/knowledge-hub/configuration-client/site-installation/access-zones/configuring-personalised-actions-for-access-zones.md) for the procedure.

</details>

6. Click the **Cameras** tab if you want to associate a DVR Camera(s) with this Access Zone.

   For further details see [Cameras tab](https://help.security.gallagher.com/knowledge-hub/configuration-client/introduction-to-command-centre/knowing-your-way-around/generic-properties-configuration/cameras-tab.md).
7. Click the **Icons** tab if you want to change the Icon Set for this Access Zone.

   For further details regarding the **Icons** tab, see [Icons](https://help.security.gallagher.com/knowledge-hub/configuration-client/site-installation/server-properties/icons.md).
8. Click the **Custom Fields** tab if you want to add and assign a custom field value to this Access Zone.

   For further details regarding the **Custom Fields** tab, see [Custom Fields](https://help.security.gallagher.com/knowledge-hub/configuration-client/site-installation/server-properties/custom-fields.md).
9. Click the **Notes** tab if you want to add a note(s) about this Access Zone.

   For further details regarding the **Notes** tab, see [Notes](https://help.security.gallagher.com/knowledge-hub/configuration-client/site-installation/server-properties/notes.md).
10. 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

A new Access Zone is added to the Command Centre system.

All access controlled doors within the selected zone will all behave in the same manner. When cardholders attempt access to the zone the doors will all require the same method of access.

***

### Editing and Deleting Access Zones

Refer to [Editing items](https://help.security.gallagher.com/knowledge-hub/configuration-client/introduction-to-command-centre/knowing-your-way-around/generic-properties-configuration/editing-items.md) and [Deleting items](https://help.security.gallagher.com/knowledge-hub/configuration-client/introduction-to-command-centre/knowing-your-way-around/generic-properties-configuration/deleting-items.md) for procedures on how to edit and delete Access Zones.

**Note:** You cannot delete any Access Zones that are currently assigned to doors, elevator cars or macros, or are configured on a Tag Board Tile in Command Centre Client. Likewise, if you attempt to delete an Access Zone that is a 'Master Zone', (i.e. it has other Access Zones associated with it), the following error message will display:

*"This Access Zone cannot be deleted, as it still contains another Access 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/adding-a-new-access-zone.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.
