Advanced Configuration

Beyond the basics, configuration splits along the architecture: corridor-layer settings (Hub, CIGS, CBS) live in the deployment's environment files, while biometric-engine settings belong to VPP and are managed through its own configuration and admin interface. Knowing which layer owns a setting is half the work — if it concerns detection, matching, or streams, it is VPP's; if it concerns units, events, or retention, it is the corridor's.

Retention tuning

With storage enabled, retention is enforced per data type by a scheduled job:

STORAGE_ENABLED=true
RETENTION_TTL_EVENTS_HOURS=48
RETENTION_TTL_IMAGES_HOURS=24
RETENTION_JOB_INTERVAL_MINUTES=30

Event records and image data (face crops, full frames) expire independently — a common production pattern keeps events for audit slightly longer than images. Size the PostgreSQL volume for your TTLs and traffic, not the defaults.

Zone behavior

CBS raises occupancy violations against configurable per-zone person limits, and derives entry/exit and count events per unit. Tune the limits to the physical corridor — a threshold that suits a wide hall floods a narrow passage with violations. When MCT is introduced, these signals switch source transparently; topics and payloads do not change.

VPP-side configuration

Detection sensitivity, matching thresholds, liveness, stream parameters, and camera management all belong to VPP and are documented in the VPP platform configuration guides — Smart Corridors uses VPP unchanged, so those guides apply directly. For which thresholds matter operationally and how to approach tuning them, see Tuning Identification.