> 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/command-centre-client/configuring-command-centre/administration/access-groups/access-groups-and-lineage.md).

# Access Groups and Lineage

Lineage is a concept concerned with the inheritance of privileges between parents and children. If you belong to an Access Group, you automatically have the privileges of its parents in the hierarchy.

A cardholder may need to belong to more than one Access Group to obtain their full access requirements, (i.e. access zones and schedules). There are also privileges assigned to Access Groups, (e.g. to escort visitors). These privileges relate to the access zones and schedules defined for that Access Group.

Child Access Groups inherit both the access requirements, (i.e. *Access Zones\** and *Schedules\*\**) and Access Group privileges, (e.g. to escort visitors) from their parent(s). The way this works is illustrated in the following example.

{% hint style="info" %}
**\*Access Zones**

A single area within a site which has controlled points of entry or exit. There may be several controlled entry or access points into an Access Zone.
{% endhint %}

{% hint style="info" %}
**\*\*Schedules**

A Schedule is a 'list of times and states that controls an item'.
{% endhint %}

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

In this example, cardholders in the 'Head Office' Access Group can lock and unlock Access Zones, as well as escort a visitor through Levels 1 & 2. They can also access the Front Door as they inherit the access rights of their immediate parent, (i.e. 'All Cardholders').

A visitor wishing to go through Levels 3, 4 & 5 however will need to be escorted by a cardholder from the 'IT Department' Access Group.

As part of the configuration of an Access Group you can configure Lineage functionality (via the **Parent** field). See [Creating a new Access Group](https://help.security.gallagher.com/knowledge-hub/command-centre-client/configuring-command-centre/administration/access-groups/creating-a-new-access-group.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/command-centre-client/configuring-command-centre/administration/access-groups/access-groups-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.
