> 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/understanding-macros.md).

# Understanding Macros

Macros can be created for scheduling a set of pre-programmed *overrides\** or for scheduling a bulk change. Macros provide the ability to group and schedule them for a specific time and for specific durations, either on a one-off basis or for events that repeat on a daily or weekly basis.

Such overrides would cater for special after-hours events that require changes to the normal security settings for the site. For an after-hours event, an area, (e.g. a conference venue), must be set to free access, and the associated Alarm Zone disarmed for the duration of the event. It may also require switching lights or air-conditioning on for the duration of the event, and it is not convenient to have an operator on-site to perform these overrides at the required time.

For some sites, some pre-programmed overrides may be a repeating event, (e.g. a class held every Tuesday evening for 10 weeks).

{% hint style="info" %}
**\*Overrides**

Overrides enable an operator to temporarily change the status of an item attached to their Command Centre system. They enable operators to respond to common, random events, (e.g. temporarily unlock a door to give access to a cardholder who has forgotten their card).
{% 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/understanding-macros.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.
