> 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/introduction-to-command-centre/getting-started/automatic-logoff.md).

# Automatic Logoff

An "automatic logoff" time can be configured so that operators are logged off after a specified period of inactivity, closing all windows and discarding any unsaved changes. There are various methods of configuring this, depending on what is required:

* for the entire system via the **Operator Defaults** tab of the Command Centre Server properties.

  (see [Operator Defaults](https://help.security.gallagher.com/knowledge-hub/configuration-client/site-installation/server-properties/operator-defaults.md) for further detail)
* by workstation, via the **Restrictions tab** of the Workstation properties.

  (see [Creating a new Workstation Item](https://help.security.gallagher.com/knowledge-hub/configuration-client/site-installation/services-and-workstations/creating-a-new-workstation-item.md) for further detail)
* by Operator Group via the **Operator Group Restriction** tab of the Operator Group properties.

  (see [Setting up Operator Groups](https://help.security.gallagher.com/knowledge-hub/configuration-client/site-management/operator-groups/setting-up-operator-groups.md) for further detail)

**Notes:**

* Automatic logoff times specified for a workstation will override any automatic logoff time configured for the entire system via the Server Properties.
* If a task that takes a long time, (e.g. Activity Report), is being carried out at the time of "automatic logoff", this constitutes activity on the workstation. This prevents an operator from being logged off while waiting for a task to be completed by the system.
* When an operator belongs to two or more Operator Groups with differing automatic logoff restrictions, the lowest inactivity time takes precedence.

  **For example:**

  *The automatic logoff time for Operator Group 1 is 30*

  *minutes, and 45 minutes for Operator Group 2. Operator X belongs to both Operator Groups 1 and 2, so will be logged off after 30 minutes of inactivity.*
* When a workstation logoff restriction applies as well as an operator group restriction, the lowest inactivity time takes precedence.

  **For example:**

  *The automatic logoff time for Operator Group 1 is 30 minutes, and 10 minutes for Workstation Z (which has Operator Group 1 included in its restrictions). Operator X belongs to Operator Group 1 and is logged into Workstation Z, so will be automatically logged off after 10 minutes of inactivity.*


---

# 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/introduction-to-command-centre/getting-started/automatic-logoff.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.
