> 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/1key-biometric/overview.md).

# Overview

***

### Components

1Key consists of three components:

* **Auth Server** — Hosted component that manages the configuration, devices, key banks, and API keys. Provides the AuthX UI dashboard for administrators.
* **Auth Agent** — Installed on end-user workstations. Communicates with the Auth Server.
* **Auth Manager** — Installed on end-user workstations. Used by end users for enrollment and account management. The application is known as **ThinC Manager** in the Windows Start menu.

### How users authenticate

After deployment is complete:

1. The administrator authorizes 1Key devices in the Auth Server.
2. End users enroll their fingerprint and security key through the Auth Manager.
3. End users can then log in to any enrolled Windows workstation using their fingerprint and a connected 1Key device — no mobile device required.


---

# 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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.1kosmos.com/authentication/1key-biometric/overview.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.