> 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/configuring-command-centre/viewer-configuration-overall-process/quick-tips-for-configuration.md).

# Quick Tips for Configuration

* The Configuration Navigation Panel down the left hand side displays all Viewers that you have the privileges to either edit, or view the configuration for. Viewers with unsaved changes will be in **bold** and have a **\*** at the end of their name.
* The Cardholder Viewer is not designed to be used at resolutions with a height of less than 768. However, if using a Cardholder Viewer for view only purposes, then any resolution can be used.
* The floating 'Tile Toolbox' contains an alphabetical list of the tile types that can be added to the type of Viewer you are configuring. The Toolbox can be re-positioned anywhere within the panel layout area by clicking on it and dragging it. It can also be minimised so that only the header displays.
* Tiles should not be configured on top of each other or overlapping, with the exception of the Camera Tile which will always be on top.


---

# 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/configuring-command-centre/viewer-configuration-overall-process/quick-tips-for-configuration.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.
