> 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-management/operator-groups/understanding-operator-groups.md).

# Understanding Operator Groups

### Introduction

An Operator Group is a group of cardholders who are authorised to use the Command Centre software. Each Operator Group defines the privileges its members have as Command Centre operators, (e.g. view only access, editing ability, site configuration ability, etc.). The privileges only apply within the Divisions assigned to that Operator Group. Operator Groups generally represent roles that an operator can have, (e.g."Monitoring Alarms for Buildings 1 and 2").

**Note:**

An operators system view can be changed to include all, some or only one of the Operator Groups they belong to. System view is limited to the site items, cardholders, Personal Data Fields (PDFs) and operator privileges assigned to them from the selected Operator Groups. 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.

### Configuring Operator Groups

An operator needs to have the "Edit Operators" privilege in at least one Division to create and configure operators and Operator Groups.

The "Edit Operators" privilege within a Division allows an operator to create Operator Groups in that Division and assign any (or all) operator privileges to that group.

An operator configuring an Operator Group will only be able to:

* assign cardholders to the Operator Group if they have "View Cardholders" or "Edit Cardholders" privilege in the cardholder's Division.
* assign or remove Divisions configured in the Operator Group if they have "Edit Operators" privilege in that Division.
* assign or remove Personal Data Field privileges configured in the Operator Group if they have "View Personal Data Definitions" or "Edit Personal Data Definitions" privilege in the Personal Data Field's Division.

### Example: How Operator Groups work

A site's divisional hierarchy is as follows:

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

An Operator Group has the following members, Divisions and operator privileges configured:

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

This means Jo Smith and Fred Roberts can "Delete Cardholders", "Edit Cardholders", "Modify Access Control" and "Print/Preview & Encode Cards" in the "Building 1" or "Factory" Divisions. As the "Building 1" Division has three children Divisions, (i.e. Level 1, Level 2 and Level 3), they also have the same privileges for these Divisions.

### Assigning Personal Data Field Privileges

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

In the example above, Sally Smith belongs to an Operator Group that gives her "Edit" privilege to the "Address" Personal Data Field for all cardholders in Divisions C and D. This Operator Group privilege overrides the default "View" privilege. Other operators who do not have a privilege for the "Address" Personal Data Field assigned to them from one of their Operator Groups, will only be able to view the content of the "Address" Personal Data Field.

An operator inherits the Personal Data Field privileges assigned to the Operator Groups that they belong to. The PDF privileges only apply to cardholders that belong to one of the Operator Group's Divisions (as configured in the **Divisions** tab).

If an operator belongs to more than one Operator Group and each assigns a privilege for the same PDF within the same Division, then the least restrictive PDF privilege is the one they inherit. For example, if one Operator Group gives the operator "View" privilege to a Personal Data Field for cardholders in Division C, but another Operator Group gives the same operator "Edit" privileges to that Personal Data Field for cardholders in Division C, then it is the "Edit" privilege that they actually receive.

If operators do not belong to any groups that assign Personal Data Field privileges for a particular Personal Data Field, then it is the default privilege (as specified in the Personal Data Field properties) that they inherit.

An operator's Personal Data Field privileges are assigned by Division, so it is possible to allow an operator to edit a particular Personal Data Field for cardholders in one Division, but only view the same Personal Data Field for cardholders in other Divisions.

The Personal Data Field privileges are also subject to the following:

* The operator has to have at least "View Cardholders" privilege in the cardholder's Division before they can view any Personal Data Fields for that cardholder.
* The operator has to have "Edit Cardholders" privilege in the cardholder's Division before they can edit any Personal Data Fields for that cardholder.
* The cardholder has to have been assigned the Personal Data Field through one of the Access Groups that they belong to.


---

# 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-management/operator-groups/understanding-operator-groups.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.
