> 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/site-installation/server-properties/operator-defaults.md).

# Operator Defaults

### Introduction

This tab enables you to set some Password and/or [Operator](https://help.security.gallagher.com/knowledge-hub/configuration-client/glossary-of-terms.md#operator) restrictions.

If your site is licensed for Active Directory Single Sign-on, the server connected to the workstation that an operator will be launching the application from has to be enabled for it. This is configured on this tab also.

### Procedure

1. Open the **Command Centre Server Properties** window. [How?](https://help.security.gallagher.com/knowledge-hub/configuration-client/site-installation/server-properties/opening-the-server-properties-window.md)
2. Click the **Operator Defaults** tab.

   ![](https://3000903572-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FfCvaxj3suxNBzdwQndVT%2Fuploads%2Fgit-blob-f59a66cf2915e95ac591e44f902ba0937d8b0e7b%2F44864.png?alt=media)
3. Configure the **Password Policy** as required.

   <table><thead><tr><th width="193">Field</th><th>Description</th></tr></thead><tbody><tr><td>Minimum password length</td><td>This is the minimum number of characters allowed for passwords.<br>(Default = 8. Range = 6 - 99)<br><br><strong>Note:</strong> On a clean install for sites with a NPSA license, the default value will be 9. If this is changed the new value will be retained after an upgrade.</td></tr><tr><td>Minimum time between password changes</td><td>This prevents users from changing passwords regularly. The default is set to '0'. This is the minimum time between password resets. This stops users from changing their passwords several times to wipe the history and get back to their old password if password history checks are made.<br>(Default = 0. Range = 0 - 9999 minutes)<br><br><strong>Note:</strong> This applies to self-selecting passwords only.</td></tr><tr><td>Password history to maintain</td><td>A figure here indicates the number of successive password changes required before a password can be repeated.<br>(Default = 10. Range = 0 - 999)</td></tr><tr><td>Expire password after</td><td>Checking this allows a number of days to be set for passwords to expire after. This forces users to change their passwords periodically.<br>(Range = 0 - 365 days)</td></tr><tr><td>Require x out of 4 of upper case, lower case, numbers and special characters</td><td><p>Checking this option enforces passwords to use at least three or all four of the four available character types, (i.e. lower case letters, upper case letters, numbers and symbols), depending on whether you select <strong>3</strong> or <strong>4</strong> from the drop-down.<br><br><strong>Notes:</strong></p><ul><li>When this setting is selected, it will not be possible for passwords to be created that do not include upper case, lower case, a number and a special character.</li><li>When this change is applied, the enforcement takes place the next time the Operator changes their password.</li></ul></td></tr><tr><td>Do not allow 3 or more repeating or consecutive characters</td><td>Checking this option enforces passwords to not contain 3 or more characters repeated in a row, or 3 or more consecutive characters, regardless of upper/lower case combinations, (e.g. "aaa", "1234abcd").</td></tr></tbody></table>

   **Note:** It is possible to force a one-off change of password for an operator. This is achieved by checking the **Force password change at next logon** checkbox (on the **Operator Configuration** tab of cardholder properties), when you set up a cardholder as an operator. When the operator logs on to Command Centre for the first time the 'Change Password' dialog displays, forcing them to change their password.

   Once the change has been forced, the **Force password change at next logon** checkbox will go back to being de-selected, unless either the **EN50131 Compliance** or **SSF1014 Compliance** checkbox is checked on the **Standards** tab of the Server Properties.
4. Click the appropriate checkbox(es) to configure the **Operator Restrictions**, as required.

   <table><thead><tr><th width="193">Field</th><th>Description</th></tr></thead><tbody><tr><td>Enable workstation restrictions</td><td>Check this if you want to restrict the Operator Groups on workstations, and to ensure that any new workstations must be created in the <strong>Services &#x26; Workstations</strong> List Window (via <strong>Configure</strong> from the main menu bar).<br>Checking this results in an additional <strong>Restrictions</strong> tab displaying on the Workstation properties. See <a href="https://help.security.gallagher.com/knowledge-hub/configuration-client/site-installation/services-and-workstations/creating-a-new-workstation-item.md">Creating a new Workstation Item</a> for further details on what can be configured on this tab.<br><br><strong>Note:</strong> Client Authentication verifies that a workstation is what it claims to be, using a Client Certificate installed on the workstation machine. Enabling workstation restrictions here means that all workstations, except for the server workstation, need to be registered with a registration code. Refer to the "Client Authentication Appendix" in the <em>Command Centre Release Note</em> for further detail.</td></tr><tr><td>Invoke automatic logoff after</td><td>Checked by default. Checking this and specifying a time will mean users get logged off after that period of inactivity.<br>(Default = 480 minutes. Range = 1 minute - 1440 minutes, i.e. 24 hours)<br><br><strong>Note:</strong> On a clean install for sites with a NPSA license, the default value will be 15 minutes. If this is changed the new value will be retained after an upgrade.</td></tr><tr><td>Prevent logon at multiple workstations</td><td>The system considers an operator with multiple sessions logged on from a single Windows session as using one workstation license. Checking the <strong>Prevent logon at multiple workstations</strong> checkbox (under "Operator Restrictions") prevents an operator from logging on from multiple Windows sessions.</td></tr><tr><td>Remember Logon Name from last logon</td><td>Checked by default. Each time this control is toggled off or on, operators will need to login one additional time before the change takes effect.<br>When <strong>selected</strong>, the last operator <strong>Logon Name</strong> that logged into Command Centre will be displayed in both the Command Centre and Configuration clients Logon window, and the cursor focus will be on the <strong>Password</strong> field.<br>When <strong>unselected</strong>, the <strong>Logon Name</strong> will be blank in both the Command Centre and Configuration clients Logon window, and the cursor focus will be on the <strong>Logon Name</strong> field.</td></tr></tbody></table>
5. Configure **Operator Lockout** as required:
   1. Specify the number of continual failed attempts before lockout action will occur, in the **Number of failed attempts before lock out** field.

      (Default = 5. Range = 1 - 20)
   2. Click the appropriate radio button to indicate how long the operator will be locked out after that configured number of failed attempts.

      <table><thead><tr><th width="193">Radio button</th><th>This option locks an operator account...</th></tr></thead><tbody><tr><td>Lockout permanently</td><td>immediately (permanently) after the configured number of failed attempts.<br>The account will require a privileged operator to unlock user account. This is the default lockout setting.</td></tr><tr><td>Lockout for &#x3C;specified time></td><td>for a specified period of time, i.e. silently delay (without feedback to the operator) the ability to logon after the configured number of failed attempts. Subsequent failed logon attempts will invoke the same period of time.<br>(Default = 5 minutes. Range = 20 seconds - 60 minutes and 59 seconds)</td></tr></tbody></table>
6. Enable/disable the **Show all cardholder access group memberships** checkbox as required.

   <table><thead><tr><th width="112">When...</th><th>an operator...</th></tr></thead><tbody><tr><td>checked,</td><td>can see ALL Access Groups assigned to a cardholder as long as the operator can see the cardholder.</td></tr><tr><td>unchecked,</td><td>can only see the Access Groups associated with the cardholder when they have "Modify Access Control", "Edit Access Groups" or "View Access Groups" privilege in the division of the Access Group.<br><br><strong>Note:</strong> Before turning off 'Show all Cardholder access group memberships' it is important to ensure that the site has accurately configured all the Access Groups, Operators Groups, Cardholders memberships with the correct divisions and privileges.</td></tr></tbody></table>
7. Enable/disable the **Require Modify Access Control in Cardholder Division** checkbox as required.

   <table><thead><tr><th width="112">When...</th><th>an Operator...</th></tr></thead><tbody><tr><td>checked,</td><td>must have the Modify Access Control privilege both in the division of the Access Group AND in the division of the Cardholder in order to add/modify/remove access.</td></tr><tr><td>unchecked,</td><td>only requires the Modify Access Control privilege in the division of the Access Group in order to add/modify/remove access, no matter what division the cardholder is in (default).</td></tr></tbody></table>
8. Configure the **Single Sign-on** options as required:

   <table><thead><tr><th width="112">Field</th><th>Description</th></tr></thead><tbody><tr><td>Entra ID</td><td>This checkbox only appears if your site is licensed for Entra ID Single Sign-on.<br>If enabled, when an operator launches Command Centre Client on a workstation connected to this server, the system checks if they can be logged on using Entra ID Single Sign-on. Entra ID Single Sign-on is not used for Configuration Client.<br>Operators must be assigned a User ID to use Entra ID Single Sign-on. Refer to <a href="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</a> for details.</td></tr><tr><td>Active Directory</td><td>This checkbox only appears if your site is licensed for Active Directory Single Sign-on.<br>If enabled, when an operator launches either Configuration Client or Command Centre Client on a workstation connected to this server, the system checks if they can be logged on using Active Directory Single Sign-on.<br>Operators must be assigned a Windows logon to use Active Directory Single Sign-on. Refer to <a href="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</a> for details.</td></tr></tbody></table>
9. The **Authentication Tokens** certificate is used to sign JSON Web Tokens, for services that require operators to be authenticated and authorised using a token. Services that require these tokens are generally optional or licensed, so this certificate may or may not be used for your site.

   If you wish to change this certificate, click the Manage Certificates button and select the required option:

   <table><thead><tr><th width="194">Mode</th><th>Description</th></tr></thead><tbody><tr><td>Default Internal Certificate</td><td>The Default Internal Certificate is a self-signed certificate which is generated by Command Centre and stored in the database. It exists to provide a standard option for sites that don't need a custom certificate. The private key is protected by Command Centre's Database Encryption.</td></tr><tr><td>Custom Certificate</td><td>This lets you import your own ECDsa P384 certificate certificate as a PFX or P12 file. The private key will be protected by Command Centre's Database Encryption.</td></tr><tr><td>External Certificate</td><td>An "External" certificate is loaded from the Windows certificate store rather than Command Centre's database.<br>This option requires that you add an ECDsa P384 certificate with a Friendly Name of 'Gallagher Command Centre Token Signer' to Gallagher Applications\Certificates in the Local Machine certificate store.</td></tr></tbody></table>
10. In the **Maximum age of historical manual access events** field, enter the maximum number of days in the past a manual access event can be, when it is created. This affects what date and time an operator can select when creating a manual access event from a Cardholder Viewer. This setting does not delete or affect manual access events that have already been created.

    For more information, refer to the “Creating manual access events for Cardholders” topic in the *Gallagher Command Centre Online Help*.
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/site-installation/server-properties/operator-defaults.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.
