> 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/creating-doors.md).

# Creating Doors

### Introduction

Once Controllers have been configured you can then add "doors". This may seem odd at first, however by adding these logical doors, it makes it simple to attach the actual reader devices.

**Note:**

We recommend that sites do not have sensors, outputs or readers for a single door spanning more than one Controller. This is recommended for performance reasons and so site security is not compromised, (e.g. components spanning Controllers can result in relays switching when they shouldn't, door access being provided when it shouldn't, and alarms being reported unnecessarily).

***

### Configuration

To create a Door, perform the following procedures in Gallagher Configuration Client:

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

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

   **Note:** The default Action Plan for the 'Unit on Door Tampered' Event Type (under the 'Tamper' Group) is **Log an event**. Command Centre will display a 'Unit on Door Tampered' event whose source is a door, when an associated reader or door sensor goes into a tamper state.

   This event can be configured as an alarm here instead so that these alarms will display elsewhere in Command Centre as being against the door, (e.g. if a site only has doors on their Site Plans they will show against the door. Note that if the associated reader or sensor is also on the Site Plan the alarm will show against them as well).

   If your site requires this functionality to be system-wide rather than against specific door(s), this can be configured on the **Event Default** tab of the Server Properties instead.
5. Click each tab in turn and configure the door properties as required:

<details>

<summary>Connections tab</summary>

