> 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/administrator-configuration.md).

# Administrator configuration

***

### Enabling Orion Authenticator

When enabled, users in the community see **Orion Authenticator** as an option under the **Setup** menu in their profile. When disabled, the option is hidden.

**Steps**

1. Sign in to the **AdminX** portal as a community administrator.
2. Navigate to **Authentication → Orion Authenticator**.
3. Toggle **Login with Orion Authenticator** to **ON**.
4. Click **Save**.

**Configuring Orion detection wait time**

The login page detects Orion on the workstation through a short polling window. You can configure this window to balance detection reliability against login speed.

**Steps**

1. Navigate to **Authentication → Orion Authenticator** in the AdminX portal.
2. Set the **Orion Detection Wait Time** value in milliseconds.
3. Click **Save**.

{% hint style="info" %}
**Recommended values:** Start with the default and increase only if users on slower workstations report detection failures. Larger wait times delay every login.
{% endhint %}

### Configuring device limits

Two settings under **Authentication → Passwordless Login** control how many devices can be linked to an account and how many accounts can be onboarded to a single workstation:

| Setting                                           | Purpose                                                    |
| ------------------------------------------------- | ---------------------------------------------------------- |
| Max number of devices linked to an account        | Caps how many Orion installations a single account can use |
| Max number of accounts onboarded on single device | Caps how many users can share one Orion installation       |

Adjust these based on your organization's policy on shared workstations.

### Creating an adaptive authentication journey

Adaptive authentication journeys let you require Orion-generated codes as part of an MFA flow — automatically triggered based on risk signals, user attributes, or workstation posture.

**Steps**

1. In the AdminX portal, navigate to **Authentication → Adaptive Authentication**.
2. Click **Add new adaptive auth journey**.
3. Specify a **journey name** and associate a rule (e.g., risk score, user group, network).
4. In the **MFA Required** action, set the **Authentication Method** to **Password & Passcodes from Orion Agent**.
5. Click **Save**.

The journey now applies to any login that matches the associated rule. Users in scope are required to provide their password plus a code generated by Orion.

### **Monitoring onboarding events**

When a user successfully onboards an account through Orion, an `E_USER_ONBOARDED` event is generated in the AdminX event log. This event includes:

* The user's identity
* The workstation where onboarding took place
* Timestamp and origin
* Any associated posture data from the Orion health agent

To view onboarding events:

1. In the AdminX portal, navigate to **Reports → Event Logs**.
2. From the **Event** drop-down, select **E\_USER\_ONBOARDED**.

For more information on events, see Event Logs.


---

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