# Device Lock

The **Device Lock** feature allows administrators to remotely lock a managed device from the device from console. When a device is locked, user access to the device is restricted until an administrator unlocks it.

This feature is typically used in situations such as:

* Lost or stolen devices
* Security incidents
* Temporary administrative control
* Policy violations

## 1. Devices List

Administrators can view all enrolled devices from the **Devices** page. This page provides an overview of the device fleet and allows administrators to perform management actions.

The device table includes information such as:

* Device Name
* Assigned Profile
* Device Group
* Status
* Battery Level
* Device Manufacturer
* Operating System
* IMEI
* Serial Number
* Last Seen
* Enrolment Date

Administrators can open the **device action menu** to perform operations such as clearing data, locking the device, or deleting the device.

<figure><img src="/files/EUqdTA4gY1innbMzsGg7" alt=""><figcaption></figcaption></figure>

## 2. Locking a Device

From the **Devices list**, administrators can lock a device using the action menu.

#### Steps

1. Navigate to **Devices**
2. Locate the device in the list
3. Open the **Actions menu (⋮)**
4. Click **Lock Device**

This will open the **Lock Device dialog**.

## 3. Lock Device Dialog

The **Lock Device** dialog requires administrators to confirm the action and provide a reason for locking the device.

#### Fields

| Field  | Description                                              |
| ------ | -------------------------------------------------------- |
| Device | Displays the selected device identifier                  |
| Reason | Required field to explain why the device is being locked |

The reason field supports up to **500 characters**.

<div align="left"><figure><img src="/files/iJgG9S2qN6XeJYQMAH6d" alt=""><figcaption></figcaption></figure></div>

## 4. Security Warning (FRP)

When locking a device, the system displays the following warning:

> If **Factory Reset Protection (FRP)** is not configured in the device policy, the device can be **hard reset and reused**.

To ensure device security, administrators should configure **FRP within the device policy profile**.

## 5. Locked Device Status

Once a device is locked:

* The **device status changes to LOCKED**
* The lock action is recorded
* The administrator who performed the action is logged

Locked devices are clearly marked in the **Devices table**.

<figure><img src="/files/Qka3DaYnnMjfeqWRoorz" alt=""><figcaption></figcaption></figure>

## 6. Viewing Lock Details

When a device is locked, administrators can view detailed information about the lock event.

The **Device Locked dialog** displays:

| Field     | Description                         |
| --------- | ----------------------------------- |
| Device    | Device identifier                   |
| Reason    | Reason the device was locked        |
| Locked On | Timestamp of the lock event         |
| Locked By | Administrator who locked the device |

<div align="left"><figure><img src="/files/A8XxNj8ITM5ty1ijC7Ib" alt=""><figcaption></figcaption></figure></div>

## 7. Unlocking a Device

Administrators can unlock a device once the issue is resolved.

#### Steps

1. Open the **Device Details page**
2. Click **Unlock Device**
3. Provide a **reason for unlocking**
4. Confirm the action

<div align="left"><figure><img src="/files/OMqMk7qQ9GjavcYvOv9N" alt=""><figcaption></figcaption></figure></div>

## 9. Best Practices

To maintain device security:

* Always provide clear **lock and unlock reasons**
* Enable **Factory Reset Protection (FRP)** in device policies
* Review locked devices regularly
* Maintain an audit trail for administrative actions


---

# Agent Instructions: 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:

```
GET https://docs.cubilock.com/device-lock.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.
