> 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/orion-desktop-authenticator/adminx-configuration.md).

# AdminX Configuration

Orion Authenticator must be enabled and configured in AdminX before it becomes available to users.

***

### **Enabling Orion Authenticator**

This step allows users to onboard Orion and use it for authentication.

1. Navigate to **Authentication > Orion Authenticator**
2. Enable **Login with Orion Authenticator**
3. Click **Save**

### **Configuring Orion detection behavior**

Community administrators can now configure how long the UI waits for a response from Orion using a new setting, **Orion Detection Wait Time**. This setting specifies the wait time (in milliseconds) for the login page to detect Orion on the workstation.

### **Creating authentication journeys with Orion**

Orion passcodes can be used as part of authentication flows.

1. Navigate to **Authentication > Adaptive Authentication**
2. Create or edit a journey
3. Select MFA action: **Password & Passcodes from Orion Agent**
4. Click **Save**


---

# 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/orion-desktop-authenticator/adminx-configuration.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.