> 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/command-centre-client/getting-started/fido2-credentials/enforcing-fido2-multi-factor-logon.md).

# Enforcing FIDO2 Multi-factor Logon

### Introduction

Enforcing FIDO2 Multi-factor logon is configured via Operator Groups. Therefore, all cardholders that are required to logon to Command Centre using a FIDO2 authenticator must be members of an Operator Group that has FIDO2 Multi-factor logon enforced.

Operators require one of the following operator privileges to enforce FIDO2 Multi-factor logon:

* Advanced User
* Edit Site and Edit Operators

### Prerequisite

Before proceeding with this procedure FIDO2 Credentials need to be enrolled against cardholders. See [Enrolling FIDO2 Credential against Cardholder](https://help.security.gallagher.com/knowledge-hub/command-centre-client/getting-started/fido2-credentials/enrolling-fido2-credential-against-cardholder.md) for the procedure.

### Procedure

1. Select the **Administration** tab on the Command Centre title bar, and then click the **Operator Groups** button on the toolbar.

   The Operator Groups Viewer opens.
2. Click on the Operator Group that you want to enforce FIDO2 Multi-factor logon for.

   ![](https://2455150842-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fi6UYAoyykM6nimMN9yss%2Fuploads%2Fgit-blob-36c256109d5825e0ded33088861e1a341fb4de7b%2Ffido2_enforcemultifactor.png?alt=media)
3. Check the **Enforce FIDO2 multi-factor logon** checkbox.

   **Note:** This checkbox will be disabled (greyed out) if FIDO2 Credentials have not been enrolled against cardholders.
4. Click the **Save** button.


---

# 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/command-centre-client/getting-started/fido2-credentials/enforcing-fido2-multi-factor-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.
