> 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/creating-a-rule.md).

# Creating a Rule on an Event Viewer Navigation Panel

1. Click the **Create Rule** button.

   The New Rule Definition pop-up opens.

   ![](https://2455150842-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fi6UYAoyykM6nimMN9yss%2Fuploads%2Fgit-blob-299f8e7490fa2e82e21d6e5b3bacbe17306b176b%2Fnewruledefinition_popup.png?alt=media)
2. Select the Event Source, as follows:

   1. Click the **\<not filtered>** button.

      A browse tool displays.

      ![](https://2455150842-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fi6UYAoyykM6nimMN9yss%2Fuploads%2Fgit-blob-36105f1ef86785e94063ff8fd9692bf6684ff68f%2Fselecteventsource_popup.png?alt=media)
   2. Search for the item you want to use as an Event Source by entering search criteria in the **Search** field and/or refining the filters.

      The grid becomes populated with items that match the search criteria.
   3. Click the radio button next to the item name you want to use.
   4. Click the **OK** button.

      The pop-up closes and the **\<not filtered>** button changes to the name of the item you selected.

   **Note:** The **Reset** button allows you to reset the Event Source selection to \<not filtered>.
3. Select the required **Event Group** from the drop-down list.

   The **Event Type** drop-down list is populated with the Event Types applicable for the selected Event Group.
4. Select the required **Event Type** from the drop-down list.
5. Assign the Panel for the Event by clicking the appropriate radio button:

   <table><thead><tr><th width="193">If you click...</th><th>then...</th></tr></thead><tbody><tr><td>Choosing an existing panel</td><td>select the required Panel from the drop-down list.</td></tr><tr><td>Copying a Panel</td><td>select the Panel you want to copy from the drop-down list, and enter a name for the Panel to copy to.</td></tr><tr><td>Creating a new Panel</td><td>enter a name for the new Panel.</td></tr></tbody></table>
6. Click the **OK** button.

   The **New Rule Definition** pop-up closes, and the new entry appears in the grid.


---

# 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/creating-a-rule.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.
