> 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/configuring-tiles/repositioning-tiles.md).

# Repositioning Tiles

1. Move the mouse pointer to the Tile you want to reposition.
2. Click and hold down the mouse button, so that the pointer changes into ![](https://2455150842-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fi6UYAoyykM6nimMN9yss%2Fuploads%2Fgit-blob-9a22a9c3abaad50a83733ce13061eff9c201e589%2Fresposition_icon.png?alt=media).
3. Move the mouse (and hence the Tile) to the required new position.
4. Release the mouse button.

   **Notes:**

   * When a Tile is moved in proximity to a panel border or another Tile edge, cross hairs display and magnetic window snapping functionality applies, (i.e. this enables you to align Tiles perfectly with each other and with screen boundaries).
   * It is not possible for Tiles to be dragged outside the border of the panel.
   * 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/configuring-tiles/repositioning-tiles.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.
