> 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-installation/action-plans/assigning-action-plans-to-events.md).

# Assigning Action Plans to Events

### Introduction

Action Plans are linked to system events, and can be assigned to any item that has an **Event Response** tab.

The following procedure describes how to assign Action Plans to Doors. This same procedure is used to assign Action Plans to the other items mentioned above. The only difference is at Step 2, where you select the appropriate item.

### Procedure

1. Click **Configure** from the menu bar, then **Doors**.

   The **Door** List Window opens (in [grid view](https://help.security.gallagher.com/knowledge-hub/configuration-client/introduction-to-command-centre/knowing-your-way-around/list-windows/grid-view.md)).
2. **Right click** on the required Door, and select **Properties**.
3. Click the **Event Response** tab.
4. Highlight the Event Group that you wish to assign an Action Plan to.

   The edit box is then enabled.
5. Click the drop-down menu box and select the required Action Plan.

   ![](https://3000903572-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FfCvaxj3suxNBzdwQndVT%2Fuploads%2Fgit-blob-d007ae83715534fe2d1d4805cd9b6d3d6bb9ff7d%2Fassignap.png?alt=media)
6. Repeat Steps 4 - 5 as necessary.
7. Click **OK** to exit and save your changes.

   Click **Cancel** to exit without saving your changes.

   Click **Apply** to save your changes and stay in this window.

### Result

Action Plans are now assigned to a Door.


---

# 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-installation/action-plans/assigning-action-plans-to-events.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.
