> 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/invoking-workstation-routing.md).

# Invoking Workstation Routing

Once Workstation Routing has been configured, this procedure describes how an operator can invoke Routing:

1. Click the ![](https://2455150842-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fi6UYAoyykM6nimMN9yss%2Fuploads%2Fgit-blob-21696e72ec0a06324b205d044b43d8eb573a6bd7%2Fsystemoperatorbutton.png?alt=media) button on the Command Centre toolbar, and select **Routing**.

   The Workstation Routing pop-up displays.

   ![](https://2455150842-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fi6UYAoyykM6nimMN9yss%2Fuploads%2Fgit-blob-6673eb59a2eebe8ae0e9a87cdcb0b84338e7453a%2Fworkstationrouting_using.png?alt=media)
2. Routing is remembered as an Operator Workstation Preference, therefore the **Workstation Routing** button defaults to the name of the most recent Routing performed.

   If this is not the required Routing option, select an alternative Routing as follows:

   1. Click the **Workstation Routing** button.

      A browse tool displays.

      ![](https://2455150842-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fi6UYAoyykM6nimMN9yss%2Fuploads%2Fgit-blob-79bf4f737ca6379201702156c7a0db2fb24c0f43%2Fworkstationrouting_browsetool.png?alt=media)
   2. Select the appropriate Routing.
   3. Click the **OK** button.

      The pop-up closes and the button changes to the name of the Routing you selected. The **Current State** also changes to that of the selected Routing.
3. Select the required action from the **Action** drop-down list.

   The options available in the list will depend on your privileges.

   **Notes:**

   * The ‘Route to \<name>’ options are manual routing options; they will immediately invoke routing to the selected group upon clicking Route and remain that way until operator intervention.
   * The ‘Route Automatically’ option puts the Workstation Routing item into the automatic state. While in the automatic state, if there is at least one workstation logged on in the Group B workstation group (configured in the Workstation Routing item), then routing will be to that group, and if there are no workstations logged on in Group B, then routing will be to the Group A workstations. Selecting ‘Route Automatically’ and clicking Route therefore may not immediately invoke routing, and routing may be invoked automatically multiple times while in this state.
   * The ‘Disable Routing’ option treats the Workstation Routing item as if it did not exist; Operator Groups are ‘activated’ for workstation operators as per normal Operator Group assignment configuration.
4. If you want to add a comment, type your comment in the **Comment** field (Maximum of 250 characters).
5. Click the **Route** button.

### Result

The Workstation Routing item's state is changed and:

* any Macro(s) configured for that state change will run,
* if routing was invoked, (i.e. you selected a manual action, or you selected ‘Route Automatically’ and Group B’s logged-on state denoted routing should be invoked), all Operator Groups configured for the Workstation Routing item will be 'activated' for Operators logged onto Workstations in the group to which the Routing was initiated, and 'de-activated' for Operators logged onto Workstations in the other group.

  **Note:** If the server workstation is included in either group it gets ignored when Routing is actioned, so it cannot be locked out.


---

# 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/invoking-workstation-routing.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.
