> 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/licensable-features/enterprise-data-interface/configuring-operators.md).

# Configuring operators

### Operator Privileges

Assign the appropriate privileges to Gallagher Command Centre operators.

<table><thead><tr><th width="210">Privilege</th><th>is required to...</th></tr></thead><tbody><tr><td>"Edit Enterprise Data Interfaces"</td><td><p>view, add, edit, save, delete, enable, disable, find or manually run interfaces.</p><p>This privilege should be assigned to the root division of the operator group, this operator is in.</p><p>An operator with this privilege can view all PDFs (including hidden and view only), Card Types, Access Groups, Competencies and Relationhips in the Edit Mappings window.</p></td></tr><tr><td>"Run Enterprise Data Interfaces"</td><td>view, find or manually run interfaces.</td></tr></tbody></table>

**Notes:**

* An operator with the "View Site" privilege is unable to view interfaces.
* An operator with the "Advanced User" privilege can edit and manually run interfaces.

### "Run as Operator" Privileges

When an interface is run, it is run under an operator's name. This operator is referred to as the "Run as Operator". All actions performed by the interface are logged under this operator's name.

It is recommended that you create a "Run as Operator" whose sole purpose is to run all interfaces. This operator will need to be assigned the appropriate privileges in order to perform the actions specified by each interface.

<table><thead><tr><th width="210">Privilege</th><th>is required to...</th></tr></thead><tbody><tr><td>"Create Cardholders" and<br>"Edit Cardholders"</td><td>create and/or change cardholders</td></tr><tr><td>"Edit Cardholder Notes"</td><td>create and/or change a cardholder's notes</td></tr><tr><td>"Delete Cardholders"</td><td>delete cardholders</td></tr><tr><td>"Modify Access Control"</td><td>set cardholder access groups</td></tr><tr><td>"View Site"</td><td>view competencies</td></tr></tbody></table>


---

# 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/licensable-features/enterprise-data-interface/configuring-operators.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.
