> 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/creating-a-new-workstation-routing-item.md).

# Creating a new Workstation Routing item

Perform the following procedure to create a new Workstation Routing item:

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

   The new Workstation Routing item is added to the Viewer Navigation Panel, and the Workstation Routing Configuration pop-up displays.

   ![](https://2455150842-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fi6UYAoyykM6nimMN9yss%2Fuploads%2Fgit-blob-629bce89bffd75f319cb4d6e49a4ed19f91a7df1%2Fworkstationconfig_popup.png?alt=media)
2. If you want to replace the default name the system has given the Workstation Routing item, enter a new name in the **Name** field (limited to 60 characters).
3. If required, enter a logical **Description** (limited to 200 chanracters).
4. The **Division** button defaults to the name of the last Division in which the Operator created a Command Centre item, regardless of whether it was created in Configuration Client or via Command Centre Client.

   If this is not the appropriate Division for this Workstation Routing item to be in, select a Division as follows:

   1. Click the **Division** button.

      A browse tool displays.

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

      The pop-up closes and the button changes to the name of the Division you selected.

   **Note:** If you have not set up Divisions yet, you can add these to your Workstation Routing items at a later stage.
5. Click the **Close** button.

   The Workstation Routing Configuration pop-up closes.

   There are four tabs, (i.e. **Workstations**, **Routing Rules**, **Alarm Alert Divisions** and **History/Notes**). The **Workstations** tab displays by default. All Workstations involved on one side of the routing, (e.g. from or to) should be configured as a single group.

   **Notes:**

   ![](https://2455150842-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fi6UYAoyykM6nimMN9yss%2Fuploads%2Fgit-blob-f9f4885e777ac94a2a53b6324c359784c8042993%2Fworkstationrouting_workstationstab.png?alt=media)

   * When using automatic routing, the Operator Groups’ functionality is transferred to Group A Workstations when no Group B Workstations are logged on. When at least one Group B Workstation is logged on, the Operator Groups’ functionality is transferred to Group B Workstations. The logged-on state of Group A Workstations is not considered in automatic routing.
   * If you will be *only* routing manually, it is not important which Group you assign to each set of Workstations.
6. By default, the **Shortname** for the Workstation Groups is "Group A" and "Group B".

   Change the Shortnames to more meaningful names if required.

   **Note:** Each Name is limited to 20 characters.
7. Select the Workstations for each group, as follows:
   1. Click the **Add Workstations** button.

      An Add Workstations to Group pop-up displays, listing all the available Workstations in alphabetical order, (i.e.Workstations that are on the local server).

      ![](https://2455150842-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fi6UYAoyykM6nimMN9yss%2Fuploads%2Fgit-blob-5d6cecadd3799e40e0c71954582d9e97ce24d10e%2Fworkstations_addtool.png?alt=media)
   2. Check the appropriate Workstation(s), and click the **Add Selection** button.

      The pop-up closes, and the selected Workstation(s) appear in the grid.
8. Click the **Routing Rules** tab to set the rules for what happens when routing is invoked.

   ![](https://2455150842-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fi6UYAoyykM6nimMN9yss%2Fuploads%2Fgit-blob-8b3626928c482bca4d5daf3cfc0e0767da0d30d7%2Fworkstationrouting_routingrulestab.png?alt=media)
9. Configure the Operator Groups that determine the functionality being transferred between Workstations, as follows:
   1. Click the **Add Operator Groups** button.

      An Add Operator Groups pop-up displays.

      ![](https://2455150842-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fi6UYAoyykM6nimMN9yss%2Fuploads%2Fgit-blob-ac4e11a0659cfa9f952a372840cb281341516a3a%2Faddopgroups_popup.png?alt=media)
   2. Check the appropriate Operator Group(s), and click the **Add Selection** button.

      The pop-up closes, and the selected Operator Group(s) appear in the grid.
10. If you want the Workstation Routing item to run Macros when routing, configure as required.
11. If you will be using automatic workstation routing, click the **Alarm Alert Divisions** tab (sample screen). This tab defines the Divisions whose highest priority alarm is displayed on this Workstation Routing item on Site Plans while it is in the 'Routed to Group B (automatic)' state.
12. Click the **Add Alarm Alert Divisions** button.

    An Add Alarm Alert Divisions pop-up displays.

    ![](https://2455150842-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fi6UYAoyykM6nimMN9yss%2Fuploads%2Fgit-blob-546fd3debed7ce8a5a8c5ac88650984a4b56cbd7%2Faddalarmalertdivisions_popup.png?alt=media)
13. Select the Divisions whose highest priority alarm you wish to be displayed on this Workstation Routing item on Site Plans while it is in the 'Routed to Group B (automatic)' state.
14. Click the **Add Selection** button.

    The pop-up closes, and the selected Division(s) appear in the grid.

    **Notes:**

    * While a Workstation Routing item is automatically routed to Group B, it displays on Site Plans the current highest priority alarm of all items in the Divisions assigned to its 'Alarm Alert Divisions' tab. The same applies to shapes with the Workstation Routing item as an Associated Item. From the Workstation Routing's Site Plan item, operators can view, acknowledge, process, or add notes to the alarm.
    * While a Workstation Routing item is not automatically routed to Group B, it does not reflect the alarms of any other items.
    * This allows, for example, a central control site (Group A) to get insight into important alarms that are being raised in a remote site's Divisions while routing is automatically to that remote site (Group B).
15. If you want to record any note(s) about the Workstation Routing item, click the **History/Notes** tab.

    Refer to [History/Notes tab](https://help.security.gallagher.com/knowledge-hub/command-centre-client/configuring-command-centre/administration/generic-administration-tasks/history-notes-tab.md) for further detail.
16. Click the **Save** button.

    A new Workstation Routing item has been created.

    **Note:** When Workstation Routing items are first created their state is "Disabled".

### Hints

{% hint style="info" %}
**Editing and Deleting Workstation Routing items**

Refer to [Editing items](https://help.security.gallagher.com/knowledge-hub/command-centre-client/configuring-command-centre/administration/generic-administration-tasks/editing-items.md) and [Deleting items](https://help.security.gallagher.com/knowledge-hub/command-centre-client/configuring-command-centre/administration/generic-administration-tasks/deleting-items.md) for procedures on how to edit and delete Workstation Routing items.

**Note:** It is only possible to edit the configuration of a Workstation Routing item when it is in the "Disabled" state.
{% endhint %}

{% hint style="info" %}
**Duplicating Workstation Routing**

Operators privileged to create Workstation Routing items can also duplicate Workstation Routing items, which makes the task of setting up multiple Workstation Routing items that are very similar much quicker.

Refer to [Copying items](https://help.security.gallagher.com/knowledge-hub/command-centre-client/configuring-command-centre/administration/generic-administration-tasks/copying-items.md) for the procedure.
{% endhint %}


---

# 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/creating-a-new-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.
