> 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.md).

# Creating a new Macro

Perform the following procedure to create a new Macro:

1. Click the **New Macro** button on the Viewer Navigation Panel.

   The new Macro is added to the Viewer Navigation Panel, and the Macro Configuration pop-up displays.

   ![](https://2455150842-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fi6UYAoyykM6nimMN9yss%2Fuploads%2Fgit-blob-8ec6e215b47eee6339d4cfee4009f7f6371b6e9a%2Fmacroconfig_popup.png?alt=media)
2. If you want to replace the default name the system has given the Macro, enter a new name in the **Name** field (limited to 60 characters).
3. If required, enter a logical **Description** (limited to 200 characters).
4. The **Division** button defaults to the name of the last Division in which the Operator created a Command Centre item, regardless of whether it was created in Configuration Client or via Command Centre Client.

   If this is not the appropriate Division for this Macro to be in, select a Division as follows:

   1. Click the **Division** button.

      A browse tool displays.

      ![](https://2455150842-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fi6UYAoyykM6nimMN9yss%2Fuploads%2Fgit-blob-b59df7c2a078bd54f6c17dd30b3ce00d3e5b1279%2Fselectdivisionforreport_popup.png?alt=media)
   2. Select the appropriate Division.
   3. Click the **OK** button.

      The pop-up closes and the button changes to the name of the Division you selected.

   **Note:** If you have not set up Divisions yet, you can add these to your Macro at a later stage.
5. Click the **Icons** button if you want to change the Icon Set for this Macro.

   If no selection is made, the default is selected.
6. Click the **Close** button.

   The Macro Configuration pop-up closes, displaying the five configuration tabs.

   The **Actions** tab displays by default.

   Click each tab in turn and configure the Macro properties as required:

   * [Actions tab](https://help.security.gallagher.com/knowledge-hub/command-centre-client/configuring-command-centre/administration/macros/creating-a-new-macro/actions-tab.md)
   * [Run-time Options tab](https://help.security.gallagher.com/knowledge-hub/command-centre-client/configuring-command-centre/administration/macros/creating-a-new-macro/run-time-options-tab.md)
   * [Action Plans/Alarm Instructions tab](https://help.security.gallagher.com/knowledge-hub/command-centre-client/configuring-command-centre/administration/macros/creating-a-new-macro/action-plans-alarm-instructions-tab.md)
   * [Advanced tab](https://help.security.gallagher.com/knowledge-hub/command-centre-client/configuring-command-centre/administration/macros/creating-a-new-macro/advanced-tab.md) (this tab does not display for a CAPSS site, i.e. when `NPSA=1` appears in the licence file Features section)
   * [History/Notes tab](https://help.security.gallagher.com/knowledge-hub/command-centre-client/configuring-command-centre/administration/generic-administration-tasks/history-notes-tab.md)
7. Click the **Save** button.

   A new Macro has been created to perform a number of actions quickly with minimal operator interaction. This Macro can now be placed on a Site Plan for future execution if required.

   **Note:** If the Macro contains items and actions that you do not have sufficient privileges to save, then an error message will display informing you of the disallowed items, and the changes will not be saved.

### Hints

{% hint style="info" %}
**Editing and Deleting Macros**

Refer to [Editing items](https://help.security.gallagher.com/knowledge-hub/command-centre-client/configuring-command-centre/administration/generic-administration-tasks/editing-items.md) and [Deleting items](https://help.security.gallagher.com/knowledge-hub/command-centre-client/configuring-command-centre/administration/generic-administration-tasks/deleting-items.md) for the procedure on how to edit and delete a macro.

**Note:** A macro cannot be deleted if it is on a Site Plan or is used in an Action Plan. Likewise, operators, workstations and site items that appear on a macro's **Actions** tab cannot be deleted from the system.
{% endhint %}

{% hint style="info" %}
**Duplicating Macros**

Operators privileged to create macros can also duplicate macros, which makes the task of setting up multiple macros that are very similar much quicker.

Refer to [Copying items](https://help.security.gallagher.com/knowledge-hub/command-centre-client/configuring-command-centre/administration/generic-administration-tasks/copying-items.md) for the procedure.
{% endhint %}


---

# 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.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.
