> 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/creating-a-new-macro/actions-tab.md).

# Actions tab

This procedure describes the configuration on the **Actions** tab for a Macro.

1. Click the **Actions** tab.

   ![](https://2455150842-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fi6UYAoyykM6nimMN9yss%2Fuploads%2Fgit-blob-06dacec4da06ff9956517538f1f6350532b2472a%2Fmacro_actionstab.png?alt=media)

   This tab allows you to add Command Centre item(s) that you want to perform actions on for this macro.

   **Note:** Only Command Centre items that can be supported by macros, and to which you have the correct privilege(s), can be added to this section, (i.e. Outputs, Access Zones, Alarm Zones, Interlock Groups, Logic Blocks, Doors, Bulk Changes, Guard Tours, Controllers, Fence Zones, Macros, Morpho Biometric Readers, Workstations, Command Centre Access Reports, Evacuation Reports, Configuration Client Exception Reports, Activity Reports, Configuration Client Guard Tour Reports, Cardholder Reports, Command Centre Time Reports, Command Centre Voltage Reports and Z10 Tension Sensor Groups).
2. Click the **Add Items** button.

   A browse tool displays.

   ![](https://2455150842-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fi6UYAoyykM6nimMN9yss%2Fuploads%2Fgit-blob-54f1c8118fd0abb498389afbf71d2d03d614e20e%2Faddactionitems_popup.png?alt=media)
3. If necessary, search for the item(s) you want by entering characters in the Search field and/or refining the search mode and filters.

   The grid becomes populated with items that match the search criteria.
4. Click the checkbox next to each item name you want to include, or click the **Select All** button if you want to include all items.
5. Click the **Add Selection** button.

   The pop-up closes and each of the selected item(s) appear in the **Items** grid.

   **Note:** To remove an item, select (highlight) the item you want to remove and click the **Remove** button.
6. These Command Centre items need to have actions configured for them.

   Select the first item in the list and click the **Configure Actions** button.

   A Configure Actions pop-up displays.

   ![](https://2455150842-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fi6UYAoyykM6nimMN9yss%2Fuploads%2Fgit-blob-38a382cecb26a1330ae6b991cd32522f4509223f%2Fconfigureactions4macro_popup.png?alt=media)

   **Note:** The options available on this pop-up depend on the type of Command Centre item. This example is for an Alarm Zone.
7. Configure actions as required, and click the **OK** button.

   The pop-up closes and details of the currently configured action for that item populate the **Actions** column for the item.

   **Notes:**

   * Some items only support one action, (e.g. for doors you can "Open Door", for bulk changes you can "Run Bulk Change", and for Controllers you can "Re-sync Databases"). However, for items that support more than one action, (e.g. items supporting override actions), then the default action is "None Selected".
   * For Alarm Zones, the **Alarm Processing** drop-down list (as shown on the above screen) only displays if you have the "Bulk Process Alarms" privilege. By selecting "Acknowledge all alarms" or "Process All the Alarms", all existing alarms for the Alarm Zone will be acknowledged or processed, respectively. By selecting "Auto-Acknowledge All the Alarms", all subsequent alarms for the zone will be auto-acknowledged, up until the point where all alarms on the zone have been processed.

     **IMPORTANT:** These options bypass both mandatory alarm notes and the option to disallow an operator from processing escalated alarms.
   * For Evacuation, Exception, Activity, Cardholder and Guard Tour Reports the settings that have been saved for the report display. These settings can be changed (if you have the operator privilege to edit the report in the report's Division), by right clicking on the Report in the **Name** grid and selecting **Properties**.
   * For Exception, Activity, Cardholder and Guard Tour Reports, you need to select the report in the **Name** grid in order for its Division to be selected automatically.
8. Return to Step 6 of [Creating a new Macro](https://help.security.gallagher.com/knowledge-hub/command-centre-client/configuring-command-centre/administration/macros/creating-a-new-macro.md) for configuration instructions for the other Macro tabs.


---

# 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/creating-a-new-macro/actions-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.
