Skip to content
Camzify
Use cases

Twenty-one situations, one set of rounds

A use case is a situation a security manager is responsible for, and the checklist, detections and notifications that cover it. Every scenario here runs on the same account and the same cameras. What changes is what the round asks at each stop, which detections watch between rounds, and who is told when a check fails. Each page says what applies, shows the checklist, and says where it stops.

  • Same cameras, same account
  • A checklist per scenario
  • Honest about what it will not do

Looking for an industry instead?

The industry pages start from the site type, warehouses, construction, retail and thirteen more, and pick the use cases that fit it.

Browse industries

Or the detection itself?

Every use case names the detections it uses. Each has its own page: what it fires on, how it is tuned per camera, and what it does not detect.

All 22 detections
FAQ

Frequently asked questions

A feature is a capability, such as line intrusion detection. A use case is a situation a security manager is responsible for, such as a perimeter after dark, and the combination of detections, patrol checklist and notifications that covers it. Each use-case page names the detections that apply, shows the checklist a round would run, and says what the platform will not do in that situation.

No. Every use case on this page runs on the same account: the same cameras, the same 22 detections licensed per camera, and the same virtual patrolling. What changes between them is configuration: which detections are enabled on which cameras, what the checklist at each stop asks, and who is notified when a check fails.

The one with the clearest failure condition. After-hours monitoring and perimeter security are the usual starting points because the checklist writes itself: doors closed, zones empty, fence line clear. A round that passes is a round nobody thinks about, and a round that fails produces a snapshot and a guard message. Once that is working, the other scenarios are a matter of adding cameras and checklist items.

Yes, and most do. A warehouse runs perimeter security on the fence cameras, loading dock monitoring on the bays, and after-hours rounds across the interior, all as patrol sequences on the same account. Each sequence has its own schedule, checklist and guard roster.

They are examples of what a round for that scenario checks, written the way a checklist item is written in the console. The items on your own rounds are yours to define per camera. The states shown, Compliant, Not Compliant and Pending, are the three a checklist item can hold.

Ready to patrol your site 24/7?

Book a 15-minute demo and see a live patrol run on your own cameras.

This site is being updated

We are rebuilding pages as you read this, so an image, a link or a section may look unfinished for a while. The product itself is unaffected. If something important is broken, tell us at the contact page and we will fix it.