> 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/entra-id-single-sign-on/linking-operators-to-their-entra-id-account.md).

# Linking operators to their Entra ID account

### Introduction

In order for an operator to log onto Command Centre Client using Entra ID single sign-on (using their Entra ID credential), their Cardholder record needs to be configured with their Entra ID User ID (User Principal Name).

See [Entra ID Single Sign-on](https://help.security.gallagher.com/knowledge-hub/configuration-client/licensable-features/entra-id-single-sign-on.md) for further detail about this feature.

### Automating this process

The ‘User Principal Name’ (and other details) of each Entra ID user can be synced to their Command Centre operator using the separately licensed Entra ID Sync feature. This removes the need for each operator to have their User Principal Name manually typed or pasted into Command Centre. For details about this feature, contact the Gallagher Support Team.

### Procedure

To manually assign an Entra ID user’s User Principal Name to their Command Centre operator, perform the following procedure:

1. Click **Manage** from the menu bar, then **Cardholders**.

   The **Cardholder** List Window opens (in [grid view](https://help.security.gallagher.com/knowledge-hub/configuration-client/introduction-to-command-centre/knowing-your-way-around/list-windows/grid-view.md)).
2. Locate and highlight the Cardholder whose User ID you want to assign.
3. Right-click and select **Properties**.
4. Click the **Operator Configuration** tab.

   ![](https://3000903572-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FfCvaxj3suxNBzdwQndVT%2Fuploads%2Fgit-blob-78f669612b3db0c286dd7167b7a36382b1b583b2%2Fentraid_chold_operatorconfigurationtab.png?alt=media)

   **Note:** If the server to which the workstation connects is enabled for Entra ID Single Sign-on, this tab will display as shown (when the Cardholder is not in an Operator Group).

   If the Cardholder was an Operator *before* the server was enabled for Entra ID Single Sign-on, they will already have a Command Centre logon, so the **Command Centre Logon** checkbox will be checked and their logon name will appear in the **Logon Name** field.

   If the Cardholder is made an Operator (by assigning them Operator Groups) after the server is enabled for Entra ID Single Sign-on, the **Command Centre Logon** checkbox will be enabled but unchecked, and the **Logon Name** field will be blank and disabled.
5. If the Cardholder is not already an Operator, (i.e. the ‘Operator Group Membership’ grid is blank), open the **Operator Group** List Window and drag and drop the required Operator Groups into the grid.
6. Check the **Entra ID Logon** checkbox.

   The **User ID** field becomes enabled.
7. In the **User ID** field, type or paste the operator’s Entra ID ‘User Principal Name’. This can be found in the overview of the user’s details in Entra ID admin center.
8. 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.


---

# 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/entra-id-single-sign-on/linking-operators-to-their-entra-id-account.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.
