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

# Linking operators to their Active Directory account

### Introduction

In order for an operator to log onto the system using single sign-on (using their Active Directory user name and password), their Cardholder records need to be configured with their Windows logon.

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

### 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 you want to configure their Windows logon for.
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 Active Directory 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 Active Directory 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 Active Directory Single Sign-on, the **Command Centre Logon** checkbox will be enabled but unchecked, and the **Logon Name** field will be blank and disabled.
5. Check the **Windows Logon** checkbox.

   The **User Name** field and Browse ![](https://3000903572-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FfCvaxj3suxNBzdwQndVT%2Fuploads%2Fgit-blob-2faa7ab66c6abaa3b468de2eb70428ff3cce64c5%2Fthreedotsbutton.png?alt=media) button become enabled.
6. If the **User Name** field is empty, it needs to be populated with the domain name, (e.g. "Gallagher.Local").

   Do this by either:

   * typing the user name or pasting it into the **User Name** field, or
   * clicking the ![](https://3000903572-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FfCvaxj3suxNBzdwQndVT%2Fuploads%2Fgit-blob-2faa7ab66c6abaa3b468de2eb70428ff3cce64c5%2Fthreedotsbutton.png?alt=media) button to browse to the Active Directory for a Windows user name.

     The Select User dialog displays:

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

     **Note:** Choosing the user name by browsing will overwrite any content in the **User Name** field.
7. Click the **Object Types** button to select the appropriate object type.
8. Click the **Locations** button to select the domain.
9. Click the **OK** button.

   The Select User dialog closes.
10. If the Cardholder is not already an Operator, (i.e. the Operator Group grid is blank), open the **Operator Group** List Window and drag and drop the required Operator Groups into the grid.
11. 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/active-directory-single-sign-on/linking-operators-to-their-active-directory-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.
