> 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/system-division/setting-up-system-divisions.md).

# Setting up System Divisions

### Introduction

Entities that can be divided include:

* Cardholders
* Access Groups
* Site Items, e.g. doors, relays, alarm zones
* Reports
* Action Plans
* Operators and Workstations
* Calendars

The "Configure Site" or "Edit Divisions" operator privilege is required to set up divisions.

**Notes:**

* It is important that any divisions are formalised prior to the commencement of configuration work.
* Your site license will determine the number of divisions you can have, therefore once you have added all you are allowed, the option to create more will be disabled.

### Procedure

1. Click **Configure** from the menu bar, then **Divisions**.

   The **Division** List Window opens (in [tree view](https://help.security.gallagher.com/knowledge-hub/configuration-client/introduction-to-command-centre/knowing-your-way-around/list-windows/tree-view.md)).
2. **Right click** and select **New\...Division**.

   By default the **General** tab displays.
3. Complete the fields as required.

   For further detail see [General tab](https://help.security.gallagher.com/knowledge-hub/configuration-client/introduction-to-command-centre/knowing-your-way-around/generic-properties-configuration/general-tab.md).
4. Click the **Lineage** tab.

   ![](https://3000903572-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FfCvaxj3suxNBzdwQndVT%2Fuploads%2Fgit-blob-f7bd05d476efd7baf4ea67e88f202ce461e6a03b%2Fdivlineage.png?alt=media)
5. Select the "Immediate Parent" division from the drop-down list.
6. Click the **Custom Fields** tab if you want to add and assign a custom field value to this division.

   For further details regarding the **Custom Fields** tab, see [Custom Fields](https://help.security.gallagher.com/knowledge-hub/configuration-client/site-installation/server-properties/custom-fields.md).
7. Click the **Notes** tab if you want to add a note(s) about this division.

   For further details regarding the **Notes** tab, see [Notes](https://help.security.gallagher.com/knowledge-hub/configuration-client/site-installation/server-properties/notes.md).
8. Click **OK** to exit and save your changes.

   Click **Cancel** to exit without saving your changes.

   Click **Apply** to save your changes and stay in this window.

### Result

A new system division is created.

**Note:**

This new Division defaults into the "Immediate Children" box on the Lineage tab of the Division you selected as the "Immediate Parent".


---

# 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/system-division/setting-up-system-divisions.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.
