> 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/introduction-to-command-centre/getting-started/logon.md).

# Logon

### Introduction

You must log on to the Configuration Client to access the system operations.

**Notes:**

* Workstations can be on a different build to the server, but it has to be lower OR equal to the server version. When Command Centre is launched, if the version number is newer than the server, logon will fail and the message *"The client version is incompatible with the server. Startup failed!"* will display on the splash screen.
* When the Configuration Client is launched, if the server to which the workstation is trying to connect to is enabled for Active Directory single sign-on (a licensable feature), the system will try to log the operator onto the Configuration Client. If Active Directory single sign-on is being used, ensure you have a domain account, (e.g. <Windowsuser@Gallagher.Local>).
* The following procedure describes the 'standard' method of logging on to the Configuration Client, (i.e. via entry of a valid operator username and password). However, it may be possible to log on and off designated Configuration Client workstations using a FIDO2 authenticator, if cardholders have FIDO2 Credentials enrolled against them. For further detail refer to [Logon with FIDO2 Credentials](https://help.security.gallagher.com/knowledge-hub/configuration-client/introduction-to-command-centre/getting-started/logon/logon-with-fido2-credentials.md).

### Procedure

1. Open the Configuration Client by either:
   * double-clicking the **Configuration Client** icon on your Desktop, OR
   * from the **Start** menu, click **All Programs** > **Gallagher** > **Configuration Client**.
2. Is your site licensed for Active Directory single sign-on?

   <table><thead><tr><th width="84">If...</th><th>then...</th></tr></thead><tbody><tr><td>no</td><td>the following logon screen displays:<br><img src="https://3000903572-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FfCvaxj3suxNBzdwQndVT%2Fuploads%2Fgit-blob-43158ba0b44559a344e172ba40001594ddc36764%2Flogon.png?alt=media" alt=""><br>Go to Step 4.</td></tr><tr><td>yes</td><td><p>if automatic logon is possible, the Configuration Client main window displays.<br>If not, an error message informing the user of the reason logon has failed displays, followed by the logon screen below:<br><img src="https://3000903572-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FfCvaxj3suxNBzdwQndVT%2Fuploads%2Fgit-blob-e6ca80316b2d1fe906c7d8da42a79e5d35140e9b%2Flogon_authentication.png?alt=media" alt=""><br><strong>Note:</strong> For the system to automatically log the operator onto the Configuration Client the following must apply:</p><ul><li>the Active Directory is available</li><li>the domain account used to log onto the network has not been disabled, deleted or locked out in Active Directory</li><li>the domain account is linked to an operator in the Configuration Client.</li></ul><p>Go to Step 3.</p></td></tr></tbody></table>
3. Select the appropriate Authentication Logon method from the **Logon Method** drop-down box.

   <table><thead><tr><th width="247">If you click...</th><th>then...</th></tr></thead><tbody><tr><td>Windows Authentication,</td><td>the system will find the operator linked to the user's domain account and log onto the workstation as that operator.</td></tr><tr><td>Configuration Client Authentication,</td><td>this allows the operator to enter a Configuration Client Logon Name and Password.<br>Go to Step 4.</td></tr></tbody></table>
4. Type your **Logon Name**.

   **Note:** When you first log on as the system operator, **system** is the default 'Logon Name', but there is no default 'Password'. For any other operator logging on, the **Logon Name** will be blank for a new install on a workstation or server that has not had an attempted logon. After that, it will be populated with last attempted Logon Name for that workstation or server.
5. Click within the **Password** field.

   (Alternatively, press the **Tab** key.)
6. Type your password.
7. The **Language** drop-down box provides a list of available languages.

   If you have previously logged in, **Last Selected** will be the first option, and this is selected by default.

   Select another language if required.
8. Click **Logon**.

   (Alternatively press the **Enter** key.)

   **Notes:**

   * If you do not have the "Launch Configuration Client" operator privilege, the following message appears on the logon screen:

     *"You do not have the privilege to launch the configuration client. Please contact your system administrator"*.
   * When you log on for the first time as the system operator, the system password must not be left blank, therefore the following screen displays:

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

     When other operators log on for the first time the following screen will display so they can change their password from the one the system administrator provided them with:

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

     1. Type in the **New Password**.
     2. **Confirm Password** by re-typing it.
     3. Click the **OK** button.
   * The System Operator is initially used to set up Command Centre. Once other operators have been created, the System Operator should be disabled by another operator.

     See [Disabling the System Operator](https://help.security.gallagher.com/knowledge-hub/configuration-client/site-management/cardholders/disabling-the-system-operator.md) for further detail.

### Result

* The Logon window is removed from the screen.
* The Configuration Client main window displays providing the following information:

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

* Your user name
* The current date and time
* A **System view** drop-down box may also display, depending on whether you have the operator privilege to see it, (i.e. the "Select System View" or "Advanced User" operator privilege). If it does display, you can restrict (change) your system view. See [Restricting System View](https://help.security.gallagher.com/knowledge-hub/configuration-client/introduction-to-command-centre/getting-started/restricting-system-view.md) for further detail.

**Note:** The Configuration Client main window can be resized down to 480px if required.

* A visual Activity Indicator ![](https://3000903572-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FfCvaxj3suxNBzdwQndVT%2Fuploads%2Fgit-blob-d9e19db1388723623bc7215f66738b4cb841dc72%2Findicator.png?alt=media) may display to indicate that the Configuration Client is communicating with the server. The purpose of this indicator is to provide operators with confirmation that the Configuration Client has not ceased operation.

  The Activity Indicator can be enabled/disabled via the **Advanced** tab of the Server Properties. (See [Advanced](https://help.security.gallagher.com/knowledge-hub/configuration-client/site-installation/server-properties/advanced.md).) Once enabled, the Activity Indicator is always visible while the Configuration Client is running and responding, and can be moved anywhere on your screen by clicking on it and holding down the mouse button, then dragging it.
* You can access those menus available to you.

  **Note:**

  Depending on your operator privileges or current system view, some of the menu options shown on the screen above may not appear.
* The session will be added to the list of sessions visible in the Operator Sessions Viewer of the Configuration Client and the Operator Sessions tile in the Command Centre Client.

### Hint

{% hint style="info" %}
**Failed logons**

If an operators’ successive logon attempts reach the configured 'number of failed attempts before lockout', then they will be locked out for the configured lockout period (or permanently if this option is set). A message will display on the logon screen indicating that the operator is locked out.

<img src="https://3000903572-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FfCvaxj3suxNBzdwQndVT%2Fuploads%2Fgit-blob-b75f02401bca1fa7722a7ad46a9464a09c8a4ec2%2Flogon_failed.png?alt=media" alt="SystemOperator Password" data-size="original">

The lockout period (if any) will not be displayed. When the lockout period has completed, the logon name and password can be re-entered and authenticated successfully. If the operator needs the account unlocked, a privileged operator can do so via the **Operator Configuration** tab of the Cardholder properties. See [Unlocking an Operator account](https://help.security.gallagher.com/knowledge-hub/configuration-client/introduction-to-command-centre/getting-started/operator-passwords/unlocking-an-operator-account.md) for further detail.

**Note:** Lockout state does not get replicated to remote servers in a multi-server environment.
{% endhint %}

### In This Section

* [Logon with FIDO2 Credentials](https://help.security.gallagher.com/knowledge-hub/configuration-client/introduction-to-command-centre/getting-started/logon/logon-with-fido2-credentials.md)


---

# 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/introduction-to-command-centre/getting-started/logon.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.
