Restricted zone check
The original source page (docs/video/III-guides/3-kiem-tra-vung-gioi-han.md) had only section headers with no body content. Confirmed against the Portal (2026-07-21): this feature is real, and its actual name on the Portal is Detection Event = "Restricted Area Alert" (in the Event Detection tab when creating a task). The Zone Configuration interface was also observed directly (see Configuring ROI zones), but only on a Shift meeting task — that screen showed only 2 tabs, ROI and EXCLUSION, with no separate "Restricted" tab.
Remaining open point: whether the Zone Configuration for an actual Restricted Area Alert task shows a third tab is still unconfirmed, despite trying multiple approaches: the current test account has no existing task of this type (0 results on search), and repeated attempts to create a new task for testing failed due to a rendering bug in the Location/camera dropdown when automated via script. Resolving this needs either someone with Portal access to check manually, or a test account that already has a task of this type. The "Configuration" section below still relies partly on inference from the intrusion-detection backend service's technical README for the zone-drawing step.
The restricted zone check feature detects people entering restricted areas and sends real-time alerts with evidence images of the violation.
How it works
This feature shares the same ROI mechanism as other features (see Configuring ROI zones), plus a third zone type dedicated to intrusion detection:
| Zone type | Role |
|---|---|
| Inclusive | The area the AI tracks objects in |
| Exclusive | The area excluded from analysis |
| Restricted | The forbidden area — detecting a person entering it triggers an alert |
When a person is detected inside a restricted zone continuously for longer than a minimum duration (dwell time — a system-configured default, used to avoid false alerts for people just passing by), the system logs a violation, saves an evidence image, and sends an alert to the Platform Backend.
The dwell-time threshold distinguishes someone genuinely intruding/stopping in the restricted area from someone just passing through the frame — similar to how the system distinguishes "customers" from "others" in presence reports (see Report types reference).
Prerequisites
- The camera is positioned to cover the entire restricted area you need to monitor.
- An ROI has been drawn for the camera, with the restricted zone covering the forbidden area exactly — see Configuring ROI zones.
Configuration
- Go to Operations → Tasks → click Create New.
- On the General Information tab: name the task, choose the location and camera to monitor.
- Switch to the Event Detection tab → choose Detection Event = Restricted Area Alert.
- Choose a video source (Live stream or Playback), and set Confidence Threshold / Trigger Interval / Duration Classification Threshold if needed — see Configuring Task AI.
- (Needs further verification) Click the Zone Configuration icon on the newly created task's row, and draw the restricted zone on the canvas — see the general process in Configuring ROI zones. Whether this task type shows a dedicated "Restricted" tab (instead of just ROI/EXCLUSION as observed on a Shift meeting task) hasn't been directly confirmed.
- Click Create task now to save and activate.
Viewing violation alerts
Restricted-zone violations appear in the alert list alongside other alert types — see Working with alerts. The evidence image attached to the alert helps you quickly confirm whether it's a genuine intrusion before acting on it.