> 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-monitoring/site-plans/viewing-an-existing-site-plan.md).

# Viewing an Existing Site Plan

### Introduction

You may want to see more details about a particular site plan. This can be done by opening either the Site Plan properties or the Site Plan layout, (i.e. the graphical image of a site, or part of a site).

### Procedure

1. Click **Monitor** from the menu bar, then **Site Plans**.

   The **Site Plan** 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)).
2. Highlight the Site Plan you want to view.
3. **Right click** the mouse button.
4. From the displayed pop-up menu, either:
   * select **Properties**.

     The Site Plan property pages open. 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-4222141f09b2c27a49de6a438daa0cd75aa425b9%2Fexistingsp_properties.png?alt=media)

     or:
   * select **View in New Window**.

     The Site Plan opens in "View" mode if it is a legacy Site Plan, (i.e. created in Configuration Client).

     If the Site Plan was created in Command Centre Client, the following message will display:

     *"This site plan is edited or viewed in the Command Centre Client"*

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

     **Note:**

     For further detail and a description of the Toolbar buttons on a Site Plan, see [Site Plan "Edit" and "View" modes](https://help.security.gallagher.com/knowledge-hub/configuration-client/site-installation/site-plans/site-plan-quot-edit-quot-and-quot-view-quot-modes.md).

### Hints

{% hint style="info" %}
**"Edit" and "View" mode**

By clicking the "Site Plan editing mode" ![](https://3000903572-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FfCvaxj3suxNBzdwQndVT%2Fuploads%2Fgit-blob-51cc461b0e8b4f0bbc61fdd5d00eee40ff63cf28%2Fediticon.png?alt=media) button you can change back and forth between "Edit" and "View" mode.
{% endhint %}

{% hint style="info" %}
**Sizing and Positioning Site Plans**

The size and position of a Site Plan can be altered to suit your purposes. The position of a Site Plan can be altered by clicking on the title bar, holding down the mouse button and then dragging it to the desired position. To resize a Site Plan window, see [Sizing the windows](https://help.security.gallagher.com/knowledge-hub/configuration-client/introduction-to-command-centre/knowing-your-way-around/list-windows/sizing-the-windows.md) for the procedure.

These settings will be saved by the system for your logon only, (i.e. the size and position of a Site Plan saved by one operator will not affect another operator).

**Note:** Resizing a Site Plan scales the icons relative to the size of the Site Plan, and the percentage in the "Icon Scaling" field alters accordingly.
{% 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-monitoring/site-plans/viewing-an-existing-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.
