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

# Understanding Workstation Routing

The Workstation Routing function 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 without operators having to perform complex operations in order for this to happen.

Functionality (through the enabling and disabling of privileges) can be routed from one group of Workstations to another.

The following table describes the key system components involved in Workstation Routing, and how they are involved:

<table><thead><tr><th width="157">Component</th><th>Description</th></tr></thead><tbody><tr><td>Divisions</td><td>Divisions are used for grouping system items that have something in common, (e.g. their location, the company they belong to, the department they belong to, etc.). Using Divisions allows a site to give Operators different privileges for items in different groups, and can be used as a way of sub-dividing items into logical groupings. For large sites this makes the system easier to use, allowing involved in the current action to be filtered out easily.<br>The Workstation Routing feature relies on (system) Items that are to be made visible to a set of Operators when functionality is routed to their workstations and hidden when it is routed away, being stored in different Divisions from the items the Operator can see that are not affected by Workstation Routing.</td></tr><tr><td>Operator Groups</td><td>Operator Groups are used to control which (system) Items an Operator can see, and the functions they can perform on those items based on the Item's Division and the privileges granted for those Divisions.<br>The 'activation' and 'deactivation' of certain Operator Groups for Operators using nominated Workstations is a key component of Workstation Routing.</td></tr><tr><td>Workstations</td><td>Although workstations are software Items, they can be used to represent physical locations by virtue of the physical PC they are associated with.<br>As the action of routing functionality can affect all Operators in a particular location (regardless of who they are logged on as), Workstation Items are used to denote 'what' is affected by the routing. This allows the site to perform one action to invoke the routing without individual Operators having to perform an action.</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/command-centre-client/configuring-command-centre/configuring-licensable-features/workstation-routing/understanding-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.
