> 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/creating-an-engage-site-in-gallagher-configuration-client.md).

# Creating an Engage Site in Gallagher Configuration Client

### Introduction

This procedure details how to create an Engage Site and add site managers to the site.

**Notes:**

* Engage Site Managers can delegate access using the Allegion Engage™ Mobile App to Allegion Engage™ Mobile App Operators. Operators can run diagnostics, perform firmware updates, and link and unlink devices to Gateways.
* An Engage Site cannot be deleted while there are Gateways or Site Managers still attached to the site.

### Prerequisites

Prior to creating an Engage Site, a Command Centre Cloud item needs to be created first. See [Connecting to the Cloud](https://help.security.gallagher.com/knowledge-hub/configuration-client/site-installation/services-and-workstations/connecting-to-the-cloud.md) for the procedure.

### Configuration

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

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

   The Engage List Window opens.

   ![](https://3000903572-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FfCvaxj3suxNBzdwQndVT%2Fuploads%2Fgit-blob-784ee78ee7ae53027502494fb2709ec9224653a2%2Fallegionmlw.png?alt=media)
2. **Right click** and select **New\...Engage Site**.

   By default the **General** tab displays.

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

   **Note:** The Engage Site Name is prefixed with the unique server serial number (from the license file).
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 **Apply** button.

   **Notes:**

   * If you did not create a Command Centre Cloud item prior to starting this procedure, the following error message will display:

     *"The operation failed. Please ensure Command Centre is configured to communicate to the cloud."*
   * If you miss this step the "Send Invitation" option will fail with an error message.
5. Click the **Site Managers** tab.

   This tab allows you to invite Site Managers.

   ![](https://3000903572-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FfCvaxj3suxNBzdwQndVT%2Fuploads%2Fgit-blob-c04e555a55b4a3906d96702f75a89219d7b63d30%2Fallegionengagesite_sitemanagerstab.png?alt=media)
6. Click the **Invite Site Manager** button.

   The "Invite Site Manager" dialog displays.

   ![](https://3000903572-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FfCvaxj3suxNBzdwQndVT%2Fuploads%2Fgit-blob-1d421dbbbc909b52a2d51ccbb757b9a402d3ff5a%2Fallegionengage_invitesitemanagerscreen.png?alt=media)
7. Type in the **Email Address** of the person you require as a Site Manager.
8. Confirm the email address by re-typing it in the **Confirm Email** field.
9. Click the **Send Invitation** button.

   An email is sent to the email address and the date and time the email was sent displays in the **Invitation History** grid.
10. Click the **Close** button.

    The "Invite Site Manager" dialog closes.

    The details of the email recipient will not display in the **Site Managers** grid until they have accepted the invitation.
11. The email recipient accepts the invitation as follows:
    1. Click the **Accept This Invite** link in the email.

       The Engage Terms & Conditions page displays.

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

       **Note:** If the Engage invite is not accepted it will be withdrawn after five days and is unable to be resent to the same email address.
    2. Scroll down and read through the Terms & Conditions.
    3. At the end of the Terms & Conditions page click the **I ACCEPT** button.

       The "Create New Account" dialog displays.

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

       **Note:** If the email recipient already has an account, they should click **Click here to sign in** instead with their account.
    4. Enter your details and click the **Submit** button.

       Another email is sent, and you need to click **Confirm my account**.

       ![](https://3000903572-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FfCvaxj3suxNBzdwQndVT%2Fuploads%2Fgit-blob-8ff81a096ab5c8f072683d4134979fa55f25c91e%2Fsmconfirmaccount.png?alt=media)
12. Once the invitation has been accepted, click the **Refresh** button on the **Site Managers** tab.

    The name and email address of the person who accepted the invitation will also populate the **Site Managers** grid.

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

    **Notes:**

    * The Username is taken from the User Profile on the Allegion Engage webpage. Changing it there automatically changes it on this tab also.
    * Any Allegion Engage™ Mobile App Operators will also show in the **Site Managers** grid. Their role will be Operator.
    * If you wish to remove a Site Manager, simply highlight the Site Manager in the **Site Managers** grid and select the **Remove** button.
13. Click the **Icons** tab if you want to change the Icon Set for this Engage Site.

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

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

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


---

# 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/creating-an-engage-site-in-gallagher-configuration-client.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.
