> 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/setting-up-operator-groups.md).

# Setting up Operator Groups

### Introduction

This procedure is split into two parts, as follows:

* Creating an Operator Group,

  (i.e. providing the minimum information required to create a new Operator Group)
* Configuring an Operator Group,

  (i.e. linking the various components to it - Divisions, Privileges, Cardholders and Personal Data Fields are the components of an Operator Group).

You can create a new Operator Group, then configure it at a later stage, once you have set up the necessary components for it.

***

### Configuration

#### Create the Operator Group

1. Click **Manage** from the menu bar, then **Operator Groups**.

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

   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).

   **Note:** The Operator Group's Division controls which operators can view or edit the Operator Group. It does not affect which Divisions the privileges in this group apply to.
4. Click the **Apply** button, and the Operator Group is created.

   The rest of this procedure allows you to fully configure the Operator Group.

#### Configure the Operator Group

5. Ensure the following components have already been set up:

   *Divisions*

   Refer to "[Setting up System Division](https://help.security.gallagher.com/knowledge-hub/configuration-client/site-installation/system-division/setting-up-system-divisions.md)".

   *Cardholders*

   Refer to "[Add new cardholder](https://help.security.gallagher.com/knowledge-hub/configuration-client/site-management/cardholders/adding-a-new-cardholder.md)".

   *Personal Data Fields*

   Refer to "[Creating a new Personal Data Field](https://help.security.gallagher.com/knowledge-hub/configuration-client/site-management/personal-data-fields/creating-a-new-personal-data-field.md)".
6. Click each tab in turn to configure the Operator Group:

<details>

<summary>Operator Membership tab</summary>

1. Click the **Operator Membership** tab.
2. Click **Manage** from the menu bar, then **Cardholders**.

   The **Cardholder** List Window opens.
