> 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/external-systems/the-external-systems-list-window.md).

# The External Systems List Window

### Introduction

The **External Systems** List Window allows the following external systems, and associated children to be created.

<table><thead><tr><th width="192">System type</th><th width="192">Child</th><th>Purpose</th></tr></thead><tbody><tr><td>DVR System</td><td>DVR Camera</td><td>DVR Interface</td></tr><tr><td>Intercom System</td><td>Intercom</td><td>Jacques Intercom Interface</td></tr><tr><td>External System</td><td>External System Item</td><td>FTCAPI functionality</td></tr><tr><td>Austco Intercom System</td><td>Austco Intercom</td><td>Austco Intercom Interface</td></tr><tr><td>SchindlerID System</td><td></td><td>Schindler Cardholder Management Interface</td></tr><tr><td>Commend Intercom System</td><td>Commend Intercom Item</td><td>Commend Intercom Interface</td></tr></tbody></table>

The **External Systems** List Window displays in tree view showing all external system(s), set up in your system.

By expanding the tree, the children of each system can also be displayed and edited, and in the case of DVR, ‘live footage’ viewed.

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

In this example, there are three Intercoms that belong to the ‘Jacques Intercom System’, one Austco Intercom that belongs to the ‘Austco Intercom System’ and a ‘SchindlerID System’. There are also two External System Servers. 'External System Server 1' has the ‘External System 1’ assigned to it and 'External System Server 2' has the ‘Sample DVR System’ assigned to it.

**Note:** At most, 100 External System Items can be assigned to an External System. However, you can configure multiple External Systems that are the same. To configure an External System that is the "same as" another External System, refer to Step 8 in the topic *"Configuring an External System"*.

### Configuration

To configure your external system, refer to the appropriate procedure below:

* [Configuring an External System Server](https://help.security.gallagher.com/knowledge-hub/configuration-client/site-installation/external-systems/configuring-an-external-system-server.md)
* [Configuring an External System](https://help.security.gallagher.com/knowledge-hub/configuration-client/site-installation/external-systems/configuring-an-external-system.md)
* [Configuring a DVR System](https://help.security.gallagher.com/knowledge-hub/configuration-client/site-installation/external-systems/configuring-a-dvr-system.md)
* [Configuring FTCAPI Trigger Strings and Reflected Outputs](https://help.security.gallagher.com/knowledge-hub/configuration-client/site-installation/external-systems/configuring-ftcapi-trigger-strings-and-reflected-outputs.md)
* [Configuring a SchindlerID System](https://help.security.gallagher.com/knowledge-hub/configuration-client/site-installation/external-systems/schindlerid/cardholder-management-interface/configuring-a-schindlerid-system.md)
* [Adding external systems to a Site Plan](https://help.security.gallagher.com/knowledge-hub/configuration-client/site-installation/external-systems/adding-external-systems-to-a-site-plan.md)


---

# 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/external-systems/the-external-systems-list-window.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.
