> For the complete documentation index, see [llms.txt](https://docs.1kosmos.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.1kosmos.com/authentication/windows-workstation-mfa/capabilities/fallback-authentication.md).

# Fallback Authentication

Windows sign-in normally relies on a user's primary authentication method, but sometimes that method won't work—a typing pattern may drift enough to fail Behavioral Authentication, or a user may simply forget their PIN. If left unresolved, these situations can lock a user out of their workstation.

Fallback Authentication gives administrators a safety net for exactly these cases. You can define a secure secondary path that lets a locked-out user regain access through a temporary one-time passcode (OTP) issued by the Helpdesk. After signing in with the passcode, the user can reset the failed factor — such as Behavioral Authentication or PIN — and continue.

For complete setup, configuration, and the end-to-end login experience, see [Fallback Authentication](https://docs.1kosmos.com/authentication/windows-workstation-mfa/authentication-methods/fallback-authentication).


---

# 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://docs.1kosmos.com/authentication/windows-workstation-mfa/capabilities/fallback-authentication.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.
