# Camera Smart Lists

Smart Lists provide visibility into new or frequently seen people across your organization. They update automatically to provide timely insights without requiring manual effort.

* **New People** – Individuals appearing only a few times.
* **Frequently Seen People** – Individuals who appear repeatedly.

Smart Lists refresh as new detections occur to keep activity data current.

### Why use Smart Lists

* Identify new people as soon as they appear.
* Track frequently seen people to understand recurring activity.
* Streamline reviews with automatic updates.
* Filter out irrelevant results by excluding existing lists or marking individuals as known.

{% hint style="info" %}
After you create a Smart List, you can enable [Smart List alerts](/verkada-cameras/analytics/create-camera-event-alerts/smart-list-alerts.md).
{% endhint %}

***

### Requirements

* Face Detection must be enabled on the camera(s).
* Stricter filtering criteria apply compared to general face detection:
  * Faces must occupy a larger portion of the frame.
  * Side profiles are excluded; a **straight-on view** is required.
  * Clear, well-lit captures improve accuracy.

***

## Smart Lists

{% hint style="danger" %}
You need at least **Site Viewer** permissions for the site the camera is in to create and manage Smart Lists.
{% endhint %}

### Create a Smart List

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

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

{% step %}
**Next to Smart List, click** <i class="fa-plus">:plus:</i>**.**

a. Enter a unique name.\
b. Select the camera(s) to use for detection.\
c. Toggle off **Access: Public** if you want the list only to be accessible to you.

* **Public** – Visible to others with access to at least one camera in the list. Results are limited to the cameras they can access. Others cannot modify the list but can mark people as known.
* **Private** – Only visible to you.

f. Under **Exclude people list from detections,** enter people lists you do not want to appear in the detections. This ensures Smart Lists remain focused only on relevant new or recurring appearances.\
g. Click **Save.**
{% endstep %}
{% endstepper %}

### Manage a Smart List

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

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

{% step %}
**Under Smart List, select your list.**
{% endstep %}

{% step %}
**Under a person thumbnail select** <i class="fa-angle-down">:angle-down:</i>**. You can:**

a. Download Image\
b. Search by Face\
c. Mark as Known
{% endstep %}
{% endstepper %}

{% hint style="warning" %}
When a person is marked as known, they will no longer show up as a new or frequent person.
{% endhint %}

### Remove a marked known person

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

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

{% step %}
**Under Smart List, next to your list, select** <i class="fa-ellipsis">:ellipsis:</i>**.**

a. Select **View known people list.**\
b. In the top right of a person profile, select <i class="fa-trash">:trash:</i>.
{% endstep %}
{% endstepper %}

***

## Best practices

* Place cameras in well-lit, high-traffic entry points where faces are clearly visible.
* Periodically review Smart List results, marking known individuals or excluding lists to keep insights focused and valuable.
* For best results, configure Smart Lists with a smaller set of relevant cameras rather than all cameras. Using a smaller camera batch helps to improve accuracy and makes it easier to manage people.


---

# 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://help.verkada.com/verkada-cameras/analytics/people-analytics/camera-smart-lists.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.