> 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/editing-removing-actions-for-a-macro.md).

# Editing/Removing Actions for a Macro

This procedure details how to edit or remove 'Actions' for a Macro.

1. Click on the Macro you want to edit from the list in the Viewer Navigation Panel.

   The properties for that Macro populate the Viewer Panel.
2. Click the **Actions** tab, if not already displayed.
3. Do you want to edit or remove an Action?

   <table><thead><tr><th width="90">If...</th><th>then...</th></tr></thead><tbody><tr><td>edit</td><td><ol><li>Select the item in the list and click the <strong>Configure Actions</strong> button.<br>The Configure Actions pop-up displays.</li><li>Select another override action from the <strong>Action</strong> drop-down list.</li><li>Click the <strong>OK</strong> button.<br>The <strong>Actions</strong> column populates with the new override action for that item.</li></ol></td></tr><tr><td>remove</td><td>select the item in the list and click the <strong>Remove</strong> button.</td></tr></tbody></table>
4. Repeat Step 3 if there are other Actions you want to edit or remove.
5. Click the **Save** button.

   The appropriate Action(s) have been edited or removed for the Macro.


---

# 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/editing-removing-actions-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.
