> 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/adding-external-systems-to-a-site-plan.md).

# Adding external systems to a Site Plan

### Introduction

External systems, like other site items, can be displayed on Site Plans. Operators require the “Edit Site” operator privilege to perform this procedure.

### Procedure

1. Open the Site Plan you wish to add the external system to. [How?](https://help.security.gallagher.com/knowledge-hub/configuration-client/site-monitoring/site-plans/viewing-an-existing-site-plan.md)

   **Note:**

   The Site Plan needs to be in “Edit” mode, (i.e. have a red line border around it), to add an item to it.
2. Click the ![](https://3000903572-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FfCvaxj3suxNBzdwQndVT%2Fuploads%2Fgit-blob-51cc461b0e8b4f0bbc61fdd5d00eee40ff63cf28%2Fediticon.png?alt=media) Site Plan editing icon to change to “Edit” mode if necessary.
3. Click **Configure** from the menu bar, then **External Systems**.

   The **External Systems** List Window opens (in [tree view](https://help.security.gallagher.com/knowledge-hub/configuration-client/introduction-to-command-centre/knowing-your-way-around/list-windows/tree-view.md)).
4. Select the item you want to add to the Site Plan, and drag and drop it onto the Site Plan.
5. **Close** the Site Plan.
6. A confirmation window displays.

   Click **Yes** to save your changes.

### Result

The external system has been added to a Site Plan.

### Hint

{% hint style="info" %}
External systems can also be added to Site Plans from the Find Tool.
{% endhint %}


---

# 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/adding-external-systems-to-a-site-plan.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.
