> 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/services-and-workstations/connecting-to-the-cloud.md).

# Connecting to the Cloud

### Introduction

This procedure describes how to create a Command Centre Cloud item. This item connects your Command Centre system to the Cloud. This item represents the status of the Cloud. Only one Command Centre Cloud item can be created per Command Centre server.

**Notes:**

* The Command Centre server authenticates against the Cloud using a private certificate which is stored in Command Centre's database. If you wish to move your Command Centre installation from one server to another, refer to [Server Migration](https://help.security.gallagher.com/knowledge-hub/configuration-client/site-installation/services-and-workstations/connecting-to-the-cloud/server-migration.md) for further detail.
* In a Command Centre multi-server environment, credentials issued on one server will replicate out to other servers. If you wish to issue credentials from multiple servers, you will need to create a Command Centre Cloud item on each Command Centre server used to issue credentials; the Command Centre Cloud item is not replicated across servers. If you wish to merge Command Centre servers that have been using this feature, please contact Gallagher Technical Support.
* If you attempt to issue credentials from a Command Centre server that does not have a Command Centre Cloud item, the credentials will sit in the "sending" state, until the mobile credential expires; no invitation email is sent.

***

### Before you begin

Ensure you are logged on as an operator with the "Advanced User" privilege.

**Note:** While the "Advanced User" privilege is required to create the Command Centre Cloud item, to edit the properties of the Command Centre Cloud item you only need the "Edit Site" privilege.

***

### Configuration

To create a Command Centre Cloud item, perform the following procedures in Gallagher Configuration Client:

1. Click **Configure** from the menu bar, then **Services & Workstations**.

   The **Services and Workstations** 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\...Command Centre Cloud.**

   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 each tab in turn to configure a Command Centre Cloud item:

<details>

<summary>Status and Overrides tab</summary>

1. Click the **Status and Overrides** tab.

   **Notes:**

   * When talking to the Cloud there are two communication channels; an inbound (Receive) channel and an outbound (Send) channel, either of which can be active independently of the other.

     Both the send and receive channels can be online, offline or idle independently of one another, and if there is a network error, it will now show some text related to that error. For example:

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

     <table><thead><tr><th width="84">Status</th><th>Description</th></tr></thead><tbody><tr><td>Idle</td><td>The channel has no work to do and has not attempted to connect to the Cloud.</td></tr><tr><td>Online</td><td>The channel has successfully connected to the Cloud.</td></tr><tr><td>Offline</td><td>The channel has attempted to connect to the Cloud, but has failed due to an error.</td></tr></tbody></table>
   * If the Cloud is offline it is highly likely that the individual network configuration of the site (Firewalls, network connections, etc.) is preventing the connection. It is likely the IT staff on site will need to be involved to unblock the connection. More detailed error information may be available in the Command Centre log file.

</details>

<details>

<summary>Configuration tab</summary>

1. Click the **Configuration** tab.

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

   <table><thead><tr><th width="144">Field</th><th>Description</th></tr></thead><tbody><tr><td>Region</td><td>The ‘Command Centre Cloud’ resides in Sydney, Australia.</td></tr><tr><td>URL</td><td>This field only appears and is enabled when 'Custom' is selected as the <strong>Region</strong>. 'Custom' should only be selected upon advisement from Gallagher Technical Support. The URL is:<br><strong>Command Centre Cloud:</strong><br>DNS address: <strong>commandcentre-ap-southeast-2.security.gallagher.cloud</strong><br>It has two static IP addresses: <strong>52.62.211.7</strong> and <strong>54.79.91.203</strong></td></tr><tr><td>Enable Gallagher API Gateway</td><td><p>The Gallagher API Gateway allows Command Centre Mobile, Rest API, Web Client, Apple Wallet and OneLink Clients to connect securely from anywhere without the need for complex reverse proxy solution or VPNs.<br>If your site wants the ability to access Command Centre from any internet connected device, (including desktop and mobile), configure as follows:</p><ol><li>Tick the <strong>Enable Gallagher API Gateway</strong> checkbox.<br>The <strong>Region</strong> selector below it is enabled.</li><li>Select the appropriate <strong>Region</strong> from the drop-down, (i.e. Australia, United States or Custom).<br><br><strong>Note:</strong> If you select 'Custom' a <strong>URL</strong> field will appear. Custom should only be selected upon advisement from Gallagher Technical Support.</li><li>Tick the <strong>Enable Command Centre Web</strong> checkbox.<br>A <strong>URL</strong> field displays populated with a system generated URL address.<br><strong>Tip:</strong> Clicking <strong>once</strong> in the <strong>URL</strong> field will highlight the entire URL to allow you to copy it.<br><img src="https://3000903572-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FfCvaxj3suxNBzdwQndVT%2Fuploads%2Fgit-blob-66ab7f820d2baa2169ee2e3fd45b2015364128c8%2Fregistrationserver_enableccweb.png?alt=media" alt="Arrows"></li><li>Enter the appropriate country code in the <strong>Default country for SMS verification</strong> field by either typing it in or selecting from the drop-down list.</li><li>Click the <strong>OK</strong> or <strong>Apply</strong> button to save your changes.<br><br><strong>Note:</strong> This step is necessary for the system to generate the correct URL address.</li></ol></td></tr><tr><td>Region</td><td>This is the region that the Gallagher API Gateway resides in.</td></tr><tr><td>URL</td><td>This field only appears and is enabled when 'Custom' is selected as the Gallagher API Gateway <strong>Region</strong>. Custom should only be selected upon advisement from Gallagher Technical Support. The AU/US URLs are:<br><strong>Australian Gateway Region:</strong><br>DNS address: <strong>commandcentre-api-au.security.gallagher.cloud</strong><br>It has two static IP addresses: <strong>3.106.1.6</strong> and <strong>3.106.100.112</strong><br><strong>United States Gateway Region:</strong><br>DNS address: <strong>commandcentre-api-us.security.gallagher.cloud</strong><br>It has two static IP addresses: <strong>44.193.42.111</strong> and <strong>3.209.194.103</strong></td></tr><tr><td>Expire invitations after</td><td>This field allows you to configure the invitation expiry time period, (i.e. the invitation will be valid for 7 days from when it was registered to a user in Command Centre). The default invitation expiry period is 7 days. Minimum expiry period is 1 hour. Maximum expiry period is 100 days. When the invitation has expired, the invitation is removed from the Command Centre Cloud.</td></tr><tr><td>Default country code for SMS verification</td><td><p>Select or <strong>type</strong> the default country code for SMS verification of the mobile credential.<br><br><strong>Notes:</strong></p><ul><li>The country code specified here will automatically prepend the cardholder’s mobile number when the SMS verification is sent.</li><li>If a cardholder’s mobile number already specifies a country code, then the country code here will not be used. This enables cardholders within different regions to receive SMS verification, for mobile credential registration.</li><li>Typing a country code will display the option 'Custom' with your country code entered.</li></ul></td></tr><tr><td>Use custom facility name</td><td>If the <strong>Use custom facility name</strong> checkbox is unchecked, the default facility name (taken from the Command Centre licence file) will be used in the invitation email subject line, (i.e. You have received a new mobile credential for [facility name]).<br>To use a custom facility name in the invitation email subject line, check the <strong>Use custom facility name</strong> checkbox and enter a custom name in the text field.<br>If you do not wish to use a facility name in the invitation email subject line, check the <strong>Use custom facility name</strong> checkbox and leave the text field blank.</td></tr></tbody></table>

