> 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/configuration-client/licensable-features/commend-intercoms/assigning-a-commend-console-to-a-workstation.md).

# Assigning a Commend Console to a Workstation

### Introduction

The Commend Console must be located near the Command Centre workstation. If an operator responds to an intercom call event via the workstation, the call event will be removed from all other operator workstations.

Perform the following procedure to assign a Commend Console to a Command Centre workstation.

### Procedure

1. Click **Configure** from the menu bar, then **Services & Workstations**.

   The Services & Workstations List Window opens.
2. Open the workstation you want to assign the Commend Console to.
3. Click the **Commend Configuration** tab.

   ![](https://3000903572-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FfCvaxj3suxNBzdwQndVT%2Fuploads%2Fgit-blob-3f0eefaf8ca11b93af87a15c8a3b2dd5aeebf74b%2Fcommendconsole.png?alt=media)
4. Select the Commend Intercom that you want to assign to the workstation.

   **Notes:**

   * Only master intercoms can be associated with a workstation.
   * A master intercom can only be associated with one workstation.
5. Click **OK** to exit and save your changes.

   Click **Cancel** to exit without saving your changes.

   Click **Apply** to save your changes and stay in this window.

### Result

A Commend Console has been assigned to a Command Centre workstation.


---

# 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/configuration-client/licensable-features/commend-intercoms/assigning-a-commend-console-to-a-workstation.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.
