> 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/configuration-client/site-installation/setting-up-your-site/wizards.md).

# Wizards

### Introduction

The Wizards provide a user interface to assist operators in the configuration of Command Centre. The most frequent use of the wizards will be for new site configuration, but can also be used for the addition of hardware and cardholders to existing sites.

The Wizards enable you to easily configure a number of items for your site. You step through the Wizards using the **Next** button to access each wizard page, accepting default settings or customising appropriately. The **Finish** button can be clicked at any time to create the item without stepping through each page. At any stage you can backtrack via the **Back** button, or stop the configuration process by choosing the **Cancel** button (which also exits the particular wizard without offering to save changes).

It is recommended that only one operator invoke wizards at any one time to avoid inconveniences such as duplicate name clashes.

### Operator Privileges

The Startup Wizard will only be enabled if you have the "Advanced User" operator privilege. Operators require the "Edit Site" operator privilege to run the wizards on the Configuration Wizard and wizard templates.

Operators require the "Edit Cardholder", "Modify Access Control" and "View Site" operator privileges (all in the correct division) to run the Cardholder Wizard and successfully add cardholders with cards.

This section covers the following topics:

* [Startup Wizard](https://help.security.gallagher.com/knowledge-hub/configuration-client/site-installation/setting-up-your-site/wizards/startup-wizard.md)
* [Configuration Wizard](https://help.security.gallagher.com/knowledge-hub/configuration-client/site-installation/setting-up-your-site/wizards/configuration-wizard.md)
* [Wizard Templates](https://help.security.gallagher.com/knowledge-hub/configuration-client/site-installation/setting-up-your-site/wizards/wizard-templates.md)

### In This Section

* [Startup Wizard](https://help.security.gallagher.com/knowledge-hub/configuration-client/site-installation/setting-up-your-site/wizards/startup-wizard.md)
* [Configuration Wizard](https://help.security.gallagher.com/knowledge-hub/configuration-client/site-installation/setting-up-your-site/wizards/configuration-wizard.md)
* [Wizard Templates](https://help.security.gallagher.com/knowledge-hub/configuration-client/site-installation/setting-up-your-site/wizards/wizard-templates.md)


---

# 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/configuration-client/site-installation/setting-up-your-site/wizards.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.
