> 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/introduction-to-command-centre/knowing-your-way-around/list-windows/switching-between-windows.md).

# Switching between windows

### Introduction

When you have multiple Command Centre windows open, it can be confusing to find the actual window you want to view. Via the Window menu, you can quickly select the window you want.

### Procedure

1. Click **Window** from the menu bar.
2. From the displayed drop-down menu, select the title of the window that you want to be active.

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

### Result

The selected window is moved to the foreground. It is now the active window.

### Hints

{% hint style="info" %}
**Titles displayed**

The drop-down menu list only contains those window titles that are currently open and are sorted alphabetically. For example, if you have four windows open, those four window titles will be displayed in the list.

There is a maximum of 30 windows that will display in the window drop-down menu list at once. The oldest opened window is the one that is dropped off the bottom of the list.
{% endhint %}

{% hint style="info" %}
**Organising your screen**

* Close, (by clicking the ![](https://3000903572-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FfCvaxj3suxNBzdwQndVT%2Fuploads%2Fgit-blob-d30a140cb8208828297ae7f96a30bc664512c0b2%2Fclosebutton.png?alt=media) button in the top right corner), or minimise those windows you are not using.
* Resize the windows to suit.
  {% 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/introduction-to-command-centre/knowing-your-way-around/list-windows/switching-between-windows.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.
