> 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/integrated-systems/allegion-engage-interface/command-centre-configuration/gallagher-command-centre-engage-gateway-configuration.md).

# Gallagher Command Centre Engage Gateway configuration

### Introduction

An Engage Gateway provides Command Centre with a certificate which is used to encrypt the communications that are sent to the Gateway. It is also used to decrypt what has been sent from the Gateway to Command Centre.

This procedure details how to create an Engage Gateway.

### Prerequisites

Before proceeding with this procedure, ensure:

* An Engage Gateway has been created in the Allegion Engage™ Mobile App. See [Commissioning Engage Gateways from the Allegion Engage™ Mobile App](https://help.security.gallagher.com/knowledge-hub/configuration-client/integrated-systems/allegion-engage-interface/allegion-engage-configuration/commissioning-engage-gateways-from-the-allegion-engage-mobile-app.md) for the procedure.
* Locks have been created in the Allegion Engage™ Mobile App. See [Commissioning Engage Doors from the Allegion Engage™ Mobile App](https://help.security.gallagher.com/knowledge-hub/configuration-client/integrated-systems/allegion-engage-interface/allegion-engage-configuration/commissioning-engage-doors-from-the-allegion-engage-mobile-app.md) for the procedure.
* Your license file allows for the number of doors you are adding.

### Configuration

To configure an Engage Gateway, perform the following procedure in Gallagher Configuration Client:

1. Click **Configure** from the menu bar, then **Engage**.

   The Engage List Window opens.
2. **Right click** and select **New\...Engage Gateway**.

   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 assign a primary Alarm Zone for all events.

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

   ![](https://3000903572-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FfCvaxj3suxNBzdwQndVT%2Fuploads%2Fgit-blob-2db26a3eb41c33432357f1d458a34a9cdb0361ff%2Fallegionengagegateway_configurationtab.png?alt=media)
6. Input the **IP Address**, and select the **Engage Site** and **Controller** from the drop-down list.

   **Notes:**

   * The IP Address should be the same IP Address you gave the Gateway when you created it using the App. You can find this on the App by bringing up the Gateway and clicking on **Host Properties**.
   * It is recommended that no more than eight Engage Gateways are connected a single Gallagher Controller.
7. Click the **Engage Doors** tab.

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

   Doors you have created in the Allegion Engage™ Mobile App appear in bold.
8. Click on the **Create Items** button.

   All Doors that were bold no longer appear in bold, indicating they have been created in Command Centre.

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

   **Note:** The names of the Doors will be the names given in the Allegion Engage™ Mobile App.
9. Click the **Icons** tab if you want to change the Icon Set for this Engage Gateway.

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

    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).
11. Click the **Notes** tab if you want to add a note(s) about this Engage Gateway.

    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 **Apply** to save the Gateway.

    **Note:** If you click **Apply** without first creating the Gateway in the Allegion Engage™ Mobile App, the following error message will display:

    *"Unable to connect to the Engage Gateway at the specified IP address."*

### Failure to create doors

If there are insufficient licenses to create the doors in Command Centre, or if a door is given the same name as an existing Engage Door in the Command Centre server, the doors will fail to create. If the issue is due to licensing, the doors will be created up until the license limit is reached. If the installer wants to choose which doors they want created, they will need to use the Allegion Engage™ Mobile App to remove the doors they do not want to be created. They can also use the app to change the name of a door. They can then go back to the Gateway item and ‘Create Doors’ to update what has been created in Command Centre.

### Editing and Deleting Gateways

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 Engage Gateways.

**Notes:**

* You cannot delete a Gateway that has Doors assigned to it.
* If for some reason the Gateway is deleted from Command Centre, it will need to be factory reset before it can be used again.

Press and hold the **Factory Default Reset** button until the Gateway Status LED flashes green two times and remains solid. After the indicator flashes twice, release the **Factory Default Reset** button.

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

For more information refer to the [ENGAGE™ Gateway Installation Instructions and User Guide](https://us.allegion.com/content/dam/allegion-us-2/web-documents-2/InstallInstructions/Schlage_ENGAGE_Gateway_Installation_Instructions_and_User_Guide_110964.pdf).


---

# 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/integrated-systems/allegion-engage-interface/command-centre-configuration/gallagher-command-centre-engage-gateway-configuration.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.
