Events and investigation
Events groups detections into visits. Filter by camera, object type, time, recognition state, and whether the sighting was marked wrong, then open a visit for its picture and available footage. The play icon on an event card opens the visit and starts its clip as soon as the footage is ready. The arrow keys move between cards, Enter opens one and Esc closes the review. Load more pages older events in; the page shows one window of cards at a time, with Show newer and Show older to move through what is loaded, and stops at 1,200 events, after which a narrower time range or camera is the way to see more. Detection is an aid to review: an empty event list does not prove nothing happened. Use Playback to inspect the recording directly.
Correct a detection or teach a known object
Use the event's correction and identity controls to record what the sighting actually shows. Marking an event wrong says the detector saw nothing real — a shadow, a reflection, a moving branch — which is a different claim from unrecognized, meaning a real person the recorder does not know. The event and its footage are untouched, and a second tap takes the mark back. Filter on those marks to judge whether a camera needs its floors or zone adjusted.
Known objects manages named people, vehicles, and pets and the sightings used to teach them. An administrator can withdraw an incorrect example without deleting the entire identity.
Where face and plate recognition is on, the event panel also shows what the face or plate reading found, and the Plate box in the filters finds every visit with all or part of a plate.
Recognition uses appearance evidence and can be unsure. A suggested identity or cross-camera match needs human review; it is not proof of a person's identity. See detection settings for confidence and recognition floors.
Find and trace visits
In Investigation, search for a description and narrow by time and camera. When the local semantic assets are installed, appearance search runs on the recorder. Otherwise, search falls back to labels and colors and reports that state.
Choose Trace movement on a result or event to review a trail. A sighting joins the trail when its object image resembles the subject's at or above the matching floor (Strict, Normal or Loose), or when it was seen on another camera within a minute of a sighting already on the trail and its image is not far under the floor, or was never indexed. The second rule is what follows a car from the garage to the drive to the street when each camera sees a different side of it; it never links two sightings on the same camera, so a second car in the same drive stays separate. Under Strict, appearance alone decides, and timing fills in only for an image that was never indexed. Each sighting says how it joined: Likely or Possible with how alike it looks, Possible · by timing with the likeness when its image was scored, or by timing only when it was not. Rejecting a sighting with Not the same person (or car) also drops any that joined only through it. Adjust the time window and strictness, inspect candidate sightings, and add or reject them. Save the trail with a title and notes when it is useful.
When the site has a plan and the trail's cameras are on it, On the plan above the timeline draws the trail: each sighting numbered at its camera, a line through them in order, and the sightings that joined only as Possible in a lighter color. Markers are where the cameras are, not where the subject stood, and the panel says how many sightings are on cameras that are off the plan.
Search ranks at most the newest 2,000 filtered events and returns up to 100 matches. If the result is truncated, narrow the filters. Background appearance indexing runs in small batches between recording work and can lag behind a busy scene. When the AI agent searches pictures on your behalf it is told when a result was truncated, and it uses the label and color index instead when the appearance model is not installed.
The Known objects list shows a person the identities seen on cameras they may access; administrators see every identity.
Appearance search, trails, and new incidents and notes are a licensed feature. Where the recorder's license does not include investigation, search uses labels and colors, and incidents already saved can still be read and exported.
Preserve an investigation
Saved investigations collect sightings, notes, and footage ranges. Review the camera and time for every range you retain. Export controls require footage export permission; a PDF report collects the incident's records and observations, with a page of the site plan when the incident's cameras are on one: every camera on that plan with its wedge, the incident's cameras numbered in the order their footage starts and joined by a line, and a legend naming any of the incident's cameras that are not on the plan. A plan image over 4 MB is left out and the report says so.
Incident holds are exempt from normal retention. They can fill storage and stop new recording. Review retained incidents and release holds when they are no longer needed.
An action rule with a Preserve footage action opens preserved investigations of its own, titled with the rule's name, the camera, and the time, with no creator. Runs close together on the same camera extend the hold rather than opening another, and a later run adds a range to the same investigation while it is under a day old and has room; after that a new one opens. These appear in the list like any other and are released the same way, with Release preservation. The evidence log records Footage preserved when a rule opens a hold and Footage hold extended by a rule when it widens one. See action rules.
An evidence archive includes whole segments and can contain context outside the selected interval. Archives are limited to one at a time site-wide, 512 MiB of source media, 1,024 segments, and ten minutes per response.
The optional Ask the AI agent feature is configured separately. Read AI security agent before enabling it or sharing pictures.