3. Select those cardholder(s) to belong to the new Operator Group.

   Drag and drop them into the **Operator Membership** tab.

   ![](https://3000903572-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FfCvaxj3suxNBzdwQndVT%2Fuploads%2Fgit-blob-100997e6a89955166b361b03a644b98d3f26b835%2Fchintoog.png?alt=media)
4. Close the **Cardholder** List Window.
5. If there are any Service Principals you want to belong to this Operator Group also, click **Manage** from the menu bar, then **Service Principals**.

   The **Service Principal** List Window opens.
6. Select those Service Principal(s) to belong to the new Operator Group.

   Drag and drop then into the **Operator Membership** tab.
7. Close the **Service Principal** List Window.

</details>

<details>

<summary>Divisions tab</summary>

1. Click the **Divisions** tab.

   This tab dictates where you can use the operator privileges you select for this group (in Step 15). By default, the Division automatically assigned on the **General** tab is assigned to this tab also.

   ![](https://3000903572-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FfCvaxj3suxNBzdwQndVT%2Fuploads%2Fgit-blob-21d2f5dc732d1907e71da6114095d44ea3aeab15%2Fogdivisions.png?alt=media)
2. Do you require the privileges assigned to this group to apply to **all** Divisions?

   <table><thead><tr><th width="73">If...</th><th>then...</th></tr></thead><tbody><tr><td>yes</td><td>leave the "Root Division" in the grid, as all other Divisions will be included with it.<br>Go to the next tab.</td></tr><tr><td>no</td><td>right click on the "Root Division" and select <strong>Remove from List</strong>.</td></tr></tbody></table>
3. Click **Configure** from the menu bar, then **Divisions**.

   The **Division** List Window opens.
4. Select those Division(s) this Operator Group conveys privileges for.

   Drag and drop them into the **Divisions** tab.

   **Note:**

   If a Division is selected, its child(ren) Divisions are automatically included also.

   ![](https://3000903572-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FfCvaxj3suxNBzdwQndVT%2Fuploads%2Fgit-blob-1660fa20d89fe23432d5251edbb2c1fa1cd17cde%2Fdivisions_into_og.png?alt=media)
5. Close the **Division** List Window.

</details>

<details>

<summary>Operator Privileges tab</summary>

1. Click the **Operator Privileges** tab.
2. Click **Manage** from the menu bar, then **Operator Privileges**.

   The **Operator Privileges** List Window opens.

   Select those privileges appropriate for this Operator Group.

   Drag and drop them into the **Operator Privileges** tab.

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

   **Note:**

   Operators may end up without the privileges required to see their own operator events. This happens when the Division used for events is different to the Division used to change items.
3. Close the **Operator Privileges** List Window.

</details>

<details>

<summary>Configuration tab</summary>

1. Click the **Configuration** tab.

   ![](https://3000903572-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FfCvaxj3suxNBzdwQndVT%2Fuploads%2Fgit-blob-cc461b5989541538774abc0f1ce1c25797a09240%2Fogconfig.png?alt=media)
2. Do you wish to alter the behaviour of the Alarm Viewer window?

   <table><thead><tr><th width="73">If...</th><th>then...</th></tr></thead><tbody><tr><td>yes</td><td>Check the <strong>Alarm Viewer Configuration</strong> checkbox.<br>Go to Step 3.</td></tr><tr><td>no</td><td>Leave the <strong>Alarm Viewer Configuration</strong> checkbox unchecked.<br>Go to Step 4.<br><br><strong>Note:</strong> By leaving the checkbox unchecked, the Alarm Viewer will remain wherever it is placed by the currently logged on operator and will not automatically pop to the front of other windows.</td></tr></tbody></table>
3. Click the appropriate radio button for the option you prefer.

   **Automatically displays on alarm occurrence**

   The Alarm Viewer will be opened, made visible and brought to the front of all other windows on the occurrence of any new alarm.

   With this option enabled you can not locate the Alarm Viewer off screen and the entire Alarm Viewer will be visible at all times.

   **Always on top**

   The Alarm Viewer will always be in front of all other windows.

   With this option enabled the entire Alarm Viewer will be visible at all times and you can not:

   * minimise the Alarm Viewer, or
   * locate the Alarm Viewer off screen.
4. The **Escalated Alarm Options** section of this screen allows you to set what will happen to escalated alarms.

   **Note:** The Escalated Alarm Viewer privileges are conveyed via an Operator Group, but are intended to be applied system-wide for an operator, (i.e. they are not divisionally based like most other privileges conveyed via an Operator Group). Hence, disabling the Operator Group from your system view will not affect these settings, (e.g. An operator belongs to multiple Operator Groups, all with different escalated alarm option settings. If the operator narrows their system view to one Operator Group whose settings do not enable the Escalated Alarm Viewer, it will ignore that and still display the Escalated Alarm Viewer if one of the Operator Groups has that setting checked).

   Do you want escalated alarms to display in a separate window from the main Alarm Viewer?

   <table><thead><tr><th width="73">If...</th><th>then check the...</th></tr></thead><tbody><tr><td>yes</td><td><strong>Enable Escalated Alarm Viewer</strong> checkbox. The Escalated Alarm Viewer will be accessible from the <strong>Monitor</strong> menu, along with the main Alarm Viewer.</td></tr><tr><td>no</td><td><strong>Leave escalated alarms in main Alarm Viewer</strong> checkbox. Any escalated alarms will remain in the main Alarm Viewer with non-escalated alarms.</td></tr></tbody></table>

   **Note:** By checking both options you can have escalated alarms appear in both the main Alarm Viewer as well as the Escalated Alarm Viewer.
5. Check the **Do not allow operator to acknowledge or process escalated alarms** checkbox if required for operators in this group.

   **Note:** If checked, the **Acknowledge** and **Process** buttons will be disabled on the Alarm Details property page for escalated alarms.
6. Do you wish to configure alarm note options?

   If **no**, then go to the next tab.

   If **yes**, then click the appropriate radio button for the option you require.

   **Optional** *(Option A)*

   The privileged operator can optionally select alarm note(s) before processing or acknowledging an alarm.

   **Required when processing alarms** *(Option B)*

   The privileged operator must select one or more alarm notes in order to process, or bulk process alarms at a priority level that is equal to or higher than the alarm notes priority threshold.

   **Required when acknowledging or processing alarms** *(Option C)*

   The privileged operator must select one or more alarm notes in order to acknowledge, process or bulk process alarms at a priority level that is equal to or higher than the alarm notes priority threshold.

   **Notes:**

   * Where an alarm monitoring operator is a member of more than one Operator Group then the following rules apply:

     1. IF at least one Operator Group to which the operator belongs is set to *Option A*, THEN alarm notes are optional to Acknowledge, Process or Bulk Process.
     2. IF at least one Operator Group to which the operator belongs is set to *Option B*, THEN alarm notes are mandatory to Process or Bulk Process and optional to Acknowledge.
     3. IF all Operator Groups to which the operator belongs are set to *Option C*, THEN alarm notes are mandatory to Acknowledge, Process or Bulk Process.

     These rules are given in order of precedence, therefore an operator that belongs to three operator groups each of which has a different option setting *(A, B, C)* will not be forced to enter alarm notes for any alarms since Rule 1 takes precedence over Rule 2 and Rule 3. This is based on the assumption that an operator that is forced to enter alarm notes is likely to have been given this restriction because they are considered to be less reliable than those who are not forced.
   * If none or only one alarm note has been configured in the Server properties, then the 'Alarm Notes' option will not be enabled.

</details>

<details>

<summary>Personal Data tab</summary>

1. Click the **Personal Data** tab.

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

   By default, this tab will not be populated with any [*Personal Data Fields (PDFs*](https://help.security.gallagher.com/knowledge-hub/configuration-client/glossary-of-terms.md#pdf-personal-data-field)*\_\_)*. Instead, this Operator Group will get the privileges for PDFs that are assigned at the PDF level. If you want to override the default privilege to something else, you can drag PDFs onto this tab.

   The level of operator privilege to view or edit cardholder information stored in a cardholder's Personal Data is determined for individual PDFs. The PDF privileges only apply to cardholders in the Operator Group's Divisions (as configured on the **Divisions** tab).

   The default operator privilege for each PDF is determined when the properties of the PDF are configured. The default operator privilege can be overridden for each PDF by selecting a new option.
2. To determine the level of operator privilege for each of the PDFs, highlight the PDF and then click the appropriate radio button for it.

   To assign a privilege for a PDF, drag and drop the PDF into the **Personal Data** tab. Click on the PDF to select it, then choose one of the following privileges.

   <table><thead><tr><th width="149">Privilege</th><th>Description</th></tr></thead><tbody><tr><td>Hide</td><td>Operators will not see the cardholder information recorded for this PDF, for cardholders in this group's Divisions.</td></tr><tr><td>View Only</td><td>Operators will be able to view cardholder information for this PDF, for cardholders in this group's Divisions.</td></tr><tr><td>Edit</td><td>Operators will be able to enter, view, change and delete cardholder information for this PDF, for cardholders in this group's Divsions.</td></tr></tbody></table>

   **Notes:**

   * There are separate Operator Privileges to view and edit the properties for PDFs. If operators do not have the "View Personal Data Field" or "Edit Personal Data Field" operator privilege (as listed in the **Operator Privileges** tab), and an individual PDF is 'hidden' from their view, they will not even be aware of its existence.
   * If Operator Groups and PDFs are being created at the same time, the list of PDFs that will be saved into the new Operator Group will only include those that were "Applied" before the Operator Group was created. To ensure all PDFs are included in the list either create all PDFs first, or check Operator Groups as you create them, and drag any new PDFs in.
   * To remove a PDF privilege assigned in this Operator Group, **right click** on the PDF and select **Remove from List**.

</details>

<details>

<summary>Competencies tab</summary>

1. Click the **Competencies** tab.

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

   Configuration on this tab is only required if you want to override the default access of a competency for the operators in this Operator Group.

   Refer to to [Overriding Operator Group Competencies](https://help.security.gallagher.com/knowledge-hub/configuration-client/licensable-features/cardholder-competencies/overriding-operator-group-competencies.md) for the procedure.

</details>

<details>

<summary>Operator Group Restriction tab</summary>

1. Click the **Operator Group Restriction** tab.

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

   **Note:** By default, the **Restrict this operator group to these workstations** checkbox is unchecked and the grid is disabled. This means that the Operator Group is unrestricted and therefore its privileges are available for use at any workstations.
2. Do you want to restrict the workstations accessible to this Operator Group?

   If **yes**, go to Step 3.

   If **no**, go to Step 7.
3. Check the **Restrict this operator group to these workstations** checkbox.

   The grid is enabled.

   **Notes:**

   * Once this checkbox is checked, at least one workstation must be assigned to the grid before you can apply and save the changes.
   * Client Authentication verifies that a workstation is what it claims to be, using a Client Certificate installed on the workstation machine. Enabling workstation restrictions here means that all workstations, except for the server workstation, need to be registered with a registration code. Refer to the "Client Authentication Appendix" in the *Command Centre Release Note* for further detail.
4. Click **Configure** from the menu bar, then **Services & Workstations**.

   The **Services and Workstations** List Window opens.
5. Select those workstations you want to restrict this Operator Group to.

   Drag and drop them into the **Operator Group Restriction** tab.
6. Close the **Services and Workstations** List Window.
7. Do you want members of this Operator Group to be automatically logged off after a specified period of inactivity?

   <table><thead><tr><th width="92">If...</th><th>then...</th></tr></thead><tbody><tr><td>yes</td><td>tick the <strong>Invoke automatic logoff</strong> checkbox and indicate the period of inactivity in the timebox.<br>(Default = 60 minutes. Range = 1 minute - 1440 minutes, i.e. 24 hours)<br>See <a href="https://help.security.gallagher.com/knowledge-hub/configuration-client/introduction-to-command-centre/getting-started/automatic-logoff.md">Automatic Logoff</a> for a full explanation.</td></tr><tr><td>no</td><td>go to the next step.<br><br><strong>Note:</strong> By leaving the automatic logoff time as disabled, the Operator Group's automatic logoff time will be the same as the Server's value, (i.e. on the <strong>Operator Defaults</strong> tab of the Server Properties).</td></tr></tbody></table>
8. Do you want members of this Operator Group to have their operator logon automatically disabled after not logging on for a specified number of days?

   <table><thead><tr><th width="92">If...</th><th>then...</th></tr></thead><tbody><tr><td>no</td><td>go to the next step.</td></tr><tr><td>yes</td><td><p>tick the <strong>Disable Operator logon</strong> checkbox and indicate the number of days before logon is disabled in the timebox.<br>(Default = 90 days. Range = 1 day to 999 days)<br><br><strong>Notes:</strong></p><ul><li>If an operator is assigned to multiple operator groups, the largest number of days assigned to those operator groups will be the time used, this means if one of those operator groups does not have this restriction enable then the operator logon will not become disabled due to not logging on.</li><li>It is recommended that only non-administrative operator groups be configured to be disabled due to inactivity. If all operators with the "Edit Operators" privilege can become disabled due to inactivity and the System operator is disabled (as recommended), there is a danger that the ability to properly manage the site may be lost.</li><li>Scheduled Macros or Reports use the operator’s credentials, that last modified it. When these Macros or Reports are run it counts as activity, similarly, if this operator became locked due to inactivity, the scheduled Macro or Report will fail to run.</li></ul></td></tr></tbody></table>
9. If you want Command Centre operators to be able to mute unacknowledged alarms (by pressing the < **F9** > key), select the **Allow muting unacknowledged alarms** checkbox. To prevent operators from muting unacknowledged alarms, deselect the checkbox.

   **Notes:**

   * An operator only needs to be in one Operator Group with this checkbox checked in order to mute unacknowledged alarms.
   * This checkbox does not prevent operators from silencing alarms via other methods such as turning down their workstation's volume.
10. The **Enforce FIDO2 multi-factor logon** checkbox will be disabled (greyed out) if FIDO2 Credentials have not been enrolled against cardholders. Configuration of FIDO2 Credentials is performed in Command Centre Client. For further information refer to the "FIDO2 Credentials" section in the *Command Centre Client Help file*.

    **Note:** Command Centre will enforce that if any Operator Group has **Enforce FIDO2 multi-factor logon** enabled, that there must be at least one Operator who can logon to Command Centre with a FIDO2 credential. This will mean that the last Operator will fail to be disabled due to inactivity.

</details>

<details>

<summary>Command Centre Viewers tab</summary>

1. Click the **Command Centre Viewers** tab.

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

   This tab is 'read-only' and displays all Viewers from Command Centre Client that are assigned to the Operator Group in alphabetical order.

</details>

<details>

<summary>Command Centre Reports tab</summary>

1. Click the **Command Centre Reports** tab.

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

   This tab is 'read-only' and displays all Reports from Command Centre Client that are assigned to the Operator Group in alphabetical order.

</details>

7. Click the **Custom Fields** tab if you want to add and assign a custom field value to this Operator Group.

   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).
8. Click the **Notes** tab if you want to add a note(s) about this Operator Group.

   For further details regarding the **Notes** tab, see [Notes](https://help.security.gallagher.com/knowledge-hub/configuration-client/site-installation/server-properties/notes.md).
9. 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 Operator Group is created.

***

### Editing and Deleting Operator Groups

Refer to [Editing items](https://help.security.gallagher.com/knowledge-hub/configuration-client/introduction-to-command-centre/knowing-your-way-around/generic-properties-configuration/editing-items.md) and [Deleting items](https://help.security.gallagher.com/knowledge-hub/configuration-client/introduction-to-command-centre/knowing-your-way-around/generic-properties-configuration/deleting-items.md) for procedures on how to edit and delete Operator Groups.

**Note:** The system will only allow the deletion of an Operator Group if all Operators (listed in the **Operator Membership** tab), are removed from the Operator Group first.

***

### Hints

{% hint style="info" %}
**Copy and paste**

An alternative to the drag and drop method is to use the copy and paste method.
{% endhint %}

{% hint style="info" %}
**Cardholder (Operators) details**

This Operator Group will now appear on the **Operator Configuration** tab of those cardholders you added to the **Operator Membership** tab. However, they still need a Logon Name and Password configured for them. See [Configuring Operators](https://help.security.gallagher.com/knowledge-hub/configuration-client/site-management/operator-groups/configuring-operators.md) for the procedure.
{% endhint %}


---

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