> 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/licensable-features/multi-server-systems/remote-command-centre-items.md).

# Remote Command Centre items

### Introduction

When Command Centre items are viewed on a server other than their home server, (i.e. a remote server), they may behave slightly differently than they do on their home server. Command Centre items in a multi-server system are split into two groups, as the following table shows:

<table><thead><tr><th width="116">Item Type</th><th width="367">Definition</th><th>Command Centre items</th></tr></thead><tbody><tr><td>Global items</td><td>Global items can be viewed at, and edited from, any workstation connected to any server in a multi-server system by an operator with suitable privileges.</td><td>Cardholders</td></tr><tr><td>Remote items</td><td>Remote items are only editable from workstations connected to the server they were created on. Some Remote Items can be viewed from servers other than their home server, and behave as <strong>read-only</strong> representations of the original item when viewed from a remote server.</td><td><ul><li><strong>Access Groups *</strong></li><li><strong>Card Types</strong></li><li><strong>Personal Data Fields **</strong></li><li><strong>Divisions</strong></li><li><strong>Operator Groups</strong></li><li><strong>Macros***</strong></li><li><strong>Site Plans</strong></li><li><strong>Remote Server</strong></li><li>Icon Sets</li><li>Alarm Instructions</li><li>Insertion Tags</li><li>Workstations</li></ul></td></tr></tbody></table>

**Note:** The remote items above in **bold** text can be viewed from the appropriate List Window. However, the other remote items, or any item on another server, can be located by using the Find Tool. See [Searching using Divisions](https://help.security.gallagher.com/knowledge-hub/configuration-client/site-monitoring/find-tool/examples/example-3-searching-using-divisions.md) for further detail.

**\*** Some **Access Group** properties are editable remotely. Local access can be assigned to remote Access Groups in the same way as for local Access Groups. Any access assigned on other servers is visible from all servers by suitably privileged operators, but cannot be removed.

**Note:** "Access" includes Access Zones, Alarm Zones, Salto Doors and Salto Zones.

**\*\* Personal Data Fields** should have unique names across servers.

**\*\*\*** **Macros** can be scheduled remotely while the home server of the Macro is online.

### Identifying an item's server

It is possible to identify which server a remote item belongs to from the **Server** field on the **General** tab of the item's property pages.

**Note:** The **Server** field is only visible for remote items. It does not display for cardholders.

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

You can give the server a more user friendly name by adding a 'Short Name' on the **General** tab of the Server Properties. The short name is then used instead of the hostname configured against the remote item.

Remote items have a restricted set of property page tabs from what would normally be visible for that item type. Only those tabs necessary for remote monitoring, (e.g. for editing or performing an override) will display. Operator privileges will also determine what information appears as 'read-only' within those tabs.

The Alarm Viewer window appears the same between servers, (i.e. there is no way of telling which server an alarm was generated by). However, when you view the alarm details, if a server name appears in the title bar in brackets, this indicates that the alarm was generated by a remote server.

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

**Notes:**

* When a remote server is off-line, a user will not be able to acknowledge the alarm and it will be marked as off-lline if they attempt to do so. All other remote alarms from that remote server will appear as off-line, read only and the user will not be able to process or enter details against them.
* If you are viewing off-line remote alarms in the Alarm Viewer and the Alarm Viewer is refreshed, (e.g. **F5** ), all off-line alarms will be removed and will not reappear until the remote server comes online again.

### Deleting remote Command Centre items

Remote Command Centre items cannot be deleted manually, instead they need to be deleted from the home server of the item.


---

# 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/licensable-features/multi-server-systems/remote-command-centre-items.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.
