---
title: Face Recognition (Preview)
slug: enterprise/face-recognition-preview
docTags: 
createdAt: 2026-04-08T13:07:58.327Z
---

# How it works

The Face Recognition rule generates an event when a person whose face is enrolled on a watchlist is detected in the scene. Watchlists are collections of people (persons of interest), and each person can have one or more face images attached to them. When Face Recognition is enabled and a face in view matches someone on the selected watchlist, the rule raises an event so an operator can respond. Typical uses include watchlist alerting at controlled entry points, monitoring sensitive zones, and face-linked forensic search.&#x20;



::Image[]{src="https://api.archbee.com/api/optimize/JzHznijrWxPLJLDUaV5A1/X1guIEqXQwTzswmVyjtbB_image.png" size="50" isUploading="false" width="1016" height="966" darkWidth="1016" darkHeight="966" showCaption="false"}

## How it detects

Face Recognition runs as a pipeline split between the Edge and the Core:

1. The Edge first detects a person in the scene.
2. The Edge sends a cropped image of the upper portion of that person to the
   Core.
3. The Core compares that representation against the faces enrolled on the
   watchlist. If it matches a person closely enough, the rule generates an event
   identifying the matched person.

Because recognition depends on first detecting a person and then getting a clear
enough face, image quality, angle, and lighting all affect accuracy.

Face Recognition can be used in more than one way:

- **Real-time watchlist alerting** — raise an event the moment a watchlisted
  person is seen.
- **Investigation / Find Faces** — search recorded video for a person, including
  by an uploaded image.

# How to set up

1. Create a **watchlist** and add the people you want to monitor, attaching one
   or more clear face images to each person.

![](https://api.archbee.com/api/optimize/JzHznijrWxPLJLDUaV5A1/WnUyfu-oaUavH5XwGq03G_image.png)

Here in the watchlist setting, the screen provides an overview of facial recognition license usage, followed by the options to create and manage watchlists.&#x20;

![](https://api.archbee.com/api/optimize/JzHznijrWxPLJLDUaV5A1/BNZ86cm9jwMxZMjTPROrc_image.png)

2. Click **+Add watchlist** and add the faces of relevant people, and give the watchlist a name. The watchlist today only allows one image per person of interest, so be sure that you don't use duplicate images. If you use duplicate images, a warning may show up on the screen like this:&#x20;

![](https://api.archbee.com/api/optimize/JzHznijrWxPLJLDUaV5A1/SmPqFNCthacVWU9TlZtkI_ee06811c-e490-4123-beaa-65f5ab97e38c.png)

![](https://api.archbee.com/api/optimize/JzHznijrWxPLJLDUaV5A1/hCZ1kX644tNrG0jUnRRJx_image.png)

![](https://api.archbee.com/api/optimize/JzHznijrWxPLJLDUaV5A1/P_4r7OCigXx5oYHYfJb98_image.png)

:::hint{type="info"}
**Note:&#x20;**&#x57;hen uploading a face to a watchlist, be sure to use an image of the person that is best captured by a CCTV camera. Here in the screenshot examples, the ones boxed in <font color="#B91C1C">**red**</font> are not the best examples, as the you are indicating to the system that the person's face is captured at head and face level. This can cause **little to no matches** in the detection, as CCTV cameras are typically *not&#x20;*&#x69;nstalled at eye level. In the examples highlighted in <font color="#15803D">**green**</font>, these sorts of examples are most suitable, as they provide the **closest image** to how a person would look like on a CCTV capture.
:::

3. Open the rule tab on a camera, create a new rule, and select **Facial Recognition** as the detection type.&#x20;

![](https://api.archbee.com/api/optimize/JzHznijrWxPLJLDUaV5A1/Sva1RENqNbCkcwcWz-Uf8_image.png)

4. Select the **watchlist** the rule should match against.

::Image[]{src="https://api.archbee.com/api/optimize/JzHznijrWxPLJLDUaV5A1/L-wJ7UBTyYmtz1qVtBcq3_image.png" size="50" isUploading="false" width="332" height="401" darkWidth="332" darkHeight="401" showCaption="false"}

5. Save and activate.

# What to expect

- An event is generated when a face in view matches a person on the selected
  watchlist, and includes the matched person's identity.

::Image[]{src="https://api.archbee.com/api/optimize/JzHznijrWxPLJLDUaV5A1/q5mGXoP5RchnsAA06Akdv_3e958682-714a-4ce5-a572-1bd8a42ff137.png" size="60" isUploading="false" width="656" height="857" darkWidth="656" darkHeight="857" showCaption="false"}

- In this result of events, you may still classify it as a true or false event when opening the event itself.

![](https://api.archbee.com/api/optimize/JzHznijrWxPLJLDUaV5A1/hTOaZnId93LowHdH8q9DY_image.png)

## Best Practices

- Recognition works best with clear, well-lit, reasonably angled-camera facing faces.
  straight angles, motion blur, or low resolution reduce match accuracy. Avoid uploading:
  - Profile pictures from social media
  - Images with heavily obscured faces (sunglasses, wigs, face paint)
  - Images that no longer matches with the person's face (ie: Uploading an image of the person from ten years ago)
  - Images with heavy facial filters
- Face Recognition stores additional face-image data to support investigation
  and searching, which increases storage requirements — plan capacity
  accordingly.
- A rule matches against one watchlist at a time.

