> 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/operator-groups/creating-a-new-operator-group.md).

# Creating a new Operator Group

Perform the following procedure to create a new Operator Group:

**Note:** Cardholders and Personal Data Fields need to be set up prior to performing this procedure.

1. Click the **New Operator Group** button on the Viewer Navigation Panel.

   The new Operator Group is added to the Viewer Navigation Panel, and the Operator Group Configuration pop-up displays.

   ![](https://2455150842-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fi6UYAoyykM6nimMN9yss%2Fuploads%2Fgit-blob-c2de17f03fa92bdc5f0943b363b089700ed7925b%2Fopgroupconfig_popup.png?alt=media)
2. If you want to replace the default name the system has given the Operator Group, enter a new name in the **Name** field (limited to 60 characters).
3. If required, enter a logical **Description** (limited to 200 characters).
4. The **Division** button defaults to the name of the last Division in which the Operator created a Command Centre item, regardless of whether it was created in Configuration Client or via Command Centre Client.

   If this is not the appropriate Division for this Operator Group to be in, select a Division as follows:

   1. Click the **Division** button.

      A browse tool displays.

      ![](https://2455150842-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fi6UYAoyykM6nimMN9yss%2Fuploads%2Fgit-blob-5ea28b89c753564de542b1b9c1b328d1e0fc8c60%2Fselectdivisionforviewer_popup.png?alt=media)
   2. Select the appropriate Division.
   3. Click the **OK** button.

      The pop-up closes and the button changes to the name of the Division you selected.

   **Note:** If you have not set up Divisions yet, you can add these to your Operator Group at a later stage.
5. Click the **Close** button.

   The Operator Group Configuration pop-up closes.

   There are four tabs, (i.e. **Operators**, **Privileges**, **Viewers & Reports** and **History/Notes** ). The **Operators** tab displays by default.
6. Select the cardholders you require to be members of the new Operator Group as follows:
   1. Click the **Add Cardholders** button.

      The Select Cardholders pop-up displays.

      ![](https://2455150842-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fi6UYAoyykM6nimMN9yss%2Fuploads%2Fgit-blob-4282590ed2df6fcd449a33720cac15b180cd9620%2Fselectcardholders_popup.png?alt=media)
   2. To find the Cardholder that you want to make a member, select what criteria you want to search on from the **By** drop-down list, (i.e. Name, Description, Division, Card Number, Last Zone Entered, Authorised or All).

      By default, Name is selected.
   3. Start entering characters in the **Search** field.

      A minimum of 3 characters starts the search. However, if you selected Card Number(s) as the search criteria, you need to click the ![](https://2455150842-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fi6UYAoyykM6nimMN9yss%2Fuploads%2Fgit-blob-f1056e058547589bcd63a07bc872a1a741ea174c%2Fsearchbutton.png?alt=media) button after you enter a number in the **Search** field.
   4. From the search results, click on the Cardholder(s) you want to make members.

      The Cardholder(s) appear in the lower section and are all checked by default.
   5. Uncheck any Cardholders you do not want to assign, and click the **OK** button.

      The pop-up closes and the selected Cardholder(s) now appear in the **Operator Membership** grid.

      **Notes:**

      * If you decide to remove a Cardholder from the list, the **Remove** button allows you to do so.
      * If a Cardholder has Notification PDFs, (e.g. Mobile number, Email address, etc.), these can be displayed by clicking the ![](https://2455150842-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fi6UYAoyykM6nimMN9yss%2Fuploads%2Fgit-blob-f70e2ebd114c59daf398a803d4b7e9cba0ed86fc%2F32861.png?alt=media) icon beside their name in the **Operator Membership** grid.
7. Do you want to restrict the workstations accessible to this Operator Group?

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

   If **no**, go to Step 10.

   **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.
8. Check the **Restrict this Operator Group to these workstations** checkbox.

   The grid is enabled.

   **Note:** Once this checkbox is checked, at least one workstation must be assigned to the grid before you can apply and save the changes.
9. Select the workstations you want to restrict the Operator Group to, as follows:

   1. Click the **Add Workstations** button.

      The Add Workstation Restriction pop-up displays.

      ![](https://2455150842-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fi6UYAoyykM6nimMN9yss%2Fuploads%2Fgit-blob-473c64c1645bba2b3654905a8db79b6a6c6dc4cf%2Faddworkstationrestrictions_popup.png?alt=media)
   2. Click the checkbox next to each workstation name you want to include, or click the **Select All** button if you want to include all workstations.
   3. Click the **Add Selection** button.

      The pop-up closes and each of the selected workstation(s) appear in the **Restrictions** grid.

   **Note:** To remove a workstation, select (highlight) the workstation you want to remove and click the **Remove** button.
10. If required, tick the **Invoke automatic logoff after inactivity** checkbox and specify a time that users will get logged off after that period of inactivity.

    (Default = 60 minutes. Range = 1 minute to 1440 minutes, i.e. 24 hours)
11. For an operator logon to become disabled after not logging on for a set number of days, tick **Disable Operator membership after x days of inactivity**. Specify the number of days that the operator will become disabled after that period of not logging on.

    (Default = 90 days. Range = 1 day to 999 days)

    **Notes:**

    * 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.
    * 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.
    * 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.
12. 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.
13. 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.
14. The **Privileges** tab allows you to configure the privileges for this Operator Group as required.

    See [Configuring Privileges for an Operator Group](https://help.security.gallagher.com/knowledge-hub/command-centre-client/configuring-command-centre/administration/operator-groups/configuring-privileges-for-an-operator-group.md) for the procedure.
15. Click the **Viewers & Reports** tab.
16. Assign the Viewers that you want operators belonging to this group to be able to see, as follows:

    1. Click the **Assign Viewers** button.

       The Add Access to Viewers pop-up displays.

       ![](https://2455150842-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fi6UYAoyykM6nimMN9yss%2Fuploads%2Fgit-blob-322696f83e9fc5c334f31c07022f9687cb5af77c%2Faddaccesstoviewers_popup.png?alt=media)
    2. Search for the Viewer you want by entering search criteria in the **Search** field and/or refining the filters.

       The grid becomes populated with Viewers that match the search criteria.
    3. Click the checkbox next to each Viewer you want to include, or click the **Select All** button if you want to include all Viewers.
    4. Click the **Add Selection** button.

       The pop-up closes and each of the selected Viewer(s) appear in the Command Centre Viewers grid.

    **Note:** If you decide to remove a Viewer from the list, the **Remove** button allows you to do so.
17. Assign the Reports that you want operators belonging to this group to be able to see, as follows:

    1. Click the **Assign Reports** button.

       The Add Access to Reports pop-up displays.

       ![](https://2455150842-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fi6UYAoyykM6nimMN9yss%2Fuploads%2Fgit-blob-ce412d78b6d5008b40a9e67c11ea908abd6d8cc4%2Fcreatesection.png?alt=media)
    2. Search for the Report you want by entering search criteria in the **Search** field and/or refining the filters.

       The grid becomes populated with Reports that match the search criteria.
    3. Click the checkbox next to each Report you want to include, or click the **Select All** button if you want to include all Reports.
    4. Click the **Add Selection** button.

       The pop-up closes and each of the selected Report(s) appear in the Command Centre Reports grid.

    **Note:** If you decide to remove a Report from the list, the **Remove** button allows you to do so.
18. Do you wish to configure Alarm Note options?

    If **no**, then go to Step 19.

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

    <table><thead><tr><th width="204">Option</th><th>Description</th></tr></thead><tbody><tr><td><strong>Optional</strong><br><em>(Option A)</em></td><td>The privileged operator can optionally select alarm note(s) before processing or acknowledging an alarm.</td></tr><tr><td><strong>Required when processing alarms</strong> <em>(Option B)</em></td><td>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.</td></tr><tr><td><strong>Required when acknowledging or processing alarms</strong><br><em>(Option C)</em></td><td>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.</td></tr></tbody></table>

    **Notes:**

    * If none or only one alarm note has been configured in the Server Properties (in Configuration Client), then the 'Alarm Notes' option will not be enabled.
    * Where an alarm monitoring operator is a member of more than one Operator Group then the following rules apply:

    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.

    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.

    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.
19. Check the **Operator can not 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 Viewer for escalated alarms.
20. Do you wish to configure Alarm Display options for Configuration Client?

    If **no**, then go to Step 19.

    If **yes**, then click the appropriate options you require.

    <table><thead><tr><th width="204">Option</th><th>Description</th></tr></thead><tbody><tr><td>Automatically display on alarm occurrence</td><td>The Alarm Viewer will be opened, made visible and brought to the front of all other windows on the occurrence of any new alarm.<br>With this option enabled you can not locate the Alarm Viewer off screen and the entire Alarm Viewer will be visible at all times.</td></tr><tr><td>Always on top</td><td><p>The Alarm Viewer will always be in front of all other windows.</p><p>With this option enabled the entire Alarm Viewer will be visible at all times and you can not:</p><ul><li>minimise the Alarm Viewer, or</li><li>locate the Alarm Viewer off screen.</li></ul></td></tr></tbody></table>
21. Do you want escalated alarms to display in a separate window from the main Alarm Viewer in Configuration Client?

    <table><thead><tr><th width="84">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.
22. If you want to record any note(s) about the Operator Group, click the **History/Notes** tab.

    Refer to [History/Notes tab](https://help.security.gallagher.com/knowledge-hub/command-centre-client/configuring-command-centre/administration/generic-administration-tasks/history-notes-tab.md) for further detail.
23. Click the **Save** button.

    A new Operator Group has been created.

### Hints

{% hint style="info" %}
**Editing and Deleting Operator Groups**

Refer to [Editing items](https://help.security.gallagher.com/knowledge-hub/command-centre-client/configuring-command-centre/administration/generic-administration-tasks/editing-items.md) and [Deleting items](https://help.security.gallagher.com/knowledge-hub/command-centre-client/configuring-command-centre/administration/generic-administration-tasks/deleting-items.md) for procedures on how to edit and delete Operator Groups.
{% endhint %}

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

The cardholder(s) you added to this Operator Group (in Step 6) will now have details displayed in the **Cardholder Operator Groups** tile, (i.e. Logon Name and Operator Group Membership details).
{% 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/command-centre-client/configuring-command-centre/administration/operator-groups/creating-a-new-operator-group.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.
