> 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/divisions-and-lineage.md).

# Divisions and Lineage

Lineage is a concept concerned with the inheritance of privileges between parents and children, and affects two areas of Command Centre:

* Access Groups
* Divisions

The procedure for setting up Lineage is the same for both Access Groups and Divisions. However, to some degree, lineage works in opposite ways for these two areas. This topic explains how lineage works for Divisions. See [Access Groups and Lineage](https://help.security.gallagher.com/knowledge-hub/configuration-client/site-management/access-groups/access-groups-and-lineage.md) for an explanation of how it works for Access Groups.

### Inheritance of Division Privileges

Privileges in a Division come courtesy of membership of an Operator Group. As a member of an Operator Group, if you have privileges in a particular Division, you automatically have those same privileges in its child division(s).

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

In this example let's say that you belong to an Operator Group that gives "Edit Cardholders" privilege in the Corporate Services Division. This means you will also have "Edit Cardholders" privilege in the Human Resources and Payroll Divisions (because they are child Divisions of the Corporate Services Division).

You would not have "Edit Cardholders" privilege in either the Accounts or Marketing Divisions as they are at the same level in the hierarchy to the Corporate Services Division.

**Notes:**

* Take notice of the **Root Division** in the above example. If you belong to an Operator Group that gives a privilege in the Root Division, you have this privilege in every Division (as every Division is a child of the Root Division).
* The **Division** List Window displays 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), which is achieved via the **Lineage** tab when you set up System Divisions.

As part of the configuration of a Division you can configure Lineage functionality. See [Setting up System Divisions](https://help.security.gallagher.com/knowledge-hub/configuration-client/site-installation/system-division/setting-up-system-divisions.md) for the procedure.


---

# 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/divisions-and-lineage.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.
