> 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/command-centre-client/using-command-centre/working-with-viewers/site-plan-viewer/embedded-site-plans.md).

# Embedded Site Plans

Embedded Site Plans display on a Site Plan Viewer either:

* out of focus, (i.e. as a bordered shape) or
* in focus, (i.e. displaying the embedded Site Plan detail)

**Note:** Site Plans can only be embedded onto other Site Plans of the ‘Site Map’ type.

If there are a number of embedded Site Plans on a Site Map, only one can be in focus, (i.e. the one that is closest to the centre point of the screen will be in focus, while the others will remain out of focus as a bordered shape) depending on the zoom level. However, if the embedded Site Plans are 'Site Maps' more than one can be in focus.

In the example below, **Building 3** is in focus, while **Building 1** and **Building 4** are out of focus.

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

Irrespective of whether an embedded Site Plan is in focus or not, if (at the time of being embedded) it has been configured to flash when in alarm, it will do so.

Levels of embedding can be configured by having nested embedded Site Plans, (e.g. Site Plan 3 is embedded in Site Plan 2 which is embedded in Site Plan 1).

Components of an in focus Site Plan, (e.g. Graphic Objects) may appear as summarised item(s). However, clicking the ![](https://2455150842-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fi6UYAoyykM6nimMN9yss%2Fuploads%2Fgit-blob-f56d97f1fe083c73c9db637e8c5126bf179e6d9a%2Fsiteplan_newfloorbutton.png?alt=media) **Zoom In** button reveals more detail.

Clicking on an out of focus Site Plan will move it to the centre point of the screen and zoom in to bring it in to focus.

If you have zoomed in on an embedded Site Plan, or moved the entire Site Plan around the viewer, clicking the ![](https://2455150842-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fi6UYAoyykM6nimMN9yss%2Fuploads%2Fgit-blob-7192014aa70ad2c961459b251c98401e18d68502%2Fsiteplanviewer_fittoview.png?alt=media) **Fit to View** button restores the original Site Plan view.

When a 'Building Plan' with multiple floors is in focus, the **floor selector** for the building plan will display.


---

# 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/command-centre-client/using-command-centre/working-with-viewers/site-plan-viewer/embedded-site-plans.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.
