> 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/configuring-privileges-for-an-operator-group.md).

# Configuring Privileges for an Operator Group

Perform the following procedure to configure the privileges for an Operator Group:

1. Click on the Operator Group that you want to configure privileges for from the list in Viewer Navigation Panel.
2. Click the **Privileges** tab, if not already displayed.

   ![SearchTab](https://2455150842-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fi6UYAoyykM6nimMN9yss%2Fuploads%2Fgit-blob-8bbc7387eb8211605e2c52a33753ae77f4bf9e0d%2Fopgroups_privilegestab.png?alt=media)
3. The **Divisions to which privileges apply** grid dictates where you can use the operator privileges you select for this group. Select the divisions you want for the Operator Group, as follows:

   1. Click the **Select Divisions** button.

      The Select Operator Divisions pop-up displays.

      ![](https://2455150842-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fi6UYAoyykM6nimMN9yss%2Fuploads%2Fgit-blob-687e7c0df3f16c7b82d91dfe621db3ad07bd3c04%2Fselectoperatordivisions_popup.png?alt=media)
   2. Click the checkbox next to each division(s) you want to include.
   3. Click the **Add Selection** button.

      The pop-up closes and each of the selected division(s) appear in the **Divisions to which privileges apply** grid.

   **Note:** If you decide to remove a division from the list, the **Remove** button allows you to do so.
4. Select the operator privileges appropriate for this Operator Group, as follows:

   1. Click the **Assign Privileges** button.

      The Add Operator Privileges pop-up displays.

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

      The pop-up closes and each of the selected privilege(s) appear in the **Privileges Granted** grid.

   **Note:** If you decide to remove a privilege from the list, the **Remove** button allows you to do so.
5. By default, the **Personal Data Field privilege overrides** grid will not be populated with any Personal Data Fields (PDFs). 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, assign PDFs here, as follows:

   **Notes:**

   * 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 in the **Divisions to which privileges apply** grid above).

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

   1. Click the **Assign Personal Data Fields** button.

      The Add Personal Data Field Access pop-up displays.

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

      The pop-up closes and each of the selected PDF(s) appear in the **Personal Data Field privilege overrides** grid.

   **Note:** If you decide to remove a PDF from the list, the **Remove** button allows you to do so.
6. To determine the level of operator privilege for each of the PDFs, highlight the PDF and click the drop-down list beside it, then choose one of the following privileges.

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

   <table><thead><tr><th width="138">Privilege</th><th>Description</th></tr></thead><tbody><tr><td>Editable (default</td><td>Operators will be able to enter, view, change and delete cardholder information for this PDF, for cardholders in this group's Divisions.</td></tr><tr><td>Hidden</td><td>Operators will not see the cardholder information recorded for this PDF, for cardholders in this group's Divisions.</td></tr><tr><td>Revealable</td><td>Operators will be able to view cardholder information for this PDF, for cardholders in this group's Divisions, by clicking on "Hidden".</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>Revealable and Editable</td><td>Operators will be able to view cardholder information for this PDF, for cardholders in this group's Divisions, by clicking on "Hidden". Operators with the "Edit Cardholders" privilege will also be able to edit the value.</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 **Privileges Granted** grid), 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 assign any new PDFs.
7. By default, the **Competency privilege overrides** grid will not be populated with any competencies. Instead, this Operator Group will get the privileges for competencies that are assigned at the competency level. If you want to override the default privilege to something else, assign competencies here, as follows:

   **Notes:**

   * The level of operator privilege to view or edit cardholder information stored in a cardholder’s competency is determined for individual competencies. The competency privileges only apply to cardholders in the Operator Group’s Divisions (as configured in the **Divisions to which privileges apply** grid above).

   * The default operator privilege for each competency is determined when the properties of the competency are configured. The default operator privilege can be overridden for each competency by selecting a new option.

   1. Click the **Assign Competencies** button.

      The Add Competency Access pop-up displays.

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

      The pop-up closes and each of the selected competency(s) appear in the **Competency privilege overrides** grid.

   **Note:** If you decide to remove a competency from the list, the **Remove** button allows you to do so.
8. To determine the level of operator privilege for each of the competencies, highlight the competency and click the drop-down list beside it, then choose one of the following privileges.

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

   <table><thead><tr><th width="138">Privilege</th><th>Description</th></tr></thead><tbody><tr><td>Edit</td><td>Operators will be able to enter, view, change and delete cardholder information for this competency, for cardholders in this group's Divisions.</td></tr><tr><td>Hide</td><td>Operators will not see the cardholder information recorded for this competency, 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 competency, for cardholders in this group's Divisions.</td></tr></tbody></table>
9. Click the **Save** button.


---

# 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/configuring-privileges-for-an-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.
