.. _getting-started: First Steps after Deployment ======================================================== Once you have successfully deployed FindFace Security, it is time to open the :ref:`web interface ` and get started. In this chapter, you can find a recommended sequence of steps that will help you harness your system's complete functionality. .. rubric:: In this chapter: .. contents:: :local: Organize Cameras ---------------------------------- #. :ref:`Create a new camera group ` or use the default one. A camera group is an entity that allows you to group cameras subject to their physical location. For example, cameras at the same entrance to a building can be combined into one camera group. #. :ref:`Add cameras ` to the camera group and :ref:`check their statuses `. .. rubric:: You may also need: #. Configure your system to process video from the group of cameras at their physical location. It may come in handy in a distributed architecture. :ref:`Learn more `. #. Consider enabling event deduplication if observation scenes of cameras within the group overlap. This feature allows you to exclude coinciding facial recognition events among cameras belonging to the same group. :ref:`Learn more `. Organize Watch Lists and Dossiers ---------------------------------------- #. :ref:`Create a new watch list ` or use the default one. A watch list is an entity that allows you to classify people by arbitrary criteria: blacklist, wanted, VIP, staff, etc. #. Upload dossiers and add them in the watch list either :ref:`manually `, :ref:`in bulk via the web interface `, or use the :ref:`console bulk upload ` function. .. rubric:: You may also need: #. :ref:`Distribute dossier database ` among several hosts. The dossier database will be available for editing on the ``master`` server and reading and monitoring on the ``slaves``. #. :ref:`Customize dossier content `. Create additional fields, tabs, and search filters. Create Users and Grant them Privileges ----------------------------------------- #. Check out the list of :ref:`predefined user roles ` and :ref:`create new roles ` if necessary. #. :ref:`Add users ` to the system and grant them privileges. Start Monitoring Faces ----------------------------------- By default, FindFace Security is monitoring only :ref:`unmatched faces `. To enable a custom watch list monitoring, simply make this list :ref:`active `. You can also turn on sound notifications and request manual acknowledgment for the events associated with the list. .. rubric:: You may also need: #. Make events more informative by enabling recognition of gender, age, emotions, beard, face mask, and glasses. :ref:`Learn more `. #. Protect your system from spoofing by enabling the Face Liveness Detection functionality. :ref:`Learn more `. Organize Video Surveillance ------------------------------- :ref:`Create a camera layout ` for essential video surveillance. Start Counting Faces and Silhouettes ------------------------------------- Set up :ref:`counters ` to count faces and silhouettes on connected cameras. This functionality can apply to a wide range of situations, such as people counting in queues and waiting areas, monitoring public gatherings, crowding prevention, and more. FindFace Security in Action --------------------------------------------- #. :ref:`Automatically identify faces in live video ` and check them against watch lists. Work with the event history by using various filters. #. Harness the :ref:`episodes `. An episode is a set of identification events that feature faces of the same person, detected within a certain period. As events on the :guilabel:`Events` tab show up in an arbitrary order, a large number of miscellaneous events can make the work challenging and unproductive. With the Episodes, the system uses AI to organize incoming events based on the faces similarity and detection time. This allows for the effortless processing of diverse events, even in large numbers. #. Search for faces in the following databases: * Database of detected faces. :ref:`Learn more `. * Dossier database. :ref:`Learn more `. #. :ref:`Search archived videos ` for faces under monitoring. #. Manually :ref:`compare two faces ` and verify that they belong to the same person. #. Use the :ref:`mobile app `. .. rubric:: You may also need: #. Harness the :ref:`person recognition `. The system databases will hold a new entity ``person event`` linked to all :ref:`episodes ` that feature a person's face. You can work with the person gallery similarly as with events and episodes. #. View analytics on the number of visitors, their gender, average age, most frequently visited zones, and the character of visits (first-timers or returners). :ref:`Learn more `. Basic Maintenance -------------------------- #. :ref:`Configure ` automatic cleanup of events, episodes, and full frames. #. Manually :ref:`purge ` events, episodes, and full frames. #. Regularly :ref:`backup ` the database. Go Further -------------------- #. Set up :ref:`webhooks ` to automatically send notifications about specific events, episodes, and counter records to a given URL. In this case, when such an event occurs, FindFace Security will send an HTTP request to the URL configured for the webhook. You can use webhooks for various purposes, for example, to notify a user about a particular event, invoke required behavior on a target website, and solve security tasks such as automated access control. :ref:`Learn more `. #. Harness the FindFace Security functions through :ref:`HTTP API `. #. Check out the list of our :ref:`partner integrations `. #. Harness :ref:`plugins ` to set your directives that determine how FindFace Security processes detected faces. .. seealso:: * :ref:`cameras` * :ref:`guests` * :ref:`users` * :ref:`offline-video` * :ref:`counters` * :ref:`advanced` * :ref:`troubleshooting`