---
locale: "en"
updated_at: "2025-12-17T10:07:17.945Z"
canonical: "https://www.isdecisions.com/en/userlock/docs/reference/access-policies/machine-restriction"
---

# Machine restrictions

Rules to control allowed or denied machines.

## Typical use cases

- Ensure sensitive accounts (e.g., administrators, finance) can log on only from secured or dedicated machines.
- Prevent users from connecting from unmanaged or shared devices.
- Restrict VPN or terminal sessions to specific sets of machines.

![](https://a.storyblok.com/f/122374/863x828/ab0584a0f3/machines-authorized-name-ip-ou.png)

## Key points to know

- Policies can target individual users, groups, or organizational units.
- Modes available:
  - **Authorized** → Logon only from the listed machines are allowed.
  - **Denied** → Logon only from the listed machines are blocked.
- Machines can be added by:
  - **Machine name** (manual entry or LDAP search).
  - **IP range** (start and end IP included).
  - **Organizational unit** (select via LDAP).
- Restrictions can apply per **session type** (workstation, terminal, Wi-Fi/VPN, IIS).
- For Wi-Fi sessions, restrictions are enforced using **MAC addresses**.
- For other session types, restrictions use **IP addresses** and, when available, NetBIOS names.

> **Best practice**
>
> Use *Authorized* mode for high-security accounts, as it provides stricter control.

## Configured policies

A list of all machine restriction policies is available in the **Access Policies** section, under the **Machine restrictions** page.

![](https://a.storyblok.com/f/122374/1671x750/827e273972/machine-restrictions-table.png)
