> 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/sync-lists-for-access-control-and-guest.md).

# Sync Lists for Access Control and Guest

Sync Lists allow you to automatically populate People Lists with your Access Control users and Guest visitors, so cameras can automatically recognize them based on face detection.&#x20;

You can sync from two sources:

* **Access Control** imports users and uses their profile pictures to create unique profiles.&#x20;
* **Guest** imports visitors when they sign in and uses their face shot to create profiles.&#x20;

{% hint style="warning" %}
Before you create a Sync List, confirm that you have all required consents to use facial recognition for the people in the list. Command asks you to confirm this on the last step.
{% endhint %}

***

{% tabs %}
{% tab title="Access Control" %}

### Sync Access Control users

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

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

{% step %}
**Next to Sync Lists, click** <i class="fa-plus">:plus:</i> **and select Sync with Access Control.**
{% endstep %}

{% step %}
**From the Access Control dialog box, select a Directory.**
{% endstep %}

{% step %}
**(Optional) Click Exclude groups and search for any Access Control groups whose users should not be synced.**
{% endstep %}

{% step %}
**(Optional) Turn on Keep deactivated users to move deactivated users to a separate list instead of removing them.**

You can choose how long deactivated users are kept before they are permanently deleted.
{% endstep %}

{% step %}
**Select the checkbox confirming that you have all required consents to use facial recognition to create identities with face data for the users synced to this list.**
{% endstep %}

{% step %}
**Click Create.**

Command starts the sync in the background. The sync can take a few minutes, depending on how many users are in the list. You can see progress on the Sync List page.

{% hint style="info" %}
Once the import completes, the list header shows the total number of users and when it last updated.&#x20;
{% endhint %}
{% endstep %}
{% endstepper %}

***

#### Low-quality or missing profile pictures  <a href="#excluded" id="excluded"></a>

Users who do not have a profile picture, or have a picture that does not meet the quality criteria, will still be synced but will need to have their photos updated to be recognized and associated on cameras.&#x20;

#### Review deactivated users <a href="#deactivated" id="deactivated"></a>

On a Sync List, use the tabs at the top to switch between **Active** and **Deactivated**. Deactivated users stay on the list until the expiry you set when you created it.
{% endtab %}

{% tab title="Guest" %}

### Sync Guest visitors

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

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

{% step %}
**Next to Sync Lists, click** <i class="fa-plus">:plus:</i> **and select Sync with Guest.**
{% endstep %}

{% step %}
**Open the Guest type dropdown and choose a type.**

Types are grouped by **Global** and by site. You can search the list.
{% endstep %}

{% step %}
**Under Expire people from the list, enter the number of days after sign-in when a visitor is removed.**

The field starts at 1 day. You can set it up to 90 days.
{% endstep %}

{% step %}
**Select the facial recognition consent checkbox.**
{% endstep %}

{% step %}
**Click Create.**

The new list appears under **Sync Lists**, in the **from Guest** group. Visitors show a **Signed In** or **Signed Out** badge, depending on their visit status.
{% endstep %}
{% endstepper %}
{% endtab %}
{% endtabs %}


---

# 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/verkada-cameras/configuration/sync-lists-for-access-control-and-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.
