> 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/getting-started/dual-monitors.md).

# Dual Monitors

### Introduction

Command Centre supports dual monitors. If a workstation has been set up in Windows to operate with dual monitors, Command Centre acknowledges this by allowing the operator to make use of both monitors that make up the desktop.

When a window's position is saved, and the desktop comprises of dual monitors, its position is saved relative to the entire desktop area, (i.e. not relative to a particular monitor).

Operator preferences for the size and position of windows are saved on a "per operator" basis, (i.e. not on a "per operator/workstation" basis).

### Limitations

* When using Gallagher Command Centre on a multi-monitor PC, Command Centre will expand to cover the Windows Task bar when maximised.
* When Windows taskbar is set to auto-hide, Gallagher Command Centre will not allow the task bar to peek over Command Centre and the client will need to be minimised or restored to allow visibility of the task bar.

### Recommended Setup

1. From the **Control Panel**, click **Display**.
2. Click the **Change display** **settings** option.

   The recommended desktop setup for dual monitors has the Primary monitor on the left and the Secondary monitor on the right, as shown in the following screen shot:

   ![](https://2455150842-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fi6UYAoyykM6nimMN9yss%2Fuploads%2Fgit-blob-da319714040b5739320183740d9e7d9f308e7666%2Fdual_monitors.png?alt=media)
3. Select "Extend these displays" from the **Multiple displays** drop-down.
4. Click the **OK** button.


---

# 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/getting-started/dual-monitors.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.
