> 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/site-management/cardholders/disabling-the-system-operator.md).

# Disabling the System Operator

### Introduction

The System Operator account is initially used to set up Command Centre. Once separate operators have been created, the System Operator is not entirely necessary and should be disabled by another operator for security purposes.

Operators require the "View/Edit Operators" privilege to perform this procedure.

### Procedure

1. Click **Monitor** from the menu bar, then **Find..**.

   The **Find** tool opens.
2. Click within the **Look in** field and select the "System Operator" option.
3. Click the **Start Search** button.

   The System Operator displays in the Search window.
4. **Right-click** on the System Operator and select **Properties**.

   By default the **General** tab displays.
5. Click the **Operator Configuration** tab.

   ![](https://3000903572-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FfCvaxj3suxNBzdwQndVT%2Fuploads%2Fgit-blob-a73af5bfe7a62eac178f9624445df60b9ed8ab94%2Fsystemoperator_opconfigtab.png?alt=media)
6. Tick the **Disable Command Centre Logon** checkbox.
7. Click **OK** to exit and save your changes.

   Click **Cancel** to exit without saving your changes.

   Click **Apply** to save your changes and stay in this window.

### Result

The System Operator account is disabled.

**Note:** If an operator attempts to logon using the System Operator name and password, the message *"Invalid logon name or password"* will display on the Logon screen.


---

# 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/site-management/cardholders/disabling-the-system-operator.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.
