> 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/command-centre-client/configuring-command-centre/configuring-licensable-features/workstation-routing/changing-the-state-of-a-workstation-routing-item.md).

# Changing the state of a Workstation Routing item

A Workstation Routing item will be in one of five states, as explained by the following table:

<table><thead><tr><th width="225">If operator has selected...</th><th width="244">and...</th><th>then the state is...</th></tr></thead><tbody><tr><td>Disable Workstation Routing</td><td><em>N/A</em></td><td>Disabled</td></tr><tr><td>Route to &#x3C;Group A name></td><td><em>N/A</em></td><td>Routed to &#x3C;Group A name> (manual)</td></tr><tr><td>Route to &#x3C;Group B name></td><td><em>N/A</em></td><td>Routed to &#x3C;Group B name> (manual)</td></tr><tr><td>Route Automatically</td><td>All Group B workstations are logged off of Command Centre</td><td>Routed to &#x3C;Group A name> (automatic)</td></tr><tr><td>Route Automatically</td><td>At least one Group B workstation is logged onto Command Centre</td><td>Routed to &#x3C;Group B name> (automatic)</td></tr></tbody></table>

The current state appears in the Routing State column in the Navigation Panel, beside the Workstation Routing item name. When necessary, perform the following procedure to change the state of a Workstation Routing item to another state:

1. Select the Workstation Routing item in the Navigation Panel.
2. Click the **Change Status** button.

   ![](https://2455150842-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fi6UYAoyykM6nimMN9yss%2Fuploads%2Fgit-blob-2dc4c5f28f482581d7cfe579ef4e09283a58ff6d%2Fworkstationrouting_changestatus.png?alt=media)
3. Select the required state.

   A Comments pop-up displays.

   ![](https://2455150842-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fi6UYAoyykM6nimMN9yss%2Fuploads%2Fgit-blob-023dc7168ba3a39d853c9ccdcb5abd01553be003%2Fworkstationrouting_changestatecomments.png?alt=media)
4. If you want to add a comment, type your comment in the **Comment** field (Maximum of 250 characters).
5. Click the **OK** button.

   The pop-up closes and the new state now appears in the **Routing State** column.


---

# 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/command-centre-client/configuring-command-centre/configuring-licensable-features/workstation-routing/changing-the-state-of-a-workstation-routing-item.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.
