> 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/introduction-to-command-centre/knowing-your-way-around/generic-properties-configuration/event-response-tab.md).

# Event Response tab

Items that support event reporting include an **Event Response** tab in their Properties window as the second tab in the name tabs area. This tab allows you to individually link site item events to Action Plans. All the Event Groups and Types available for that particular item are listed as a tree so that each individual Event Type can have a different Action Plan assigned to it. If an Action Plan is not assigned at Event Type level, the Event Group Action Plan is used.

**Note:** The example screen shot below is for an HBUS Terminal, and while it will differ slightly for other items, the procedure is still the same. The 'Alarm Zone for all Events' field only appears for Controller items.

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

1. Highlight the Event Group/Type you want to assign an Action Plan to.

   The edit box is then enabled.

   **Notes:**

   * You can assign an Action Plan at an Event Group level, or at an individual Event Type. If an Action Plan is assigned to an Event Group, all Event Types in that group will default to the groups Action Plan. However, Action Plans assigned to individual Event Types override the group event.
   * It is possible to assign Action Plans to Event Types and/or Event Groups as site wide default settings. See [Event Defaults](https://help.security.gallagher.com/knowledge-hub/configuration-client/site-installation/server-properties/event-defaults.md) for further details.

   To see all the Event Types in a Group, expand the tree by clicking on the ![](https://3000903572-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FfCvaxj3suxNBzdwQndVT%2Fuploads%2Fgit-blob-dbd0910108807d606a183525e745ef58ac247709%2Ftree2.png?alt=media) icon.

   ![](https://3000903572-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FfCvaxj3suxNBzdwQndVT%2Fuploads%2Fgit-blob-e8e9e51d88479646c761bf63efb1996e75492304%2Fsampleeventresponse1.png?alt=media)
2. Click the drop-down list to display the available Action Plans, and select the required plan.

   ![](https://3000903572-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FfCvaxj3suxNBzdwQndVT%2Fuploads%2Fgit-blob-d0af4e4b79887f1084c5459449f0bb457c2dbda9%2Fsampleeventresponse3.png?alt=media)
3. Repeat Steps 1 - 2 as necessary.
4. If there is an 'Alarm Zone for all Events' field, assign a primary Alarm Zone for all events from the drop-down list.

   ![](https://3000903572-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FfCvaxj3suxNBzdwQndVT%2Fuploads%2Fgit-blob-43086ea1c6a8297119cf7fe03f82f4e37e4250e2%2Fdooraz.png?alt=media)


---

# 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/introduction-to-command-centre/knowing-your-way-around/generic-properties-configuration/event-response-tab.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.
