> 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/verkada-cameras/configuration/security-and-privacy/lpr-search-reason-and-audit.md).

# LPR Search Reason & Audit

Require an offense reason and case/incident number for every license plate search

Users must enter an offense type and case number before searching for or accessing license plate data in Command. The incident information entered is saved directly to an organization’s audit log for maximum visibility into who accessed LPR data, when, and for what purpose.

{% hint style="danger" %}
You need Org Admin permissions to enable this feature in your Command organization through [Feature Manager](/command/organization-settings/manage-your-admin-page-settings/feature-manager.md).
{% endhint %}

***

## Search for a license plate or vehicle

{% stepper %}
{% step %}
**In Verkada Command, go to All Products > Cameras.**
{% endstep %}

{% step %}
**In the left navigation, select Vehicles.**

{% hint style="warning" %}
You will not be able to view vehicles or licenses plates without providing an Offense Type and Case/Incident number.
{% endhint %}

<div data-with-frame="true"><figure><img src="https://1795869993-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FylYKicREo6JpuOJH4teK%2Fuploads%2FyrWMEth6TTbrRA12d8E9%2FScreenshot%202026-08-27%20at%2012.25.31%E2%80%AFPM.png?alt=media&amp;token=754762a7-262e-4197-ba7a-c0aae6a3c0d4" alt=""><figcaption></figcaption></figure></div>
{% endstep %}

{% step %}
**Enter an Offense Type.**

Select one or more appropriate offense types from the dropdown list. If you believe the Offense Type dropdown does not contain the correct description, you may select "*Other*” and customize your reason.&#x20;
{% endstep %}

{% step %}
**Enter a Case / Incident Number.**

Enter the case or incident number associated with your search.&#x20;

<div data-with-frame="true"><figure><img src="https://1795869993-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FylYKicREo6JpuOJH4teK%2Fuploads%2FTxazfql1FTiYrTMDFyQv%2FScreenshot%202026-08-27%20at%2012.26.04%E2%80%AFPM.png?alt=media&amp;token=c56b4340-461e-49cd-b72f-6b9e283e247a" alt=""><figcaption></figcaption></figure></div>
{% endstep %}

{% step %}
**(Optional) Use the search bar and filters to tailor your results.**

<div align="left" data-with-frame="true"><figure><img src="https://1795869993-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FylYKicREo6JpuOJH4teK%2Fuploads%2FKH7BdRKY4NGpHASWs2hG%2FScreenshot%202026-08-27%20at%2012.26.34%E2%80%AFPM.png?alt=media&amp;token=704e36b0-0975-481d-9ccf-1a2d59e1188e" alt=""><figcaption></figcaption></figure></div>
{% endstep %}

{% step %}
**Click Search to view the results.**

{% hint style="warning" %}
Results will populate when you click **Search**. Every new search requires a reason and case number.
{% endhint %}
{% endstep %}
{% endstepper %}

***

## View searches in the audit log

{% stepper %}
{% step %}
**In Verkada Command, go to All Products > Admin.**
{% endstep %}

{% step %}
**In the left navigation, select Security & Logs > Audit Log.**
{% endstep %}

{% step %}
**Filter the logs by the event type "Vehicle Searched" and view all searches within your Command organization.**

<div align="left" data-with-frame="true"><figure><img src="https://1795869993-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FylYKicREo6JpuOJH4teK%2Fuploads%2FlO4Z27ur8LMOXKmFveXT%2Flpr.png?alt=media&amp;token=e4b8e54e-4cef-4574-b3bf-0f5152de8f27" alt=""><figcaption></figcaption></figure></div>
{% endstep %}
{% endstepper %}


---

# 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://help.verkada.com/verkada-cameras/configuration/security-and-privacy/lpr-search-reason-and-audit.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.