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

# Interlocking Doors

### Introduction

Interlocking doors are defined as a means of ensuring that only specified doors can be opened at any one time for any set group of doors. Any pair of doors that form part of an Interlock Group will be allowed to be interlocked, meaning that one cannot be unlocked unless the other is secure and vice versa for all groups the doors, etc appear in. Interlock Groups can consist of doors, inputs, outputs, logic blocks, or a combination of these items, with a limit of a combined total of 20.

All tampers to doors, inputs, outputs or logic blocks that are part of an Interlock Group are treated as Open/Insecure by the Interlock Group, which then affects the activity of other items in the group.

### Interlock Rules

The system enforces the Interlock rules when a cardholder badges their card at a reader, or a door is remote released. The only exceptions are:

* If a suitably authorised operator performed an Interlock Group override for the Interlock Group.

  **Note:**

  An operator requires the “Override – Open Door” operator privilege to perform this.
* If a door is excluded from the Interlock Group.
* If an Access Zone a door belongs to goes into free access.
* If an Emergency Release is triggered then all doors in an Interlock Group are released as any other door.

  **Note:**

  Overriding Interlock Groups, (e.g. "Disable Group" in the case of an emergency), can be run from a macro. See [Creating a new Macro](https://help.security.gallagher.com/knowledge-hub/configuration-client/site-installation/macros/creating-a-new-macro.md) for further detail.

### Interlock Breach

When the interlock rules are broken for at least one door/input in an Interlock Group, an Interlock Breach event is generated, which in turn generates an alarm by default. To help determine what has caused an interlock breach an operator can look in the following places:

* The **Status and Overrides** tab of the Interlock Groups properties will show which doors are in breach.
* The Event log or Alarm Viewer window. If there is a "Forced Door" or "Emergency Release of door" event/alarm immediately prior to the interlock breach then that is likely to be the cause of the breach.
* The Status Viewer or Site Plan with the interlocked doors and Access Zones displayed. This would show which door has been forced or emergency released, or which Access Zone has been overridden to free access, causing the interlock breach.

A Door that cannot be opened due to a breach will still give you an access granted indication but it will not let you through.

**Note:** For historical interlock breach information, an operator needs to run an Activity Report.

### Recommendations

The following recommendations apply to interlocking doors:

* A door that is in an Interlock Group should not be put in any Access Zones with doors that are not part of that Interlock Group, and that may go in to free access.
* Where possible, all doors in an Interlock Group should be connected to the same Controller. This is recommended for system stability, (e.g. if the network failed and there are doors on more than one Controller in a single Interlock Group, and doors are forced, Breach Alarms will not be detected).

If putting doors that are on different Controllers in a single Interlock Group cannot be avoided, it is recommended that you configure Inter-Controller offline monitoring for those Controllers. See [Configuring Inter-Controller Offline Monitoring](https://help.security.gallagher.com/knowledge-hub/configuration-client/site-installation/hardware/creating-controllers/configuring-offline-monitoring.md) for further detail.

* Doors in Interlock Groups should not be set up with a free handle pushbutton exit, as this defeats the purpose of an Interlock Group and doesn't really work, (i.e. if a door is not in an Interlock Group and a free handle pushbutton is toggled, it does not fire any output. However, if it is in an Interlock Group it fires the unlock output).

Select the item below that you require further detail on:

![](https://3000903572-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FfCvaxj3suxNBzdwQndVT%2Fuploads%2Fgit-blob-f30c70c9dfd07493527af00bd979539606de5d30%2Ftopiclink.png?alt=media) [Adding a new Interlock Group](https://help.security.gallagher.com/knowledge-hub/configuration-client/site-installation/doors/interlocking-doors/adding-a-new-interlock-group.md)


---

# 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.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.
