> 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/deny-list-face-match.md).
# Face Screening
Use facial recognition to check whether a visitor resembles someone on your Deny List or People Lists. Face Screening works independently of ID-based [Security Screening](/guest/configuration/guest-security-screening.md), providing organizations with another way to identify visitors who shouldn't be on-site. If Guest finds a resemblance, a Guest user reviews the result in Command before entry is allowed.
***
## Enable Face Screening
### Organization level
{% hint style="danger" %}
You need **Org Admin** permissions to enable Face Screening.
{% endhint %}
By default, Face Screening is disabled for an entire Command organization. You need to enable it at the organization level before you can enable it for a Guest Type.
{% stepper %}
{% step %}
**In Verkada Command, go to All Products > Workplace > Guest.**
{% endstep %}
{% step %}
**On the left navigation, click Guest Settings.**
{% endstep %}
{% step %}
**Under Organization > Security & Data, toggle on Enable Face Screening.**
{% endstep %}
{% endstepper %}
### Guest Type
{% hint style="danger" %}
* You need **Org Admin** permissions to enable Face Screening for a Global Guest Type.
* You need **Workplace Site Admin** permissions to enable Face Screening for a site-level 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 %}
**On Guest Settings > Organization, scroll down to Guest Types and click Manage Guest Types.**
{% endstep %}
{% step %}
**Select the desired Guest Type.**
{% endstep %}
{% step %}
**Add the Badge Photo step and enable Face Screening.**
Face Screening can screen against two sources: the Guest Deny List and Camera People Lists. Admins can select which sources to use for Face Screening. Select which Camera People Lists to use from the search bar.
{% endstep %}
{% step %}
**Click Save Changes.**
{% endstep %}
{% endstepper %}
{% hint style="warning" %}
Face Screening is unavailable in Portland, Oregon, and Illinois.
{% endhint %}
***
## Review Face Screening results
Face Screening results only appear when a visitor signs in through a Guest Type with Face Screening enabled and resembles a flagged profile. A Guest user must review the result in Command before entry is allowed.
If Face Screening results are confirmed by a Guest user, the visitor will be denied, and notifications are sent to all contacts listed in [staff notifications](/guest/configuration/guest-security-screening/security-screening-settings.md#staff-notifications). Guest users can override denials due to a confirmed Face Screening result in the visit details panel.
***
## Data retention
The face data used for Face Screening is deleted immediately after the check.
The system sends a PDF record of the issue to all [staff notification contacts](/guest/configuration/guest-security-screening/security-screening-settings.md#staff-notifications) if a Face Screening result is confirmed. This record is available on Command for the shorter of the [Retention of Saved Identification Info](/guest/configuration/guest-security-screening/security-screening-settings.md#retention-of-saved-identification-info) and [Retention of Visit Records](/guest/configuration/manage-data-retention-in-guest.md).
***
## FAQ
Does Face Screening work for Guest Events?
Yes, [Guest Events](/guest/configuration/guest-events.md) that use a Guest Type with Face Screening enabled will run invited guests through the Face Screening check in advance.
Does Face Screening work for Approved List applications?
Yes, [Approved List](/guest/configuration/approved-lists-for-guest.md) applications support Face Screening.
---
# 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/deny-list-face-match.md?ask=&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.
