> 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/admin-portal/authentication/configure-device-restriction-policy.md).

# Configure Device Restriction Policy

Enforce device enrollment limits by user group or username to reduce unauthorized device sprawl and strengthen authentication governance across your 1Kosmos community

***

A Device Restriction Policy defines how many devices of each type a user can enroll for authentication. Policies are applied by group membership, username, or both — giving administrators precise control over device enrollment without enforcing a single rule across all users.&#x20;

### How It Works&#x20;

When a policy is active, 1Kosmos enforces the Max Allowed count for each configured device type. Users who reach their limit can continue using existing enrolled devices but cannot register new ones until an existing device is removed.&#x20;

If a device type is not included in a policy, its allowed count is considered 0 — meaning users covered by that policy cannot enroll devices of that type.&#x20;

If multiple policies apply to the same user, the most restrictive policy for each device type takes effect independently.&#x20;

**Example**:&#x20;

* Policy 1 allows 3 Smartphones, 1 Platform Authenticator, 1 Orion Authenticator&#x20;
* Policy 2 allows 1 Smartphone, 2 Platform Authenticators&#x20;

The user is allowed: 1 Smartphone (Policy 2), 1 Platform Authenticator (Policy 1), 0 Orion Authenticators, 0 Security Keys.&#x20;

{% hint style="info" %}
Device Restriction Policies govern future enrollment only. Existing enrolled devices are not affected when a policy is created or updated. If a user already has more devices than the policy allows, the restriction applies the next time they try to add a new device. &#x20;
{% endhint %}

**Before You Begin**&#x20;

Only Community Administrators can create and manage Device Restriction Policies.&#x20;

For **group-based policies**, ensure the following are in place before creating a policy:&#x20;

* Group information is available from Active Directory or Microsoft Entra.&#x20;
* User Attribute Mapping is configured to capture the key-value pair corresponding to user groups.&#x20;

To navigate to Device Restriction Policies&#x20;

1. Sign in to AdminX.&#x20;
2. Go to **Authentication > Device Restriction Policy**.&#x20;

All configured policies are listed with their name, conditions, allowed devices, and status.

#### Create a Device Restriction Policy

1. Click **Create New**.&#x20;
2. Enter a Policy Name.&#x20;
3. The Enabled toggle is on by default. Turn it off to save the policy without activating it.&#x20;
4. Under Conditions, define who the policy applies to. You can add one or both condition types:&#x20;
   1. **Group** — Enter AD group names. Select is one of or is not one of and add one or more group values.&#x20;
   2. **Username** — Enter specific usernames. Select is one of or is not one of and add one or more values.&#x20;
   3. Click + to add values to a condition. Click Add another to add a second condition row. Multiple conditions are applied using logical AND.&#x20;
5. Under **Allowed Device**, select a **Device Type** and set the **Max Allowed** count. Add additional device types as needed.&#x20;
6. Click **Save**. The policy is enforced immediately after saving.

Use a Username condition when AD groups are not available or when you need a more restrictive policy for specific users.

| Device Type            | Description                             | Min Allowed | Max Allowed |
| ---------------------- | --------------------------------------- | ----------- | ----------- |
| Smart Phones           | 1Kosmos mobile app                      | 1           | 3           |
| Platform Authenticator | Security key on Windows Hello and macOS | 1           | 2           |
| Security Key           | 1Key and security keys on Android/iOS   | 1           | 3           |
| Orion Authenticator    | Orion-based authentication              | 1           | 2           |

#### &#x20;Edit a Policy&#x20;

1. On the **Device Restriction Policy** page, click the edit icon in the Actions column.&#x20;
2. Update the configuration and click **Save**.&#x20;

Changes take effect immediately after saving.&#x20;

#### Disable a Policy&#x20;

Disabling a policy pauses enforcement while keeping the policy definition intact. Users previously covered by this policy will fall back to the next applicable policy, or to default device restrictions if no other policy applies.&#x20;

1. Click the edit icon for the policy.&#x20;
2. Turn off the Enabled toggle.&#x20;
3. Click Save.&#x20;

#### Delete a Policy&#x20;

1. Click the delete icon in the Actions column.&#x20;
2. Confirm the deletion.&#x20;

Deleting a policy removes all restrictions it enforced. Users previously covered will fall back to the next applicable policy or to default device restrictions.&#x20;

**Note:** Deleted policies are permanently removed and cannot be recovered. &#x20;

#### Audit Events&#x20;

Device Restriction Policy actions are logged under **Reports > Event Logs.**

| Event                      | Description                                 |
| -------------------------- | ------------------------------------------- |
| E\_DEVICE\_POLICY\_CREATED | A new Device Restriction Policy was created |
| E\_DEVICE\_POLICY\_UPDATED | An existing policy was modified             |
| E\_DEVICE\_POLICY\_DELETED | A policy was permanently deleted            |


---

# 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/admin-portal/authentication/configure-device-restriction-policy.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.
