> 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/guest/configuration/connect-people-lists-to-guest.md).

# Connect People Lists to Guest

Integrate visitor management with advanced camera analytics

A [People List](/verkada-cameras/analytics/people-analytics/create-a-person-of-interest.md) is a powerful tool for organizing people of interest. Verkada Guest integrates with People Lists to allow organizations to utilize advanced camera features with visitors.

When a visitor signs in using a Guest Type linked to a People List, they are automatically added to the list. Their POI profile will include the full name provided at sign-in and the photo captured during the badge photo step. When the visitor signs out, they are automatically removed from the People List.

{% hint style="danger" %}
Face Detection must be enabled in Feature Manager to configure this integration.
{% endhint %}

***

## Configuration

{% hint style="danger" %}
You need at least **Workplace** **Site Admin** permissions to link a People List to a Guest Type.
{% endhint %}

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

{% step %}
**On the left navigation, click Guest Settings.**
{% endstep %}

{% step %}
**At the top, select Sites > your site.**
{% endstep %}

{% step %}
**Under Guest Types, click Manage Guest Types.**
{% endstep %}

{% step %}
**Select a Guest Type.**
{% endstep %}

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

a. Select **Badge Photo** (if already not added)**.**\
b. Select **Add Guest to People List** and choose a People List from the dropdown.
{% endstep %}

{% step %}
**Click Check-in / Check-out and select Standard Visit.**
{% endstep %}

{% step %}
**Click Save Changes.**
{% 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 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/guest/configuration/connect-people-lists-to-guest.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.