> 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/products/cc-software/configure/configuration-scenarios/scenario-monitor-operator-activity.md).

# Monitor operator activity

Log cardholder-record views by selected operator groups for reporting.

To track whether an operator is viewing cardholder details in Command Centre, enable the **`CardholderViewerTracking=1`** licence feature and switch on the matching restriction for the operator group or groups you want to monitor. Each time a monitored operator views a cardholder record in any Cardholder Viewer, an event is logged that you can report on.

### License

To enable this feature you need the licence feature:

```
CardholderViewerTracking=1
```

This feature is **free on request**.

### Enable tracking

Once the licence is installed in the system, enable it for the operator group or groups you want to monitor:

1. In **Command Centre Client**, go to the **Administration** tab.
2. Select **Operator Groups**.
3. Select the operator group you want to enable tracking for.
4. Check the restriction: **"Log an event when operator views cardholder record from any Cardholder Viewer"**.

![Operator Group restriction to log cardholder-record views](https://328339335-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F6bM8WhlBE9BYizPWJaPN%2Fuploads%2Fgit-blob-78846c86b4400063ed343a1bab5d75a264d99b1a%2FSECHUB-CCS-VIEWERTRACK-01-operator-group-restriction.png?alt=media)

### Result

When an operator from the selected operator group views any cardholder's details in any Cardholder Viewer, an **event is created** in Command Centre that can be reported on.

Operator group restrictions are configured per [Operator Groups & Privileges](/knowledge-hub/products/cc-software/configure/command-centre-operator-groups-and-privileges.md).


---

# 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/products/cc-software/configure/configuration-scenarios/scenario-monitor-operator-activity.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.