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

# Understanding System Division

System Division allows one site to be divided into smaller divisions and sub-divisions. Each sub-division can manage their own security needs. It is especially desirable for:

* multi-tenanted buildings where each tenant wishes to manage and monitor their own security
* very large enterprise-wide systems where it is more practical to divide the site up for ongoing management and monitoring, (e.g. dividing the site up into geographic zones).

Your site license will determine the number of divisions you can have.

### Operators and Divisions

Operators are only able to view, manage and report on the components in their division, in line with their operator privileges. Generally, they do not have access to components in other divisions except in certain situations, (e.g. enabling cardholders to have access through a shared foyer area in a multi-tenanted building). See [Cardholder Management across Divisions](https://help.security.gallagher.com/knowledge-hub/configuration-client/site-installation/system-division/cardholder-management-across-divisions.md) for further detail.

With the "Select System View" privilege an operator is able to restrict their view of the system. When they logon to Command Centre their system view selection, retained from their last logoff, displays in the **System view** field on the main window. See [Restricting System View](https://help.security.gallagher.com/knowledge-hub/configuration-client/introduction-to-command-centre/getting-started/restricting-system-view.md) for further details.

![](https://3000903572-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FfCvaxj3suxNBzdwQndVT%2Fuploads%2Fgit-blob-5fddf15a560364420b5b32e1979d0d5f0644cd21%2Fmainmenu.png?alt=media)

Refer to [Operator Privileges](https://help.security.gallagher.com/knowledge-hub/configuration-client/site-management/operator-privileges.md) to check you have the correct operator privilege level for working with Divisions.

### Creating new items

When creating new items, the last division an operator used for creating or saving an item would normally populate the **Division** field. However, if the operator's last used division is not available, then by default the system will select the highest division that the operator has access to. If there is more than one division at the same level, then the system will select the division which was created first.


---

# 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/understanding-system-division.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.
