> 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/quick-tips-for-working-with-workstation-routing.md).

# Quick Tips for working with Workstation Routing

Workstation Routing allows for both manual and automatic transfer of Alarm Management and Site Monitoring functionality from one set of Operators to another. This allows a site to manage alarms and monitor their site locally during the day, and then hand control over to a central monitoring station at night.

Workstation Routing items define what will happen when it changes routing state, and holds the following information:

* the item's current state (in the **Routing State** column in the Navigation Panel)
* when the state was last changed and by who
* the groups of Workstations between which functionality will be routed
* the Operator Groups that determine the functionality being routed between Workstations
* Macros to run when the state changes.

  **Note:** Macros allow a site to involve elements in the routing that cannot be controlled through the routing of Operator Groups, (e.g. the turning on of Outputs at a different location).

### Creating and editing Workstation Routing items

* Workstation Routing items with unsaved changes display in the Navigation Panel in **bold** and have a **\*** at the end of their name.
* It is only possible to edit the configuration of a Workstation Routing item when it is in the **Disabled** state, and it cannot be taken it out of this state while it is being edited.
* Two or more users cannot edit the configuration of the same Workstation Routing item at the same time.
* A Workstation Routing item cannot be saved if the same Workstation has been included in both Workstation groups.

### Changing the state of Workstation Routing items

* Workstation Routing items will be in one of five states: **Disabled**, **Routed to \<Group A name> (manual)**, **Routed to \<Group B name> (manual)**, **Routed to \<Group A name> (automatic)**, or **Routed to \<Group B name> (automatic).**
* Users can change the state of a Workstation Routing item using the ![](https://2455150842-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fi6UYAoyykM6nimMN9yss%2Fuploads%2Fgit-blob-053a472a61cdee41c2eecf1b54c5231a48d9dda4%2Fchangestatusbutton.png?alt=media) button.
* The ![](https://2455150842-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fi6UYAoyykM6nimMN9yss%2Fuploads%2Fgit-blob-053a472a61cdee41c2eecf1b54c5231a48d9dda4%2Fchangestatusbutton.png?alt=media) button is only enabled when a single Workstation Routing item is selected in the Navigation Panel.
* Workstation Routing items are put into the manual states by a user selecting one of the two ‘Route to \<name>’ options. They are put into the automatic states by a user selecting the ‘Route Automatically’ option, and then the automatic state is determined by the system: if there are workstations in Group B logged on, the state is **Routed to \<Group B name> (automatic)**; if there are no workstations in Group B logged on, the state is **Routed to \<Group A name> (automatic)**. The state may then continue to switch automatically as per the logged-on state until a user selects a manual state.

### Invoking Workstation Routing

* A user requires the ‘Disable Workstation Routing’ privilege for the **Disable Workstation** option, and the ‘Use Workstation Routing’ privilege for the other options to be available from 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.
* When Routing is invoked:
  * any Macro(s) configured for that state change will run,
  * 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.


---

# 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/quick-tips-for-working-with-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.
