> 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/site-monitoring/status-and-overrides/adding-items-to-the-status-viewer.md).

# Adding items to the Status Viewer

### Introduction

You can easily add items to the Status Viewer.

**Note:**

Any item that has a **Status and Overrides** tab in its properties can be added to the Status Viewer, along with Archives, Macros and Bulk Changes.

### Procedure

*Drag and Drop method:*

1. Click **Monitor** from the menu bar, then **View Status**.

   The **Status** Viewer opens.
2. Open the List Window that contains the item whose status you want to see.

   For example, open the **Hardware** List Window.
3. Locate the required item.
4. Drag and drop this item into the **Status** Viewer.

   For example, drag Hardware item "H/O Controller 6000" into the **Status** Viewer.

*Copy and Paste method:*

1. Open the List Window that contains the item whose status you want to see.
2. **Right click** the required item.
3. Click **Copy**.
4. Click **Monitor** from the menu bar, then **View Status**.

   The **Status** Viewer opens.
5. **Right click** and click **Paste**.

### Result

Item is added to the Status list.

**Note:**

Command Centre will only save 100 items to one Status pane. If you try to add more than 100, an error message will display.

### Hint

{% hint style="info" %}
You can select multiple items and drag them into the Viewer. Refer to "[Selecting items in a list](https://help.security.gallagher.com/knowledge-hub/configuration-client/introduction-to-command-centre/knowing-your-way-around/list-windows/grid-view/selecting-items-within-the-displayed-list.md)".
{% 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/site-monitoring/status-and-overrides/adding-items-to-the-status-viewer.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.