1. Click the **Connections** tab.

   ![](https://3000903572-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FfCvaxj3suxNBzdwQndVT%2Fuploads%2Fgit-blob-fa8c98737199eba1786573666f651ee409819a90%2Fdoor_connections.png?alt=media)
2. Assign the door to the Controller that will host this door.

   **Notes:**

   * Select the Controller with the majority of Door hardware assigned to it. It is preferable to have all Door hardware on the same Controller.
   * Doors are restricted to a maximum of 10 per controller by default. Additional door capacity can be added through licensing.

</details>

<details>

<summary>Devices tab</summary>

1. Click the **Devices** tab.

   ![](https://3000903572-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FfCvaxj3suxNBzdwQndVT%2Fuploads%2Fgit-blob-aeb7eb7b94a0ba37d7301d6f4154d1026f547cea%2Fdoor_devices.png?alt=media)
2. Assign the appropriate inputs and outputs to configure the Door.

   Inputs should be wired depending on the type of input, as follows:

   <table><thead><tr><th width="186">Input Type</th><th width="160">Wired</th><th>Notes</th></tr></thead><tbody><tr><td>Standard</td><td>Normally Closed</td><td></td></tr><tr><td>Remote Release,<br>Request to Exit (REX)</td><td>Normally Open</td><td>If wired Normally Closed, need to invert it</td></tr></tbody></table>

   <table><thead><tr><th width="162">Field</th><th>Allows the selection of an...</th></tr></thead><tbody><tr><td>Open Sensor</td><td>Input to act as the doors open sensor.</td></tr><tr><td>Lock Sensor</td><td>Input to act as the doors lock sensor.</td></tr><tr><td>Unlock output</td><td>Output to signal the door to unlock.</td></tr><tr><td>Remote release</td><td>Input connected to a push button that grants access to a door, (.e.g a button located behind a reception desk).</td></tr><tr><td>Emergency release</td><td>Input that will be connected via a relay to the Free Access Input. Opening the Input results in the Door being manually overridden to Free Access Mode (in the case of an emergency evacuation), and closing the Input results in Secure Access Mode.</td></tr><tr><td>Open warning</td><td>Output to activate when the door has been open too long (open sensor has failed to close).</td></tr><tr><td>Not locked warning</td><td>Output to activate when the door has been left unlocked (lock sensor has failed to close).</td></tr></tbody></table>

   **Note:**

   Each site can have different door requirements, (e.g. some will require remote release door functionality, while others will require a warning mechanism when the door is open). The Input/Output requirements for the Door should have been determined during the site design process.

</details>

<details>

<summary>Entry Zone tab</summary>

1. Click the **Entry Zone** tab.

   ![](https://3000903572-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FfCvaxj3suxNBzdwQndVT%2Fuploads%2Fgit-blob-4ab36cd2f33e75e875d4da6e5ae6ec1b1afb9f27%2Fentryzone_v850.png?alt=media)
2. Select the **Access Zone** that Cardholders access when entering through this Door.
3. Select whether **Entry is controlled by** Reader(s) or Push button(s).
4. Select the **Reader(s)** or **Push button(s)** that connect to this Door to control entry.

   **Note:** If you assign both a Third Party/OSDP Reader and an HBUS Terminal to this Door, the Readers behave like so:

   * The Third Party/OSDP Reader can be used for reading third-party cards.
   * The HBUS Terminal will display feedback from the Third Party/OSDP Reader on its screen. [See full overview of what can be displayed](https://help.security.gallagher.com/knowledge-hub/configuration-client/site-installation/doors/creating-doors/what-can-be-displayed-on-an-hbus-terminal-on-the-same-door-as-a-third-party-osdp-reader.md).

   However, note the following when using the HBUS Terminal to display feedback:

   * The HBUS Terminal cannot be used to view or acknowledge alarms.
   * The **Access mode** of the Access Zone of the Door must be set to **Secure**, and the **PINs mode** must be set to **No PIN**. Neither the Third Party/OSDP Reader or the HBUS Terminal will ever prompt for PIN.

   **Notes:**

   * If entry is controlled by a Reader, additional options are enabled:

     * **Disable feedback:** If this option is selected, the Door's Reader(s) will not display prompts, messages, icons, LEDs, or make access granted or access denied sounds when access attempts are made at the Reader.

     **Note:** Selecting this option has the effect of disabling any feature that requires Reader feedback, (e.g. PINs, dual-authorisation, Code or Card mode, local overrides).

     * **Turn off all warning/alarm sounds:** This affects the "beeps" on Readers for "door not locked", "door open too long" and "forced door" statuses for all Readers configured on this tab.
     * **Terminal Display Message:** Optionally set custom messages for the HBUS Terminal **Reader(s)** selected on this tab to display when they grant access, deny access, and/or deny access for anti-passback to the Entry Zone. If you leave these fields blank, the selected HBUS Terminal **Reader(s)** display the default messages when granting/denying access to the Entry Zone.

     **Notes:**

     * To edit these, the **Disable feedback** check box must be unchecked.
     * HBUS Terminals can display a maximum of two full lines of text. If the message is too long, it is truncated when displayed on the Reader.
     * Several Doors' Terminal Display Messages can be modified at once with a Door Bulk Change. See [Initiating a new Door Bulk Change](https://help.security.gallagher.com/knowledge-hub/configuration-client/site-management/bulk-changes/initiating-a-new-door-bulk-change.md).
   * If entry is controlled by a pushbutton, there is an additional **Free handle** option. This can be used for Doors where the lock does not need to be unlocked for exit. When this option is enabled and a valid exit request is made, the Door's lock relay will not activate (Door's outside handle will remain locked).

     Pushbutton/Request to Exit should be wired as normally open, if the Pushbutton input is normally closed then the input can be inverted to provide correct operation.
   * You can configure the Door to allow entry and exit via two Readers/pushbuttons. For example, vehicles of various heights use a building's vehicle Door. Therefore, two entry Readers can be mounted at different heights, one positioned for cars and the other for trucks and buses.

</details>

<details>

<summary>Exit Zone tab</summary>

1. Click the **Exit Zone** tab.

   ![](https://3000903572-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FfCvaxj3suxNBzdwQndVT%2Fuploads%2Fgit-blob-e43d4bb9f2170cb24070c29411ea20428ed588c8%2Fexitzone_v850.png?alt=media)
2. Select the **Access Zone** that Cardholders access when they exit out this Door. There is no reason to configure an Exit Zone to a Door that has no exit Reader. Refer to [Access Zones](https://help.security.gallagher.com/knowledge-hub/configuration-client/site-installation/access-zones.md) for further information.
3. Select whether **Exit is controlled by** Reader(s) or Push button(s).
4. Select the **Reader(s)** or **Push button(s)** that connect to this Door to control exit.

   **Note:** If you assign both a Third Party/OSDP Reader and an HBUS Terminal to this Door, the Readers behave like so:

   * The Third Party/OSDP Reader can be used for reading third-party cards.
   * The HBUS Terminal will display feedback from the Third Party/OSDP Reader on its screen. [See full overview of what can be displayed](https://help.security.gallagher.com/knowledge-hub/configuration-client/site-installation/doors/creating-doors/what-can-be-displayed-on-an-hbus-terminal-on-the-same-door-as-a-third-party-osdp-reader.md).

   However, note the following when using the HBUS Terminal to display feedback:

   * The HBUS Terminal cannot be used to view or acknowledge alarms.
   * The **Access mode** of the Access Zone of the Door must be set to **Secure**, and the **PINs mode** must be set to **No PIN**. Neither the Third Party/OSDP Reader or the HBUS Terminal will ever prompt for PIN.

   **Notes:**

   * If exit is controlled by a Reader, additional options are enabled:

     * **Disable feedback:** If this option is selected, the Door's Reader(s) will not display prompts, messages, icons, LEDs, or make access granted or access denied sounds when access attempts are made at the Reader.

     **Note:** Selecting this option has the effect of disabling any feature that requires Reader feedback, (e.g. PINs, dual-authorisation, Code or Card mode, local overrides).

     * **Turn off all warning/alarm sounds:** This affects the "beeps" on Readers for "door not locked", "door open too long" and "forced door" statuses for all Readers configured on this tab.
     * **Terminal Display Message:** Optionally set custom messages for the HBUS Terminal **Reader(s)** selected on this tab to display when they grant access, deny access, and/or deny access for anti-tailgating to the Exit Zone. If you leave these fields blank, the selected HBUS Terminal **Reader(s)** display the default messages when granting/denying access to the Exit Zone.

     **Notes:**

     * To edit these, the **Disable feedback** check box must be unchecked.
     * HBUS Terminals can display a maximum of two full lines of text. If the message is too long, it is truncated when displayed on the Reader.
     * Several Doors' Terminal Display Messages can be modified at once with a Door Bulk Change. See [Initiating a new Door Bulk Change](https://help.security.gallagher.com/knowledge-hub/configuration-client/site-management/bulk-changes/initiating-a-new-door-bulk-change.md).
   * If exit is controlled by a pushbutton, there is an additional **Free handle** option. This can be used for Doors where the lock does not need to be unlocked for exit. When this option is enabled and a valid exit request is made, the Door's lock relay will not activate (Door's outside handle will remain locked).

     Pushbutton/Request to Exit should be wired as normally open, if the Pushbutton input is normally closed then the input can be inverted to provide correct operation.
   * Morpho Biometric Readers are not recommended for use on exit Doors. However, if you configure the exit at a Door to be controlled by a Morpho Reader, you must specify an Access Zone (even if you create one just for this purpose), otherwise no one will be able to exit through the Door.
   * You can configure the Door to allow entry and exit via two Readers/pushbuttons. For example, vehicles of various heights use a building's vehicle Door. Therefore, two entry Readers can be mounted at different heights, one positioned for cars and the other for trucks and buses.

</details>

<details>

<summary>Advanced tab</summary>

1. Click the **Advanced** tab.

   ![](https://3000903572-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FfCvaxj3suxNBzdwQndVT%2Fuploads%2Fgit-blob-5441ed81c5525f22877017ebd42a82201b191ea3%2Fdoor_advanced.png?alt=media)
2. Select the appropriate **Lock Type** from the drop-down list:

   <table><thead><tr><th width="156">Lock Type</th><th>Description</th></tr></thead><tbody><tr><td>Shear Lock</td><td>When configured as a Shear Lock and a valid card is presented the door unlocks.<br>If the door is not physically opened it will relock after the "Door unlock time" is exceeded.<br>If the Door is opened, the lock relay remains active until the Door open sensor recloses, (i.e. the Door closes).<br><strong>Uses:</strong><br>Electronic bolts or double doors that do not have to rebate to prevent the inactive door locking prior to the active door.</td></tr><tr><td>Mortise Lock</td><td><p>When configured as a Mortise Lock and a valid card is presented the door unlocks.</p><p>If the door is not physically opened it will relock after the "Door unlock time" is exceeded.</p><p>If the Door is opened the lock relay resets immediately when the Door Open sensor switches open.</p><p>When the Door physically closes the lock is in a state that immediately re-secures the Door.</p><p><strong>Uses:</strong></p><ul><li>Most standard lock situations</li><li>Magnetic clamp locks</li></ul></td></tr><tr><td>Automatic Lock</td><td>When configured as an Automatic Lock the lock relay will always be activated for the user configured time. This time is set by the use of the <strong>Door unlock time</strong> option. All other settings will be as for the other lock types.<br><strong>Uses:</strong><br>Magnetic clamp door with only one Input.</td></tr><tr><td>Half-Cycle Lock</td><td>When configured as a Half-Cycle Lock and a valid card is presented, the Door will unlock and remain unlocked until opened and shut.<br>Since the intended use is to leave doors closed after unlocking them, No Entry Taken ("access granted but not taken") events are not raised for Half-Cycle Doors. Reader's LEDs flash green on access granted and remain solid green while closed and unlocked; Terminals will flash green on access granted and continue flashing while closed and unlocked, unless they are configured as Cardax IV Readers, in which case their LEDs behave the same as Readers.<br>When this lock type is selected, the <strong>Door unlock time</strong> and <strong>Extended access time</strong> options are disabled, because the Door is unlocked indefinitely.<br>If the Access Zone enters lockdown while a Half-Cycle Door is shut and unlocked, the unlocked state is restored once lockdown ends.<br>Half-Cycle type Doors have the extra 'Lock Door' override available, to allow the Door to be locked by an operator with the 'Override - Lock Door' privilege. While a Door is shut and unlocked after access has been granted, the 'Lock Door' override can be used to lock it.</td></tr></tbody></table>

   **Notes:**

   * The system will energise the lock in accordance with the lock type selected.
   * Ticking the **Access is via turnstile** checkbox means that when the door opens, only the last person who badged and was granted access is logged as having entered and if two people badge without the door opening, then the first person gets logged as having not entered. This is regardless of whether the person is a visitor or an escort. With a turnstile, if an escort has several visitors, then either the escort has to go through the door first, and then all the visitors (within a timeout), or else there will be a 'no entry' event for the escort.
3. Configure the Door timeouts as required.

   <table><thead><tr><th width="222">Option</th><th>This setting...</th></tr></thead><tbody><tr><td>Door is confirmed as closed after</td><td>is to stop door bounce causing a forced door alarm.<br>(Valid range is 0 - 5000 milliseconds.<br>Default = 200 milliseconds)</td></tr><tr><td>If lock attempt fails, alarm after</td><td>determines when a Door Not Locked alarm and beep is generated.<br>(Valid range is 1 - 60 seconds.<br>Default = 20 seconds)</td></tr><tr><td>Retry the lock</td><td>determines if the lock relay is pulsed when the door is not locked.</td></tr><tr><td>Door unlock time</td><td>determines the maximum time the Unlock relay is energised.<br>(Valid range is 1 - 86400 seconds.<br>Default = 5 seconds)</td></tr><tr><td>Card to complete action must be presented within</td><td><p>determines either:</p><ul><li>the maximum time between card swipes for Dual Authorisation, <strong>OR</strong></li><li>the time between pressing a function key on a keypad reader and badging the card for an Access Zone or Alarm Zone override.</li></ul><p>(Valid range is 1 - 99 seconds.<br>Default = 5 seconds)</p></td></tr><tr><td>PIN (for PIN entry) failed if not entered correctly within</td><td><p>determines either:</p><ul><li>the maximum time between badging a card and starting to enter a PIN at a keypad reader for access through a door in PINs mode, <strong>OR</strong></li><li>overriding an Access Zone or Alarm Zone in PINs mode.</li></ul><p>(Valid range is 1 - 99 seconds.<br>Default = 10 seconds)</p></td></tr><tr><td>Disable ‘Open Too Long’ alarms</td><td>is only available if the Lock type is ‘Half-Cycle’.<br>When checked, this setting disables the settings <strong>Door warns ‘Open Too Long’ if still open after</strong> and <strong>Door is ‘Open Too Long’ if still open after</strong>, so that no ‘Open Too Long’ warnings or alarms are raised for this Door.<br><br><strong>Note:</strong> ‘Open Too Long’ alarms are only raised if the door is physically open, not if it is unlocked and shut.</td></tr><tr><td>Door warns 'Open Too Long' if still open after</td><td>determines when the door reader starts beeping to warn the door has been open too long.<br>(Valid range is 0 - 9999 seconds.<br>Default = 20 seconds)<br><br><strong>Note:</strong><br>This cannot be set as greater than the alarm time, (i.e. the <strong>Door is 'Open Too Long' time</strong>). If it is, and you attempt to save the Door, the following error message will display:<br><em>"The 'Open Too Long' warning time must be less than or equal to the 'Open Too Long' alarm time."</em></td></tr><tr><td>Door is 'Open Too Long' if still open after</td><td>determines when a Door Open Too Long alarm is generated.<br>(Valid range is 5 - 9999 seconds.<br>Default = 20 seconds)</td></tr><tr><td>Door is 'Forced Open' if opened while still locked</td><td>when checked, causes a Forced Door alarm to be generated if the the open sensor detects the door is opened.</td></tr><tr><td>Door lock status follows entry zone only</td><td>when checked, the state of the door (locked or unlocked) will be based on the status of the Entry Zone only, (i.e. door is locked when the Entry Zone is secure; door is unlocked when the Entry Zone is set to free access).</td></tr><tr><td>Play tone on HBUS readers while door is unsecured</td><td>when checked, any T series readers operating over HBUS associated to the doors Entry and Exit Zone will play an extended access granted tone for the duration of the door being unsecured, (e.g. unlocked or open).</td></tr><tr><td>Play tone on HBUS readers when door is released</td><td>when checked, any T series readers operating over HBUS associated to the doors Entry and Exit Zone will play an extended tone when the door is opened via a remote release button, open door override, or an exit button on the secure side of the door.<br>This tone will play regardless of the <strong>Turn off all warning/alarm sounds</strong> setting on the doors <strong>Entry Zone</strong> and <strong>Exit Zone</strong> tabs.</td></tr><tr><td>Extended access time</td><td>determines an alternate unlock time, allowing the door to remain unlocked for longer than normal for those cardholders who require it, (e.g. disabled people, couriers, etc.).<br>(Valid range is 0 - 86400 seconds.<br>Default = 25 seconds)<br>Refer to <a href="https://help.security.gallagher.com/knowledge-hub/configuration-client/site-installation/doors/configuring-extended-access-time-for-a-door.md">Configuring alternate unlock time for a Door</a> for further details.</td></tr></tbody></table>

</details>

<details>

<summary>Lock Cycle Counting tab</summary>

This tab is visible regardless of whether the Door is configured on a Controller 6000 or 7000. However, Lock Cycle Counting functions only when the Door is connected to a Controller 7000 from v9.40 onwards.

Lock Cycle Counting tracks how many times the door lock has been activated and optionally raises alarms when limits are reached.

1. Click the **Lock Cycle Counting** tab.

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

   <table><thead><tr><th width="156">Field/Checkbox</th><th>Description</th></tr></thead><tbody><tr><td>Lock cycle count</td><td><ul><li>When Command Centre is first upgraded from a version <strong>prior to 9.40 to 9.40 or later</strong>, this field <strong>defaults to 0</strong>.</li><li>Displays the current number of lock cycles recorded for the door.</li><li>Can be manually modified to reflect the number of times the lock has been triggered, (e.g. after maintenance or lock replacement).</li><li>Automatically increments when lock cycles occur (Door unlocked + locked = 1 cycle).</li><li><strong>Valid range:</strong> 0 to 100,000,000.</li></ul></td></tr><tr><td>Lock cycle limit</td><td><ul><li>Defaults to <strong>400,000</strong>.</li><li>Represents the maximum recommended number of lock cycles for the lock hardware.</li><li>Can be modified based on the type and manufacturer’s recommendations for the lock hardware used.</li><li><strong>Valid range:</strong> 0 to 100,000,000.</li></ul></td></tr><tr><td>Alarm threshold percentage</td><td><ul><li>Defaults to <strong>80%</strong>.</li><li>Specifies the percentage of the lock cycle limit at which the system raises an “approaching limit” alarm.</li><li>The system raises a "limit reached "alarm when the lock cycle count reaches <strong>100%</strong> of the limit.</li><li><strong>Valid range:</strong> 0 to 100.</li></ul></td></tr><tr><td>Enable lock cycle counting alarms</td><td><ul><li>Checkbox is disabled by default.</li><li>When disabled, lock cycle count continues to increment when lock cycles occur with no alarm generated.</li><li>When enabled, activates lock cycle alarms.</li></ul></td></tr></tbody></table>
3. Clicking the **Apply** or **OK** button will confirm and save all changes made to the editable fields and checkbox.

</details>

<details>

<summary>Challenge and More Challenge tabs</summary>

Configuration on the **Challenge** and **More Challenge** tabs are used is only required for configuring the Challenge feature. For an explanation of this feature and further configuration details, refer to [Configuring Challenge](https://help.security.gallagher.com/knowledge-hub/configuration-client/site-installation/doors/challenge/configuring-challenge.md).

</details>

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

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

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

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

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

    The door name now displays within the Door window.

***

### Editing and Deleting Doors

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

**Note:** If you attempt to delete a Door that is linked to a macro or belongs to an Interlock Group, 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 is used in an Interlock 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/doors/creating-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.
