> 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-the-viewer-navigation-panel/event-viewer/quick-tips-for-configuring-panels.md).

# Quick Tips for configuring Panels

The "Panel Rules" grid on the Event Viewer Configuration pop-up allows you to determine what tiles are displayed and populated when an Event is selected from within the Navigation Panel. By configuring specific panel rules to meet certain criteria, you can create a view with the appropriate tiles relevant to the scenario for an event.

* New Event Viewers are created with one default rule, (i.e. "Default Panel"), therefore all Event Viewers will have this panel. This default panel is the catch-all rule that will be applied for Events that do not have a specific rule defined for their Event Source, Group and Type.
* The default panel cannot be deleted, but an alternative panel can be assigned.
* If no additional panels are configured, all events will show the default panel.
* A panel rule cannot be saved where the Event Source, Group and Type are all set to \<not filtered>, as this is effectively the same as the \<Catch-all Rule>.
* Panel names must be unique within a Viewer.
* If you have a long list of panels to work with, rather than scrolling through the list you can use the ![](https://2455150842-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fi6UYAoyykM6nimMN9yss%2Fuploads%2Fgit-blob-8d05e249c9f1da89cabcc1e491bc17f0290ad6e9%2Fexpandarrow.png?alt=media) at the right of the "Panel Rules" grid to expand it so it takes up most of the configuration pop-up.
* The rules grid can be sorted by any column. The default column sorting is by descending alphabetical Event Source.


---

# 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-the-viewer-navigation-panel/event-viewer/quick-tips-for-configuring-panels.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.
