> 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-monitoring/operator-sessions/terminating-an-operator-session.md).

# Terminating an Operator Session

### Introduction

This procedure describes how to terminate an operator session.

To terminate a session, you require the "Terminate Operator Sessions" or "Disable Workstation" privilege in the division of the workstation or mobile device associated with the session. "Terminate Operator Sessions" privilege includes the privileges provided by View Operator Session.

### Procedure

1. Click **Monitor** from the menu bar, then **Operator Sessions**.

   The Operator Sessions Viewer opens.
2. Click on the Session you want to terminate, and click the **Terminate** button.

   The confirmation message *"Are you sure you wish to terminate this operator session?"* displays.
3. Click the **Yes** button.

   The session disappears from the Operator Sessions Viewer.
4. Click the **Close (X)** button to close the Operator Sessions Viewer.

### Result

An Operator Session is terminated and:

* the following Network Connection Failure message displays for the operator whose session has been terminated:

  *"Your session has been terminated by a system administrator"*
* an Operator Event is generated.


---

# 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-monitoring/operator-sessions/terminating-an-operator-session.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.