</details>

<details>

<summary>Trusted Peer List <em>(<strong>Note:</strong> Only sites using the Cardholder Sync Utility need to modify this tab)</em></summary>

1. Click the **Trusted Peer List** tab.

   Source servers, (i.e. a server that shares cardholder information and mobile credentials with other servers) can define the Command Centre systems they want to share credentials with on this tab. The Gallagher Cloud will ensure mobile credentials are only shared with these trusted sites.

   *For example:* In a multi-tenanted building where a tenant needs to access both their own areas (controlled by one Command Centre system) as well as shared areas such as a lobby (controlled by another Command Centre system).

   ![](https://3000903572-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FfCvaxj3suxNBzdwQndVT%2Fuploads%2Fgit-blob-12f6cf1861074497519cc07328af702ce90aa5c8%2Fregistrationserver_trustedpeerlisttab.png?alt=media)
2. Click the **Add** button.

   The Add or modify Cardholder Sync site for Mobile Credential sharing dialog displays.

   ![](https://3000903572-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FfCvaxj3suxNBzdwQndVT%2Fuploads%2Fgit-blob-a45d6da26c06470d32c8f6f87275665696d3f98d%2Fregistrationserver_addtrustedpeer.png?alt=media)
3. Add the **Site Serial Number** of the site you want to share credentials with and an appropriate **Description**.
4. Click the **OK** button.

   The dialog closes and the details you entered populate the grid on the **Trusted Peer List** tab. The Description you entered appears in the 'Notes' column.

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

   **Notes:**

   * Highlighting a Cardholder Sync site in the grid and clicking the **Modify** button allows you to modify the Description. The Site Serial Number cannot be changed.
   * A Cardholder Sync sites can be removed by highlighting it in the grid and clicking the **Delete** button.

</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-7e00dc2b70a179906f18c208418e665d4358ab88%2Fregistrationserver_advancedtab.png?alt=media)

   This screen allows you to:

   * configure an outbound **Proxy Server** for Command Centre to use when talking to the Cloud.

     **Note:** Only HTTP(s) proxies are supported, (i.e. SOCKS and other proxy protocols are not supported).
   * purge Command Centre Cloud.

     **WARNING:** This feature should not be used in isolation, (i.e. purging the Cloud deletes all data in the Cloud as well as deleting the Cloud item itself). If a site wishes to create a new cloud item, mobile credentials will require reissuance.

     For further details refer to **Mobile Connect Cloud and App Security TIP.pdf** located in the `‘Documentation’` directory of the Command Centre installation files.
2. Configure an outbound proxy server if needed, as follows:
   1. Tick the **Use custom Proxy Server settings** checkbox.

      The other fields become enabled.
   2. Enter the **Host** and **Port** for your proxy server.
   3. Enter logon credentials, (i.e. **Username** and **Password** ).
3. Click the **Test Connection** button to check your connection to the Cloud.

   The message *"Successfully Connected to the Cloud"* will display if the connection is successful, otherwise the remote server will return an error message.

</details>

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

**Note:** The Command Centre Cloud is now available for use by Mobile Notifications to send alarm notifications to Mobile Client users. Refer to [Mobile/SMS Notifications](https://help.security.gallagher.com/knowledge-hub/configuration-client/site-installation/server-properties/mobile-sms-notifications.md) for details on how to enable Mobile Notifications to be sent to Mobile Client users.


---

# 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/services-and-workstations/connecting-to-the-cloud.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.
