> 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/using-command-centre/working-with-viewers/event-viewer/expanding-the-event-list.md).

# Expanding the Event List

Configuring the Event list at the top or bottom of the Viewer allows you to see a reasonable number of columns for each event but not many Events in one go, which could be frustrating for sites with a lot of Events. Therefore, to allow an operator to manually expand/maximise the Event List, a button in the middle of the Panel facing edge of the Event List Navigation Panel (see example below) has been provided.

![](https://2455150842-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fi6UYAoyykM6nimMN9yss%2Fuploads%2Fgit-blob-beab7aa0409fa18eb5b634d85544cc5d316e7246%2Feventviewerlist.png?alt=media)

When the List is maximised the button will change to point in the other direction to indicate the Event List can be returned to its original size.

If the Event List has been expanded, it will only return to normal size when you click the button to revert to normal size. When the list reverts to normal size the button will change back to its expand/maximise state.


---

# 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/using-command-centre/working-with-viewers/event-viewer/expanding-the-event-list.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.
