> 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/passwordless-for-web-apps/adaptive-authentication.md).

# Adaptive Authentication

Adaptive Authentication verifies the user's identity based on factors such as location, device status, and end-user context.

***

### What you can do with it

Adaptive Authentication offers several business scenarios that enhance security and user experience:

* **Deny access** — block access for specific users or groups when they match predefined conditions, such as IP address range, group membership, or application access.
* **Request specific authentication factors** — require additional factors such as one-time passwords (OTP), push notifications, or biometric authentication for higher-risk applications, sensitive transactions, or both.
* **Different rules for inside and outside networks** — apply separate authentication policies for internal versus external network access. For example, stricter requirements can be enforced for external access to ensure security compliance.
* **Grant access** — bypass authentication for specific applications when users are within a designated network range, avoiding redundant authentication (for example, when users would otherwise be prompted again while already inside the same network). When access has been bypassed for an application, users log in directly using username or QR code without being asked for additional authentication factors.

### Configure it

Adaptive Authentication is set up in the Admin Portal, where administrators create journeys by defining conditions and decision actions. For prerequisites and step-by-step configuration, see [Configure Adaptive Authentication.](/authentication/admin-portal/authentication/configure-adaptive-authentication.md)


---

# 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/passwordless-for-web-apps/adaptive-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.