> 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/opening-the-operator-sessions-viewer.md).

# Opening the Operator Sessions Viewer

### Introduction

This viewer provides details of the operators currently logged onto the Command Centre Server. An operator using this viewer can terminate the active sessions of other operators and disable active workstations.

To see a session in the Operator Sessions Viewer, you require the "View Operator Sessions", "Terminate Operator Sessions" or "Disable Workstation" privilege in the division of the workstation or mobile device associated with the session.

### Procedure

1. Click **Monitor** from the menu bar.
2. Click **Operator Sessions**.

### Result

The session list is retrieved from the server and displayed on the Operator Sessions Viewer.

![](https://3000903572-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FfCvaxj3suxNBzdwQndVT%2Fuploads%2Fgit-blob-3d9deef7cdf299892cd5015c3b295b6abdf18476%2Fopsessionsviewer.png?alt=media)

The columns on the Operator Sessions Viewer are described in the following table:

<table><thead><tr><th width="156">Column</th><th>Description</th></tr></thead><tbody><tr><td>Number</td><td>Assists with counting the number of sessions in the list.</td></tr><tr><td>Licensing Group</td><td>The name of the Licensing Group that the workstation belongs to, if one exists.</td></tr><tr><td>Workstation</td><td>The name of the workstation FT item associated with the session.</td></tr><tr><td>Operator</td><td>The name of the cardholder who has logged on as an operator.</td></tr><tr><td>Session Type</td><td><p>Shows the role assigned to the session for licensing purposes. The user that is logged on will have one of the following roles:</p><ul><li>None, (i.e. empty)</li><li>Operator</li><li>Operator (Configuration Client)</li><li>Mobile</li><li>Receptionist</li><li>Visit Pre-registration</li><li>Import/Export</li><li>OPC</li><li>Remote<br><br><strong>Note:</strong> In a multi-server system, when an operator is logged onto a remote server, (e.g. monitoring remote alarms), they will show as a "Remote" session.</li></ul></td></tr><tr><td>Session Name</td><td>The Windows Terminal Services Session Name.</td></tr><tr><td>Status</td><td>Each session has a Status of either "Active" or "Expired".<br>An <strong>Active</strong> session is alive and has pinged the server in the past 50 seconds.<br>An <strong>Expired</strong> session is an orphaned session that has not pinged the server in the past 50 seconds, and has been disconnected.</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/site-monitoring/operator-sessions/opening-the-operator-sessions-viewer.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.
