> 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/run-time-options-tab.md).

# Run-time Options tab

This procedure describes the configuration on the **Run-time Options** tab for a Macro.

1. Click the **Run-time Options** tab.

   ![](https://2455150842-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fi6UYAoyykM6nimMN9yss%2Fuploads%2Fgit-blob-cb8c5bacb144b2bf88b300e0ccd638ff7283423f%2Fmacro_runtimeoptionstab.png?alt=media)
2. If you want to schedule the macro now, see [Scheduling a Macro](https://help.security.gallagher.com/knowledge-hub/command-centre-client/configuring-command-centre/administration/macros/scheduling-a-macro.md) for a detailed procedure.
3. Check the **Operator confirmation required when run manually** checkbox if you want operators to be presented with a confirmation dialog prompt before the macro runs.

   The "Custom Confirmation text" field is enabled.

   **Note:** Confirmation dialogs only display when macros are manually-triggered by an operator.
4. Alter the custom confirmation text if you want something different from the default, (i.e. "Are you sure you want to run this macro?"), to appear on the confirmation dialog.

   **Note:** This field is limited to 200 characters, and while multiple lines are allowed, new lines take up two characters.
5. 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/run-time-options-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.
