> 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/1kosmos-mobile-application/application-usecase.md).

# Application Usecase

***

### Workstation MFA

**Replace Windows password prompts with strong, biometric-backed authentication.**

Using the **Windows Workstation MFA Agent**, users can log in to their workstations with:

* A **push notification** approval from the 1Kosmos app
* A 30-second workstation one-time passcode (OTP) displayed in the app
* **Biometric confirmation** on their mobile device

{% hint style="info" %}
Workstation OTP refreshes every 30 seconds and works without network connectivity, making it ideal for remote workers and disconnected environments. 
{% endhint %}

**Best for:** Enterprises looking to eliminate password resets, comply with MFA mandates, and reduce credential phishing risk.

***

### Passwordless web login

**Let users log in to your website or app by scanning a QR code — no usernames, no passwords.**

The flow:

1. Visit the login page and locate the QR code.
2. Open the 1Kosmos app and tap **Scan QR Code**.
3. Authenticate with biometrics or PIN.
4. You are logged in instantly on the website.

**Best for:** Consumer-facing platforms, customer portals, and shared devices where typing credentials is cumbersome.

***

### High-assurance identity proofing

**Verify user identity to National Institute of Standards and Technology (NIST) Identity Assurance Level 2 (IAL2) standards**

The 1Kosmos app supports identity proofing via:

* **Driver's License** scanning (front + back) with selfie liveness check
* **Passport** scanning, with optional radio-frequency identification (RFID)-based verification
* **Social Security Number** verification
* **LiveID** real-time selfie capture for liveness assurance

**Best for:** Banks, healthcare, regulated industries, and any service requiring KYC or identity verification before granting access.

***

### Application & VPN access

**Legacy time-based one-time password (TOTP) fallback for backward compatibility**

* **Push notification MFA** for OpenID Connect (OIDC) and Security Assertion Markup Language (SAML)-integrated apps
* **Account-specific OTP** for legacy apps
* **Legacy TOTP fallback** for backward compatibility
* **Per-account context** — manage multiple apps from a single mobile experience

**Best for:** IT teams adding MFA to existing applications, including VPNs, SaaS tools, and internal systems.

***

### Digital credential sharing

**Users carry verifiable credentials in their wallet and share them on demand.**

The 1kosmos app acts as a verifiable credential provider. It issues W3C-compliant credentials that users store in their digital wallet

Examples include:

* Employment credentials issued by an employer
* Educational credentials from a university
* Healthcare credentials from a provider
* Membership or licensing credentials from an authority

{% hint style="success" %}
**Selective disclosure** allows users to share only the specific attributes a relying party needs - e.g., proving they're over 21 without revealing their birthdate. 
{% endhint %}

**Best for:** Verifiable credential ecosystems, decentralized identity (DID) implementations, and privacy-respecting age/credential verification.

***

### Quick comparison

| Use case                    | Primary auth method    | Identity assurance   |
| --------------------------- | ---------------------- | -------------------- |
| Workstation MFA             | Push / Workstation OTP | Standard             |
| Passwordless web login      | QR + biometric         | Standard             |
| High-assurance proofing     | LiveID + ID docs       | NIST IAL2            |
| App / VPN access            | Push / TOTP            | Standard             |
| Verifiable credential share | Biometric + VC sign    | High (issuer-signed) |


---

# 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/1kosmos-mobile-application/application-usecase.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.