> 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/recommended-site-configuration-process.md).

# Recommended Site Configuration Process

### Introduction

The following process should be followed to ensure that each activity is performed in the correct order when setting up your site, and therefore the relationships between the various entities in Command Centre are maintained.

This process refers to separate step-by-step procedures which are either detailed in this section, or other sections as indicated.

### Before you begin

Before you get to the Command Centre installation process, it is advised that formal design work for the site has been completed, and is available to use as a configuration guide.

### Process

1. Although not necessary, it is advisable to ensure that all the equipment has been physically installed on site, according to the design specification for the site, and as instructed in the "Gallagher Installation Manual" (Part No. C209100).
2. Install Command Centre.

   (See the Command Centre Release Note for a description of the options and the installation procedure.)
3. Log on to Command Centre, and set up your system password.

   (See [Getting Started](https://help.security.gallagher.com/knowledge-hub/configuration-client/introduction-to-command-centre/getting-started.md) for procedure.)
4. Set up System Divisions.

   (See [Setting up System Divisions](https://help.security.gallagher.com/knowledge-hub/configuration-client/site-installation/system-division/setting-up-system-divisions.md) for procedure.)

   **Note:**

   As an alternative to following the rest of this procedure, there are configuration wizards available. These wizards help simplify the process for configuring some basic Command Centre settings, hardware devices, doors, cards and cardholders. See [Wizards](https://help.security.gallagher.com/knowledge-hub/configuration-client/site-installation/setting-up-your-site/wizards.md) for further details.
5. Rename the "Default Day Category", (e.g. Weekdays), and create one additional Day Category, (e.g. Weekends).

   (See [Day Categories](https://help.security.gallagher.com/knowledge-hub/configuration-client/site-installation/day-categories.md) for procedure.)
6. Create [Calendar Days](https://help.security.gallagher.com/knowledge-hub/configuration-client/site-installation/calendars.md).
7. Create Card Types and Facility Codes (see [Setting up Card Types](https://help.security.gallagher.com/knowledge-hub/configuration-client/site-installation/card-types/setting-up-card-types.md) for procedure), and create a Crypt Seed (see [Server Properties](https://help.security.gallagher.com/knowledge-hub/configuration-client/site-installation/server-properties.md) for procedure).

   **Note:** Depending on the license file the Crypt Seed may be present already.
8. Create a Cardholder, and make it part of the System Division you created in Step 4.

   (See [Adding a new Cardholder](https://help.security.gallagher.com/knowledge-hub/configuration-client/site-management/cardholders/adding-a-new-cardholder.md) for procedure.)
9. Create an Operator Group with the advanced privilege and put your new Cardholder into this group.

   (See [Operator Groups](https://help.security.gallagher.com/knowledge-hub/configuration-client/site-management/operator-groups.md) for procedure.)
10. Log off the system and log on the new user.

    This will make all items that are created in the new division, which saves time and prevents mistakes with the operator forgetting to change the division.
11. Configure the hardware.
12. Create [Schedules](https://help.security.gallagher.com/knowledge-hub/configuration-client/site-installation/schedules.md).
13. Create an Alarm Zone for all the devices. Give the Alarm Zone a meaningful name like "AZ for all h/w on Controller#1".

    (See [Alarm Zones](https://help.security.gallagher.com/knowledge-hub/configuration-client/site-installation/alarm-zones.md) for procedure.)
14. Get the Controller online, i.e. ensure the Controller has an IP address (2 flashes on Red LED), and put this IP address in the **Advanced** tab of the Controller Properties screen. (See [Creating Controllers](https://help.security.gallagher.com/knowledge-hub/configuration-client/site-installation/hardware/creating-controllers.md).)
15. Once the Controller is in the 1Hz flash mode, assign the Alarm Zone you created for the Controller and hardware in Step 13, in the **Event Response** tab of the Controller Properties screen.
16. Link the devices to the Controller.

    (See [Linking devices to Controllers](https://help.security.gallagher.com/knowledge-hub/configuration-client/site-installation/hardware/linking-devices-to-controllers.md).)

    As each device is assigned to the Controller, assign it the Alarm Zone created in Step 13.

    Continue this step until all the hardware is linked.

    **Note:**

    For each new Controller created, create a new Alarm Zone specific to that Controller.
17. [Create Doors](https://help.security.gallagher.com/knowledge-hub/configuration-client/site-installation/doors/creating-doors.md) ensuring they are in the same Alarm Zone as the Controller Hardware.
18. [Create Inputs and Outputs](https://help.security.gallagher.com/knowledge-hub/configuration-client/site-installation/hardware/creating-inputs-and-outputs.md).
19. [Link the Inputs and Outputs to devices](https://help.security.gallagher.com/knowledge-hub/configuration-client/site-installation/hardware/linking-inputs-and-outputs-to-devices.md).
20. Create any additional Schedules (see [Schedules](https://help.security.gallagher.com/knowledge-hub/configuration-client/site-installation/schedules.md) for procedure).
21. Create [Access Zones](https://help.security.gallagher.com/knowledge-hub/configuration-client/site-installation/access-zones.md).

    Temporarily give the access zone a schedule set to free during install. This will help with commissioning the site.
22. Setup [Cardholders](https://help.security.gallagher.com/knowledge-hub/configuration-client/site-management/cardholders/adding-a-new-cardholder.md).
23. Setup [Access Groups](https://help.security.gallagher.com/knowledge-hub/configuration-client/site-management/access-groups.md).
24. Once you have tested that everything is working, (i.e. alarms and events, schedule door control, etc.), create [Site Plans](https://help.security.gallagher.com/knowledge-hub/configuration-client/site-installation/site-plans.md).
25. Setup [Action Plans](https://help.security.gallagher.com/knowledge-hub/configuration-client/site-installation/action-plans.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/recommended-site-configuration-process.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.
