> For the complete documentation index, see [llms.txt](https://help.verkada.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.verkada.com/command/security/privacy-and-security-disclosure/restricted-devices.md).

# Restricted Devices

Learn what to do when you discover a restricted device in your organization

When a device is *restricted*, it means that Verkada has determined that this device has been lost or stolen.

***

## How Verkada restricts a device

{% stepper %}
{% step %}
**We alert the Organization Admins (Org Admins) on the organization the device is claimed to.**
{% endstep %}

{% step %}
**After 48 hours, the device is removed from the Verkada Command org and blocked from being added to other orgs.**
{% endstep %}
{% endstepper %}

### Contact Verkada Support

If you receive an email about a restricted device, contact [Verkada Support](https://www.verkada.com/support/) as soon as possible.

{% hint style="warning" %}
For security reasons, we do not mention the device that has been restricted. Contact [Verkada Support](/command/need-help/contact-verkada-support.md) for assistance.
{% endhint %}

***

### Example emails you may receive

#### Example 1

**Subject**: \[Action Required]: Restricted Device Found

**Body**: One of the devices in the Organization has been marked as restricted. This device will be permanently removed from your organization 48 hours from the date this email is sent. If you believe this device has been restricted in error, please contact our support team immediately.

<div align="left" data-with-frame="true"><img src="https://705858581-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FNRq5qDDjsYNxwNzF1bcB%2Fuploads%2Fgit-blob-4318b01c4ee038066128c230c76078fd5aa7bb4b%2Fcb53f502cfbd324194b30daa215c13b378544a1c.png?alt=media" alt=""></div>

### Example 2

**Subject**: Restricted Device Removed from Command

**Body**: One or more of the devices in the Organization has been removed from your Command organization. This means the device was marked as restricted on or after and can no longer be added to an organization. If you believe this device has been removed in error, please contact our support team immediately.

<div align="left" data-with-frame="true"><img src="https://705858581-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FNRq5qDDjsYNxwNzF1bcB%2Fuploads%2Fgit-blob-05fb605f47007c801aea68010b848b40bb53bc5b%2F87557dab78ec3409e6643cb7b7e94c7b1e0620ff.png?alt=media" alt=""></div>


---

# 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://help.verkada.com/command/security/privacy-and-security-disclosure/restricted-devices.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.