> 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/administration/macros/event-action-plans-and-alarm-instructions-for-a-macro.md).

# Event Action Plans and Alarm Instructions for a Macro

### Introduction

This tab allows you to individually link macro related events to Action Plans, and assign Alarm Instructions to each of the Event Types and/or their Event Group.

### Procedure

1. Click on the Macro from the list in the Viewer Navigation Panel.

   The properties for that Macro populate the Viewer Panel.
2. Click the **Action Plans/Alarm Instructions** tab.

   All the Event Groups available for Macros are listed. To see the Event Types in an Event Group, click the ![](https://2455150842-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fi6UYAoyykM6nimMN9yss%2Fuploads%2Fgit-blob-65bdd58253f73d243ca718ca08533cf8ff2f68f0%2Freport_unsortedcolumnicon.png?alt=media) beside the Event Group.

   **Note:** Action Plans and Alarm Instructions can be assigned at both Event Group and Event Type level.
3. Click the Event Group/Type you want to assign an Action Plan to.

   Two buttons become available in the grid, providing the ability to change the Action Plan for the Event Group/Type.

   **Note:** 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.

   ![](https://2455150842-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fi6UYAoyykM6nimMN9yss%2Fuploads%2Fgit-blob-e58572687e7adeff7bd20cc90a3ed76931906e23%2Fap%26aitab_macros.png?alt=media)
4. Click the **Use Default** button in the Action Plan column.

   A browse tool displays, listing all the available Action Plans in alphabetical order.

   ![](https://2455150842-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fi6UYAoyykM6nimMN9yss%2Fuploads%2Fgit-blob-d00f7306b97a579ef23a42777e5dd34638de29e7%2Fselectactionplanpopup.png?alt=media)
5. Select the appropriate Action Plan, and click the **OK** button.

   The pop-up closes and the **Use Default** button changes to the name of the Action Plan you selected.
6. Repeat Steps 3 - 5 as necessary.
7. Click the Event Group/Type you want to assign an Alarm Instruction to.

   Two buttons become available in the grid, providing the ability to change the Action Plan and/or Alarm Instruction for the Event Group/Type.

   **Note:** Like Action Plans, you can assign an Alarm Instruction at an Event Group level, or at an individual Event Type. If an Alarm Instruction is assigned to an Event Group, all Event Types in that group will default to the groups Alarm Instruction. However, Alarm Instructions assigned to individual Event Types override the group event.
8. Click the **Use Default** button in the Alarm Instruction column.

   A browse tool displays, listing all the available Alarm Instructions in alphabetical order.

   ![](https://2455150842-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fi6UYAoyykM6nimMN9yss%2Fuploads%2Fgit-blob-438128f86679eccd657a287eaa08bfd7d6d4145c%2Fselectalarminstructionpopup.png?alt=media)
9. Select the appropriate Alarm Instruction, and click the **OK** button.

   The pop-up closes and the **Use Default** button changes to the name of the Alarm Instruction you selected.
10. Repeat Steps 7 - 9 as necessary.

**Note:** If you change the assignment of alarm instructions for items already in alarm, they will not show the change of alarm instruction until the workstation is logged off and on again. Any new alarms that come in will however adopt the changes straight away.


---

# 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/administration/macros/event-action-plans-and-alarm-instructions-for-a-macro.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.
