> 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/doors/interlocking-doors/adding-a-new-interlock-group.md).

# Adding a new Interlock Group

### Introduction

From the **Interlock Group** List Window, operators with the “Edit Site” operator privilege can add a new Interlock Group.

### Procedure

1. Click **Configure** from the menu bar, then **Interlock Groups**.

   The **Interlock Group** 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. **Right click** and select **New\...Interlock Group**.

   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).
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).
5. Click the **Alarm Instructions** tab, and configure as required.

   For further detail see [Alarm Instructions tab](https://help.security.gallagher.com/knowledge-hub/configuration-client/introduction-to-command-centre/knowing-your-way-around/generic-properties-configuration/alarm-instructions-tab.md).
6. Click the **Connections** tab.

   ![](https://3000903572-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FfCvaxj3suxNBzdwQndVT%2Fuploads%2Fgit-blob-3a68084ec51fe448ee8723158518ee891919806e%2Finterlockgrp_connectionstab.png?alt=media)
7. Select the appropriate **Controller** from the drop-down list to host the Interlock Group. The Interlock Group will not function until a Controller is selected.

   **Note:**

   Select the Controller with the majority of Door hardware assigned to it. It is preferable to have all Door hardware on the same Controller.
8. Click the **Interlocks** tab.

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

   This screen allows you to create relationships between doors within the Interlock Group, and specify which doors in the group interlock with each other.

   **Note:** Inputs, Outputs and/or Logic Blocks may also be used wherever doors are mentioned.

   Complete the fields on this screen as appropriate.

   <table><thead><tr><th width="192">Field</th><th>Description</th></tr></thead><tbody><tr><td><strong>Interlocked Items</strong> grid</td><td><p>Drag the doors into the <strong>Interlocked Items</strong> grid that you want to belong to this Interlock Group.<br><br><strong>Notes:</strong></p><ul><li>The list can consist of doors, inputs, outputs, logic blocks or a combination of these items, with a limit of a combined total of 20. If you attempt to add more than 20, an error message will display.</li><li>The icons in this grid reflect the current status of the doors/inputs/outputs/logic blocks.</li></ul></td></tr><tr><td><strong>Warning Output</strong> drop-down list</td><td><p>Each door can have an output assigned to it that is on when the door is prevented from being opened due to the interlocking rules.<br>There are two ways of doing this. Either:</p><ul><li>Drag the output into the <strong>Interlocked Items</strong> grid beside the appropriate door,</li></ul><p>OR</p><ul><li>In the <strong>Interlocked Items</strong> grid, highlight the door you want to assign an output for, and select an output from the <strong>Warning Output</strong> drop-down list.</li></ul><p>The output displays in the <strong>Interlocked Items</strong> grid beside the door.</p></td></tr><tr><td><strong>Exclude selected</strong> checkbox</td><td>Allows a door to be excluded from the Interlock Group (usually as a temporary measure). For situations where a door is damaged, or for some reason needs to be opened independently of the interlock, but will become part of the group again at a later date.<br>To exclude a door, highlight it in the <strong>Interlocked Items</strong> grid and tick the <strong>Exclude selected</strong> checkbox.<br>The door will still be listed in the <strong>Interlocked Items</strong> grid with “Yes” in the ‘Excluded’ column.</td></tr><tr><td><strong>Interlocking rules</strong> radio buttons</td><td>Clicking the appropriate radio button allows you to change the interlocking rule depending on what you want to configure.<br>When <strong>Interlock</strong> is selected, all doors listed as part of the group will be interlocked, (i.e. only one of the listed doors may be open/unlocked at any one time without causing a breach).<br>When <strong>Not Interlocked</strong> is selected, none of the doors listed as part of the group shall be interlocked.</td></tr><tr><td><strong>Interlock Exceptions</strong> grid</td><td><p>Drag the doors as pairs into the <strong>Interlock Exceptions</strong> grid that you want to be exceptions to the Interlock rule.<br>If a door is dragged over an existing row with only one door, the dragged door is added to that row, unless it is the same as the first door.<br>If the row dragged over already has two doors, then there will be no effect, (i.e. once an exception pair has two doors the pair cannot be modified, and to change it you need to delete the row and recreate it).<br><br><strong>Notes:</strong></p><ul><li>The list can consist of 40 exception pairs. If you attempt to add more than 40, an error message will display.</li><li>The icons in this grid never change state.</li></ul></td></tr></tbody></table>
9. Click the **Cameras** tab if you want to associate a DVR Camera(s) with this Interlock Group.

   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).
10. Click the **Icons** tab if you want to change the Icon Set for this Interlock Group.

    For further details regarding the **Icons** tab, see [Icons](https://help.security.gallagher.com/knowledge-hub/configuration-client/site-installation/server-properties/icons.md).
11. Click the **Notes** tab if you want to add a note(s) about this Interlock Group.

    For further details regarding the **Notes** tab, see [Notes](https://help.security.gallagher.com/knowledge-hub/configuration-client/site-installation/server-properties/notes.md).
12. 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 Interlock Group has been created and displays in the **Interlock Group** List Window.

### Hint

{% hint style="info" %}
**Editing and Deleting Interlock Groups**

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 Interlock Groups.

**Note:** If you attempt to delete an Interlock Group that is linked to a macro or appears on a Site Plan, a message will display, for example:

*"This item cannot be deleted as there is a macro that depends upon it for proper operation."*

OR

*"This item cannot be deleted, as it currently appears on a site plan."*
{% endhint %}


---

# 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/doors/interlocking-doors/adding-a-new-interlock-group.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.
