> 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/configuring-licensable-features/cardholder-viewer-tracking.md).

# Cardholder Viewer Tracking

The Cardholder Viewer Tracking logs an event whenever an Operator views a Cardholder record in Command Centre Cardholder Viewer. By default, this feature is not enabled for any Operator Group.To enable this feature, see [Configuration](https://help.security.gallagher.com/knowledge-hub/command-centre-client/configuring-command-centre/configuring-licensable-features/cardholder-viewer-tracking/enable-or-disable-cardholder-viewer-tracking.md). Using Activity report and Filters, you can run a report to view all Cardholders whose records were accessed. See [Reporting](https://help.security.gallagher.com/knowledge-hub/command-centre-client/configuring-command-centre/configuring-licensable-features/cardholder-viewer-tracking/reporting-cardholder-viewer-tracking.md) section.

**Notes:**

* Operator groups that have advanced privileges can change the setting to disable this feature.
* A 250 milliseconds delay is used to reduce the number of events raised while an Operator is scrolling rapidly through Cardholder records.

### Licensing

The 'Cardholder Viewer Tracking' is a licensable feature, i.e. your license file must contain the following option:

`[Features]`\
`CardholderViewerTracking=1`

<details>

<summary>Configuration</summary>

To enable/disable the Cardholder Viewer Tracking for an Operator Group, perform the following procedure:

1. From the Gallagher Command Centre menu, click **Administration** > **Operator Groups**.
2. Select the appropriate Operator Group.

   The Operator configuration panel displays.
3. Ensure **Operators** tab is selected.

   ![](https://2455150842-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fi6UYAoyykM6nimMN9yss%2Fuploads%2Fgit-blob-fad72c22c6d241bb6d2838996986e3633d416fa3%2Fchviewertracking_opgroups.png?alt=media)
4. Do you want to enable or disable the Cardholder Viewer Tracking? Configure as required.

   | To enable...  | select the **Log an event when operator views Cardholder record from any Cardholder Viewer** checkbox.   |
   | ------------- | -------------------------------------------------------------------------------------------------------- |
   | To disable... | deselect the **Log an event when operator views Cardholder record from any Cardholder Viewer** checkbox. |
5. Click **Save.**

   **Note:** Repeat steps 2-5 for each Operator group that you want to enable this feature for.

</details>

<details>

<summary>Reporting</summary>

Using the Activity report, and appropriate Filter(s) you can schedule or run a report to view:

* Which Cardholders have been viewed by a particular Operator
  * Use **Event Occurrence Time** Filter to specify the reporting period
  * Use **Operator Generated Events** Filter, and select **Specific Operator**. Then, select the appropriate Operator
  * Use **Event Group or Type** Filter, then select **Operator** **Viewed Cardholder details** from the Event Groups and Types drop-down menu.
* Which Operators have viewed a particular Cardholder
  * Use **Event Occurrence Time** Filter to specify the reporting period
  * Use **Cardholder is** Filter, and select **Specific Cardholder**. Then, select the appropriate Cardholder
  * Use **Event Group or Type** Filter, then select **Operator Viewed Cardholder details** from the Event Groups and Types drop-down menu.

For more details on how to create a report see [Creating Reports](https://help.security.gallagher.com/knowledge-hub/command-centre-client/configuring-command-centre/creating-reports.md).

</details>


---

# 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/configuring-licensable-features/cardholder-viewer-tracking.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.
