CLIENTS ======================== NCheck Bio Attendance Client is used as a client application for NCheck Bio Attendance server. It is mainly used to record attendance. It also can be used as a standalone attendance device. NCheck Bio Attendance client has two applications #. NCheck Bio Attendance Lite client NCheck Bio Attendance Lite client is a simple client application with minimal required functionality for Windows, Android and IOS. #. NCheck Bio Attendance Standard client NCheck Bio Attendance Standard client for Windows and Android includes client-side biometric extraction and matching which provides advanced functions like automatic face recognition, face capturing and offline operation. The Standard client requires a NCheck Bio Attendance license #. NCheck Bio Attendance Surveillance client for Windows NCheck Bio Attendance Surveillance client for Windows support all the features in NCheck Bio Attendance Standard client for Windows with guard functionality in which an authorized person can manually identify the person and record the event in the attendance system #. NCheck Bio Attendance Guard client for Android NCheck Bio Attendance Guard for Android application provide functionality which an authorized person can manually identify person and record event in the attendance system. System requirement ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ .. list-table:: System requirements for clients applications :widths: 1206 2735 2414 2414 * - - Lite - Standard - Surveillance/Guard * - Windows - #. Microsoft Windows 8 or higher operating system #. 1GB of disk space #. 2GB of RAM #. Supported :ref:`Face` peripheral - #. Microsoft Windows 8 or higher operating system #. 1GB of disk space #. 4GB of RAM #. One supported peripheral as mentioned in the in Peripherals section - #. Microsoft Windows 8 or higher operating system #. 1GB of disk space #. 8GB of RAM #. Supported :ref:`Face` peripheral * - Android - #. Android phone or tablet running Android 4.4 OS or later version #. 1 GB Of RAM #. Integrated camera - #. Android phone or tablet running Android 4.4 OS or later version #. 2 GB of RAM #. USB OTG (USB On the Go) feature if using peripherals as mentioned in the in Peripherals section - #. Android phone or tablet running Android 4.4 OS or later version #. Integrated camera * - IOS Client - Apple device running IOS 10.2 OS or later - Not available - Not available Peripherals ------------------------------ NCheck Bio Attendance client applications supports following peripherals. #. :ref:`Face` #. :ref:`Fingerprint` #. :ref:`Iris` #. :ref:`Other` .. note:: NCheck Bio Attendance installer for Windows is installing all necessary drivers in order to enable face, fingerprint and iris scanners. But in case if you need additional drivers, you may need to install compatible drivers in the computer. You can download drivers for supportable camera, fingerprint and iris scanners from `scanner driver package `_`. `_ .. _Ref34215697: Face +++++++++++++++++++++++++++++++++++++++++++ NCheck Bio Attendance Android and IOS clients are using cameras available with the device. NCheck Bio Attendance Windows clients support following camera types. #. USB cameras #. IP cameras USB cameras """""""""""""""""""" In general, USB cameras working in Windows OS are supported. IP cameras """"""""""""""""""" Refer `Neurotechnology guide for supported cameras `_ section for all supported IP cameras. Refer :ref:`Preferences` section for add IP cameras for NCheck Bio Attendance Standard for Windows. .. _Ref32910914: Fingerprint ++++++++++++++++++++++++++++++++++++++++++++++++++ NCheck Bio Attendance clients support external or internal USB fingerprint scanners. Refer `Neurotechnology guide for supported fingerprint scanners and sensors `_ for Windows standard client. .. _Ref32910921: Iris +++++++++++++++++++++++++++++++++++++++++++ NCheck Bio Attendance clients support external or internal USB iris scanners. Refer `Neurotechnology guide for supported iris scanners `_ for Windows standard client`. `_ .. note:: By default, iris scanners are disabled for Windows standard client. To enable, unzip necessary iris scanners from the IrisScanners folder in NCheck Bio Attendance installation folder (By default the installation folder is “C:\Program Files\Neurotechnology\ NCheck Bio Attendance”) .. _Ref32910925: Other ++++++++++++++++++++++++++++++++++++++++++++ NCheck Bio Attendance supports capturing other authentication data. Data capture is performed by using the following hardware. .. list-table:: Hardware requirements for non-biometric identification :widths: 1870 3741 2754 * - - Lite - Standard * - RFID - #. External HID #. External Serial - NFC Support * - Barcode - External HID - Using built-in camera Access control --------------------------------- NCheck Bio Attendance Standard clients are able to trigger external executables with given parameters as mentioned in :ref:`External executables` section. Supporting Locations --------------------------------------- NCheck Bio Attendance uses operating system provided location services to capture the location of attendance events. .. note:: For enabling location service from the operating system, please refer location service configuration for the relevant operating system. .. _Ref32500937: Install Client ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ Download client ---------------------------------- NCheck Bio Attendance clients application download from `download page `_. Install clients for Windows ---------------------------------------------- Windows install includes all components of NCheck Bio Attendance. You need to select the required client (Lite or Standard) to install the client. Refer :ref:`Install client For Windows` section for more details .. figure:: Images/Clients/image665.PNG :width: 444 :figclass: align-center Select components of Windows installation After successful installation you will be asked to activate license in NCheck Bio Attendance Standard clients, Surveillance client for Windows and Guard client for Android as mentioned in :ref:`License Activation` section. For NCheck Bio Attendance Lite client you will be asked to register the device as mentioned in :ref:`Register clients` section. .. _Ref40853628: License Activation ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ NCheck Bio Attendance Client Standard needs to activate licenses. Please refer :ref:`Activation` section for more details. .. note:: NCheck Bio Attendance Lite clients are free and not required to activate licenses. After successful license activation, you will be asked to register the client application as mentioned in :ref:`Register clients` section. .. _Ref37763181: Register clients ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ NCheck Bio Attendance Clients can be used with following modes #. NCheck Bio Attendance Cloud #. NCheck Bio Attendance server installed on-premises #. Standalone (Standard clients and Surveillance client only) Registration process configures the application to work with one of the above three modes. Accessing registration can be done as the following ways #. Application will prompt you the registration dialogue in case it is not registered #. User registration option from the application menu. Registration screen -------------------------------------- Mode of registration +++++++++++++++++++++++++++++++++++++++ #. Server URL #. Search server button Select this option to detect server URL. This option works if the server and client work in same network. #. :ref:`Registration Token` #. Scan barcode button Instead of entering registration token, users can scan barcode in Android client. Cloud mode """"""""""""""""""" .. list-table:: Registration views of cloud mode :widths: 1075 1080 6930 * - - Version - Cloud mode * - Windows - Lite - .. figure:: Images/Clients/image667.PNG :width: 452 :figclass: align-center Windows lite client registration view on cloud mode * - - Standard/Surveillance - .. figure:: Images/Clients/image669.PNG :width: 464 :figclass: align-center Windows standard client registration view on cloud mode * - Android - Lite/Guad - .. figure:: Images/Clients/image671.PNG :width: 283 :figclass: align-center Android lite client registration view on cloud mode * - - Standard - .. figure:: Images/Clients/image673.PNG :width: 301 :figclass: align-center Android standard client registration view on cloud mode * - IOS - Lite - .. figure:: Images/Clients/image675.PNG :width: 303 :figclass: align-center IOS lite client registration view on cloud mode On-premises mode """"""""""""""""""""""""" .. list-table:: Registration views of on-premises mode :widths: 985 1260 6840 * - - Version - On-premises mode * - Windows - Lite - .. figure:: Images/Clients/image677.PNG :width: 475 :figclass: align-center Windows lite client registration view on on-premises mode * - - Standard/ Surveillance - .. figure:: Images/Clients/image679.PNG :width: 453 :figclass: align-center Windows standard client registration view on cloud mode * - Android - Lite/Guard - .. figure:: Images/Clients/image681.PNG :width: 262 :figclass: align-center Android lite client registration view on on-premises mode * - - Standard - .. figure:: Images/Clients/image683.PNG :width: 283 :figclass: align-center Android standard client registration view on on-premises mode * - IOS - Lite - .. figure:: Images/Clients/image685.PNG :width: 259 :figclass: align-center IOS lite client registration view on on-premises mode Standalone mode """""""""""""""""""""""" .. list-table:: Registration views of standalone mode :widths: 1165 1080 6840 * - - Version - Standalone mode * - Windows - Standard - .. figure:: Images/Clients/image687.PNG :width: 417 :figclass: align-center Windows standard client registration view on standalone mode * - Android - Standard - .. figure:: Images/Clients/image689.PNG :width: 297 :figclass: align-center Android standard client registration view on standalone mode .. _Ref30753248: Registration Token --------------------------------------------------------- To register the client application with cloud or on-premises server, a registration code is required. Registration code can be generated by an administrator. Depend on the registration code generation, the client application can be registered in the following two modes #. Group Please refer :ref:`User group quick view` section for more details about registering device for group of users. Once the device is registered, the selected group of people can use the attendance terminal to check-in and check-out. #. Personal Please refer :ref:`User quick view` section for more details about registering device for person. Once the device is registered as a personal device, the selected user only can perform check-in and check-out from the terminal. Registration ------------------------------- Select the Connect button to proceed with registration. If the server has signed with the untrusted certificate, you will be asked to accept self-signed certificate as mentioned in :ref:`SSL Certificate validation` section. Successful registration will take you to :ref:`Main view` . Register button will be disabled if the mandatory fields are empty or :ref:`Validation errors` exist. Following error messages could be appeared in the registration screen. .. list-table:: Error messages of device registration :widths: 1255 5040 * - Error code - Error message * - 2051 - Failed to register with the NCheck Bio Attendance server {server URL} * - 2052 - Failed to register with the registration code * - 2053 - The registration token has already been used. Please generate new registration code or contact administrator * - 2054 - Could not discover the NCheck Bio Attendance server URL .. _Ref60396754: SSL Certificate validation ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ To start the NCheck Bio Attendance server, a valid SSL certificate must be added as mentioned in :ref:`Server` section. If any SSL certificate validation error occurred, you will be prompted the validation error as below. .. list-table:: Certificate validation error dialogue :widths: 1885 6745 * - Client - Self-signed certificate prompt * - Windows - .. figure:: Images/Clients/image691.PNG :width: 318 :figclass: align-center Certificate validation error dialog for Windows client * - Android - .. figure:: Images/Clients/image693.PNG :width: 177 :figclass: align-center Certificate validation error dialog for Android client #. Title of the SSL certificate validation error dialogue #. Error message #. Actions .. _Ref32831678: Main view ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ NCheck Bio Attendance client’s main views as follows, #. :ref:`Main view for biometrics capture` #. :ref:`Main view for non-biometrics capture` .. _Ref37693390: Main view for biometrics capture ----------------------------------------------------------------------- .. list-table:: Main view of clients :widths: 1203 1582 5990 * - - Version - Windows * - Windows - Lite - .. figure:: Images/Clients/image696.PNG :width: 20 :figclass: align-center Main view of Windows lite client * - - Standard - .. figure:: Images/Clients/image699.PNG :width: 397 :figclass: align-center Main view of Windows standard client * - - Surveillence - .. figure:: Images/Clients/image701.PNG :width: 314 :figclass: align-center Main view of Windows Surveillance client * - Android - Lite - .. figure:: Images/Clients/image703.PNG :width: 210 :figclass: align-center Main view of Android lite client * - - Standard - .. figure:: Images/Clients/image705.PNG :width: 150 :figclass: align-center Main view of Android standard client * - - Guard - .. figure:: Images/Clients/image707.PNG :width: 220 :figclass: align-center Main view of Android Guard client * - IOS - Lite - .. figure:: Images/Clients/image709.PNG :width: 171 :figclass: align-center Main view of IOS lite client #. Date and time Show the Time and date #. Menu button Refer :ref:`Main menu` section for more details. #. Status bar Refer connection status section for more details. #. :ref:`Attendance view` #. Single/multi face mode button #. Settings collapse button of Android clients #. Language menu of Windows clients Selected luggage will be applied to the application. #. Mask detection indicator Mask detection indicator is showing in the view according to the :ref:`Mask detection` setting and :ref:`Mask detection threshold` can be applied from either web control panel :ref:`Client settings view` or :ref:`Client settings for device` .. _Ref30759374: Main menu ++++++++++++++++++++++++++++++++++++++++++++++++ .. _Ref30757868: .. list-table:: Main menu of clients :widths: 1669 2066 2066 2066 * - Client - Windows - Android - IOS * - Lite - #. :ref:`Register` #. :ref:`Control panel` #. About - #. :ref:`Register` #. :ref:`Control panel` #. :ref:`Preferences` #. About - Not available * - Standard – Cloud/On-premises - #. :ref:`Control panel` #. :ref:`Register` #. :ref:`Preferences` #. :ref:`License manager` #. :ref:`Synchronize` #. :ref:`About` - #. :ref:`Register` #. :ref:`Control panel` #. :ref:`Preferences` #. :ref:`Synchronize` #. :ref:`License manager` #. :ref:`About` - Not available * - Standard - Standalone - #. :ref:`Login` #. Register #. :ref:`Preferences` #. :ref:`License manager` #. :ref:`About` - #. :ref:`Register` #. :ref:`Control panel` #. :ref:`License manager` #. :ref:`Preferences` #. :ref:`About` - Not available * - Surveillance - - Not available - Not available * - Guard - Not available - #. :ref:`Register` #. :ref:`License manager` #. preferences #. :ref:`About` - Not available .. _Ref45084461: Control panel """""""""""""""""""""""""""""""""""""""""" This option allows to access NCheck Bio Attendance control panel from the client as follows. #. NCheck Bio Attendance control panel Control panel allows to access NCheck Bio Attendance control panel if the NCheck Bio Attendance client is registered to the Cloud/On-premises modes. #. NCheck Bio Attendance Client control panel Control panel allows to access NCheck Bio Attendance Client control panel if the NCheck Bio Attendance client is registered to the On-premises server modes or :ref:`Offline operation mode` is enabled in the Cloud/On-premises modes. .. _Ref45084883: Login """""""""""""""""""""""""""""""""" Login to the standalone control panel .. _Ref34821574: Register """"""""""""""""""""""""""""""""""""" Re-register the client application as mentioned in :ref:`Register` section. .. _Ref45084575: Synchronize """""""""""""""""""""""""""""""""""""""" NCheck Bio Attendance Standard clients synchronize server-side data with the devices in the time intervals define in :ref:`Offline data synchronize interval` setting. If instant synchronize required, user can select Synchronize option. .. _Ref45084542: License manager """""""""""""""""""""""""""""""""""""""""""" Show the License activation window as mentioned in :ref:`Activation` section. .. _Ref45084693: About """"""""""""""""""""""""""""""""""" .. list-table:: About views of Clients :widths: 1075 1440 6480 * - - Version - About window * - Windows - Lite - .. figure:: Images/Clients/image711.PNG :width: 406 :figclass: align-center About view of Windows lite client * - - Standard - .. figure:: Images/Clients/image713.PNG :width: 415 :figclass: align-center About view of Windows standard client * - - Surveillance - .. figure:: Images/Clients/image713.PNG :width: 415 :figclass: align-center About view of Surveillance client * - Android - Lite - .. figure:: Images/Clients/image715.PNG :width: 332 :figclass: align-center About view of Android lite client * - - Standard - .. figure:: Images/Clients/image717.PNG :width: 357 :figclass: align-center About view of Android standard client * - - Guard - .. figure:: Images/Clients/image719.PNG :width: 321 :figclass: align-center About view of Guard client * - IOS - Lite - #. Product name #. Copyrights #. Neurotechnology logo #. Application type and version #. NCheck Bio Attendance support email #. NCheck Bio Attendance website #. Open NCheck Bio Attendance log folder #. Generate NCheck Bio Attendance diagnostic info #. Open NCheck Bio Attendance privacy policy #. Close button .. _Ref34829420: Preferences ++++++++++++++++++++++++++++++++++++++++++++++++++ .. list-table:: Preferences of clients :widths: 1236 2150 3108 2522 * - - Windows - Android - IOS * - Lite - Not available - #. :ref:`Capture sound` #. :ref:`Crop face` #. :ref:`Capture quality` #. :ref:`Predefined location` #. :ref:`Checkout notification` #. :ref:`Enable logs` - #. :ref:`Capture sound` #. :ref:`Crop face` #. :ref:`Predefined location` #. :ref:`Checkout notification` * - Standard - #. :ref:`Camera list` - #. Device settings #. :ref:`Capture sound` #. :ref:`Crop face` #. :ref:`Extract on server` #. :ref:`Low CPU support` #. :ref:`Startup application` #. :ref:`External scanner` #. Camera settings #. :ref:`Mirror preview` #. :ref:`Enable app orientation` #. :ref:`Rotation settings` #. Power saving mode #. :ref:`Enable power saving mode` #. Security #. :ref:`Encrypt the database` #. Debug mode #. :ref:`Enable logs` #. :ref:`Diagnostic report` - Not available * - Surveillance - #. :ref:`Camera list` #. :ref:`Surveillance engine properties` - Not available - Not available * - Guard - Not available - #. :ref:`Capture sound` #. :ref:`Crop face` #. Enable auto capture #. :ref:`Capture quality` #. :ref:`Enable logs` - Not available .. _Ref30763763: Capture sound """""""""""""""""""""""""""""""""""""""""" Enable to play the capturing sound when the image is capturing. .. _Ref30763774: Crop face """""""""""""""""""""""""""""""""""""" Enable to crop face to increase the matching accuracy. .. _Ref76050277: Predefined location """""""""""""""""""""""""""""""""""""""""""""""" This allows to set a default location for Android and IOS Lite clients. This predefined location will be used for the recording event according to the selected option in :ref:`Allow predefined location` client setting in the server. The predefined location dialog as follows. .. figure:: Images/Clients/image721.PNG :width: 198 :figclass: align-center Predefined location dialog in IOS Lite client .. figure:: Images/Clients/image723.PNG :width: 239 :figclass: align-center Predefined location dialog in Android Lite client #. Latitude Latitude coordinate of the location #. Longitude Longitude coordinate of the location #. Address #. Clear button Remove all location parameters. #. Ok button Save location coordinates #. Cancel button .. _Ref76050282: Checkout notification """""""""""""""""""""""""""""""""""""""""""""""""" Check-out notifications are used to aware user to check-out before the check-out time. Checkout notifications are available in Android and IOS Lite clients registered as a personal device .. _Ref30763884: Extract on server """""""""""""""""""""""""""""""""""""""""""""" Face details should be extracted to identify the faces in the captured image. Enable this setting to minimize the extraction delay on low performance devices. .. _Ref30763888: Low CPU support """""""""""""""""""""""""""""""""""""""""""" This setting has introduced for low CPU devices to lower the CPU usage when application in use. Enable this setting to preview captured face instead of showing the face rectangle (as mentioned in Face capture view section) with lower resolution preview. .. _Ref37693682: Startup application """""""""""""""""""""""""""""""""""""""""""""""" Enable this setting to start application on restart the device. .. _Ref30763899: External scanner """"""""""""""""""""""""""""""""""""""""""""" NCheck Bio Attendance Standard can be used with external scanners in order to record attendances with extended user experiences. Currently NCheck Bio Attendance Standard supports below type of devices/scanners .. figure:: Images/Clients/image725.PNG :width: 256 :figclass: align-center External scanners view of Android standard client #. TPS980 TPS980 is an Android Biometric Face recognition Terminal with infrared sensor and face recognition camera and fingerprint scanner. NCheck Bio Attendance Standard client can be installed to use with available sensors. #. HF-7000 HF-7000 from HFSecurity is a fingerprint reader based on capacitive fingerprint sensor. The fingerprint scanner uses USB for communications with host PC or device. Refer `this link `_ for more information. To configure the NCheck Bio Attendance Standard #. Select External scanner from the scanner list #. Select configure button to configure the selected scanner. #. Select the feedback type from the list #. All events Select this option to apply scanner configuration across all scanners. #. External scanner events Select this option to apply scanner configuration to external scanner events. 3. Select the Configure button to customize the selected scanner configuration above. .. figure:: Images/Clients/image727.PNG :width: 199 :figclass: align-center TPS scanner configuration view .. _Ref37693728: Mirror preview """"""""""""""""""""""""""""""""""""""""""" Enable this to fix the mirror effect of the camera preview. .. _Ref30763981: Enable app orientation """"""""""""""""""""""""""""""""""""""""""""""""""" Enable this to fix the application ore as 0, 90, 180, 270 degrees. .. note:: This setting may not be compatible with the devices, designed for a fix orientation Accelerometer and gyroscope sensors are not available .. _Ref30763986: Rotation settings """""""""""""""""""""""""""""""""""""""""""""" Custom rotation settings need to be configured in case of camera orientation and device rotation settings return from the Android API are not same as standard Android devices. This applicable for the devices, #. Designed for a specific orientation #. Accelerometer and gyroscope sensors are not available Camera orientation and device rotation can be set as follows, Camera orientation for a normal android device can be identified as follows. .. list-table:: Camera orientation :widths: 2659 5318 * - Camera - Orientation * - Front camera - 270 degrees * - Back camera - 90 degrees When the camera orientation has differences as mentioned above, this value can be set manually using these settings. Device rotation for a normal device can be identified as follows, .. list-table:: Custom device rotation :widths: 2411 1994 * - Device orientation - Device rotation * - .. figure:: Images/Clients/image729.PNG :width: 59 :figclass: align-center - 0 * - .. figure:: Images/Clients/image730.PNG :width: 96 :figclass: align-center - 1 * - .. figure:: Images/Clients/image731.PNG :width: 54 :figclass: align-center - 2 * - .. figure:: Images/Clients/image732.PNG :width: 94 :figclass: align-center - 3 User can set matching value for device rotation in special devices depending on the device orientation as above table. .. _Ref30763991: Enable power saving mode """"""""""""""""""""""""""""""""""""""""""""""""""""" Reduce the CPU usage when application is idle. Power saving mode timeout """""""""""""""""""""""""""""""""" The timeout can be select to set the device idle when no attendance recording. Available timeouts are #. 10 minutes #. 20 minutes #. 30 minutes #. 1 hour .. _Ref37693782: Encrypt the database """"""""""""""""""""""""""""""""""""""""""""""""" Encrypt the database of NCheck Bio Attendance Standard client by giving a password. .. _Ref30763804: Enable logs """""""""""""""""""""""""""""""""""""""" Log all events to a file for debugging. .. _Ref30764007: Diagnostic report """""""""""""""""""""""""""""""""""""""""""""" Generate Diagnostic report and send to developers for debugging. .. _Ref30763809: Capture quality """""""""""""""""""""""""""""""""""""""""""" Select face capture quality to reduce the time when recording events #. Low #. Medium #. High #. very high .. _Ref37693895: Camera list """""""""""""""""""""""""""""""""""""""" This option allows to configure IP cameras with NCheck Bio Attendance Windows Standard client application. .. figure:: Images/Clients/image733.PNG :width: 440 :figclass: align-center Camera list preference of Windows standard client #. Camera list table Camera list view as shown in :numref:`Ref34824594` . .. _Ref34824594: .. figure:: Images/Clients/image735.PNG :width: 353 :figclass: align-center Camera list view of camera list preference #. Name #. URL IP address of the camera #. Key #. Add button Add new camera. #. Remove button Remove selected camera. #. Apply button Update all camera in the camera list #. Cancel button .. _Ref40781342: Surveillance engine properties """"""""""""""""""""""""""""""""""""""""""""""""""""""""""" .. figure:: Images/Clients/image737.PNG :width: 5 :figclass: align-center .. figure:: Images/Clients/image738.PNG :width: 420 :figclass: align-center Surveillance engine properties of Surveillance client #. Use NVDIA GPU Enable/disable running surveillance engine on GPU #. Determine Age This enable/disable showing the age on top of the face rectangle in the attendance view. #. Determine gender This enable/disable showing the gender on top of the face rectangle in the attendance view. #. Determine Glasses This enable/disable showing the availability of glasses (whether the user is wearing spectacles) on top of the face rectangle in the attendance view. #. Apply button #. Cancel button Enable auto capture """""""""""""""""""""""""""" The capture mode of the Guard client can be changed as following. #. Manual capture The fault capture mode of the Guard client. When this mode has enabled, the Guard must capture the face manually pressing the capture button. To enable this mode, disable enable auto capture mode setting from the preference menu. #. Auto capture To enable this feature, enable “Enable auto capture mode” from the Preference menu. When the auto capture mode has enabled, the Guard client will be automatically detect the face and then extract once faced to the camera. .. _Ref35351493: Connection status +++++++++++++++++++++++++++++++++++++++++++++++++++++++++ .. list-table:: Connection status view of clients :widths: 977 1196 6843 * - - - Connection status view * - Windows - Lite - .. figure:: Images/Clients/image740.PNG :width: 474 :figclass: align-center Status bar view of Windows lite client * - - Standard/ Surveillance - .. figure:: Images/Clients/image742.PNG :width: 487 :figclass: align-center Status bar view of Windows standard client * - Android - Lite - .. figure:: Images/Clients/image744.PNG :width: 314 :figclass: align-center Registration details of Android Lite client * - - Standard - .. figure:: Images/Clients/image746.PNG :width: 354 :figclass: align-center Registration details of the Android standard client * - - Guard - .. figure:: Images/Clients/image748.PNG :width: 242 :figclass: align-center tus bar of Guard client #. Network availability #. License status indicator Shows the current license obtaining status as licensed, trial or expired. #. Server and port URL and port of the connected server in cloud, on-premises or standalone mode #. Registered user/user group name Registered user/user group name is showing in cloud or on-premises mode. In standalone mode, “All users” will be shown. #. Organization name in the cloud or on-premises mode #. Connectivity status with the server indicator in cloud and on-premises mode as shown in below. .. list-table:: Online/Offline statuses of Standard clients :widths: 1139 1814 1919 2384 * - Status - Description - Android standard client - Windows standard client * - Online - Connected with the server - .. figure:: Images/Clients/image750.PNG :width: 39 :figclass: align-center - .. figure:: Images/Clients/image751.PNG :width: 74 :figclass: align-center * - Offline - Cannot connected with the server - .. figure:: Images/Clients/image752.PNG :width: 49 :figclass: align-center - .. figure:: Images/Clients/image753.PNG :width: 73 :figclass: align-center #. Synchronizing progress of the standard clients if the :ref:`Offline operation mode` is enabled. #. Email address if the Lite client registered to the user and :ref:`Allow without biometrics` setting has enabled. #. Server indicator for cloud, on-premises, and standalone mode. .. list-table:: Server indicators for Clients :widths: 2070 1980 * - Mode - Indicator * - Cloud - .. figure:: Images/Clients/image754.PNG :width: 38 :figclass: align-center * - On-premises - .. figure:: Images/Clients/image755.PNG :width: 27 :figclass: align-center * - Standalone - .. figure:: Images/Clients/image756.PNG :width: 30 :figclass: align-center #. Location restriction status Location restriction status indicates how far from the location coordinates where the location restriction applied as mentioned in :ref:`Location restrictions` section. Android Lite client uses Google location services to find the device location. Location restriction status indicated following details. .. list-table:: :widths: 3150 5151 * - Status - View * - Location is restricted. But user is inside the permitted radius - .. _Ref41912867: .. figure:: Images/Clients/image757.PNG :width: 288 :figclass: align-center User inside the permitted area * - Location is restricted. User is not inside the permitted radius. - .. figure:: Images/Clients/image759.PNG :width: 280 :figclass: align-center User is not inside the permitted area * - Location services are not available. Location services of the device has disabled or not available in the area. - .. figure:: Images/Clients/image761.PNG :width: 238 :figclass: align-center Location coordinates are not available * - Location has not restricted. - .. figure:: Images/Clients/image763.PNG :width: 180 :figclass: align-center Location has not restricted #. Location restriction indicator Indicator will be turned to red if the user is not inside the permitted radius from the location coordinates where the location restriction applied. Otherwise it will be shown in green color. #. Distance Distance from location coordinates where the location restriction has been applied. #. Location accuracy This parameter indicates the accuracy of the distance. As shown in :numref:`Ref41912867` , the correct location can be anywhere between 11+ 14 meters and 11 - 14 meters. The distance and location accuracy may not be accurate depending on the Google location service availability. Please refer this `Google maps help `_ for more details. .. _Ref37693445: Main view for non-biometrics capture --------------------------------------------------------------------------- .. note:: This feature is currently available with NCheck Bio Attendance Lite for Android only. In NCheck Bio Attendance Lite for Android, users are allowed to record the events without presenting face biometrics. In order to enable this feature, Users must enabled the Allow without biometrics setting as mentioned in NCheck Bio Attendance control panel :ref:`Client settings view` or :ref:`Device settings` sections. The view is changing according to the enable/disable status of the :ref:`Manual capture start` setting in the NCheck Bio Attendance :ref:`Client settings view` or :ref:`Block/unblock device/API` as shown in :numref:`Ref32837720` . When the :ref:`Manual capture start` is enabled, user can select the event as check-in or check-out before record. .. _Ref32837720: .. list-table:: Main views for non-biometric capture :widths: 1885 1875 5256 * - :ref:`Manual capture start` is disabled - Android Lite - .. figure:: Images/Clients/image765.PNG :width: 206 :figclass: align-center Capture without biometric view of Android lite client * - - IOS Lite - .. figure:: Images/Clients/image767.PNG :width: 254 :figclass: align-center Capture without biometric view for IOS Lite client * - :ref:`Manual capture start` is enabled - Android Lite - .. figure:: Images/Clients/image769.PNG :width: 275 :figclass: align-center Capture without biometric view of Android lite client when manual capture start setting is enabled * - - IOS Lite - .. figure:: Images/Clients/image771.PNG :width: 263 :figclass: align-center Capture without biometric view of IOS Lite #. Time #. Check-in/check-out icons #. :ref:`Connection status` #. User thumbnail #. Record event button Record the events #. Check-in button Record the check-in events #. Check-out button Record the check-out events .. _Ref32838404: Attendance view ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ Attendance view shows attendance view screen. Attendance view Screen has the following components. #. :ref:`Capture view` #. :ref:`Manual event selection view` #. :ref:`Record event view` #. :ref:`Result view` #. :ref:`Recent events list` Following error could be occurred during capture. .. list-table:: Error messages of record attendances :widths: 1435 6496 * - Error code - Error message * - 2002 - License cannot be obtained * - 2055 - Device has not registered. Please register the device first. * - 2056 - The location is restricted. You are not allowed record attendance from this location * - 2042 - Could not record events. The user has been blocked * - 2037 - Could not record events. The device has been blocked * - 2043 - Could not record event. Check-in time has restricted * - 2044 - Could not record event. Check-out time has restricted * - 2057 - You have already checked-in/checked-out. Please try again in {number of seconds} seconds. * - 2058 - Attendances time has restricted. Please contact administrator for more details. * - 2059 - No match found. Please make sure that face/fingerprint/iris templates have been enrolled before record attendance. * - 2060 - Failed to identify the face/fingerprint/iris. Please try again. * - 2064 - Could not record attendances. Invalid user id input. * - 2065 - Could not record attendances. Peripherals are not ready. Please try again. * - 2067 - User not allowed to Check-in while on Restricted Leave! .. _Ref37694158: Capture view --------------------------------------------------- The default capture view of the NCheck Bio Attendance Standard and Lite clients. Capture view can have a one or more capture device views. Those are #. :ref:`Face capture view` #. :ref:`User ID input` #. :ref:`Fingerprint Capture view` #. :ref:`Iris Capture view` Capture view supportability in Lite and Standard can be identified as follows. .. list-table:: Capture view supportability in clients :widths: 2045 1585 2038 1674 1674 * - - Lite - Standard - Surveillance - Guard * - Face capture - .. figure:: Images/Clients/image54.PNG :width: 14 :figclass: align-center - .. figure:: Images/Clients/image54.PNG :width: 14 :figclass: align-center - .. figure:: Images/Clients/image54.PNG :width: 14 :figclass: align-center - .. figure:: Images/Clients/image54.PNG :width: 14 :figclass: align-center * - User id input - .. figure:: Images/Clients/image55.PNG :width: 17 :figclass: align-center - .. figure:: Images/Clients/image54.PNG :width: 14 :figclass: align-center - .. figure:: Images/Clients/image55.PNG :width: 17 :figclass: align-center - .. figure:: Images/Clients/image55.PNG :width: 17 :figclass: align-center * - Fingerprint capture view - .. figure:: Images/Clients/image54.PNG :width: 14 :figclass: align-center - .. figure:: Images/Clients/image54.PNG :width: 14 :figclass: align-center - .. figure:: Images/Clients/image55.PNG :width: 17 :figclass: align-center - .. figure:: Images/Clients/image55.PNG :width: 17 :figclass: align-center * - Iris capture view - .. figure:: Images/Clients/image55.PNG :width: 17 :figclass: align-center - .. figure:: Images/Clients/image54.PNG :width: 14 :figclass: align-center - .. figure:: Images/Clients/image55.PNG :width: 17 :figclass: align-center - .. figure:: Images/Clients/image55.PNG :width: 17 :figclass: align-center * - RFID capture view - .. figure:: Images/Clients/image55.PNG :width: 17 :figclass: align-center - .. figure:: Images/Clients/image54.PNG :width: 14 :figclass: align-center - .. figure:: Images/Clients/image55.PNG :width: 17 :figclass: align-center - .. figure:: Images/Clients/image55.PNG :width: 17 :figclass: align-center * - Barcodecapture view - .. figure:: Images/Clients/image55.PNG :width: 17 :figclass: align-center - .. figure:: Images/Clients/image54.PNG :width: 14 :figclass: align-center - .. figure:: Images/Clients/image55.PNG :width: 17 :figclass: align-center - .. figure:: Images/Clients/image55.PNG :width: 17 :figclass: align-center .. list-table:: Capture views of clients :widths: 930 1315 6660 * - - Version - Lite * - Windows - Lite - .. figure:: Images/Clients/image773.PNG :width: 315 :figclass: align-center Capture view of Windows lite client * - - Standard - .. figure:: Images/Clients/image775.PNG :width: 342 :figclass: align-center Capture view of Windows standard client * - - Surveillance - .. figure:: Images/Clients/image777.PNG :width: 295 :figclass: align-center Capture view of Surveillance client * - Android - Lite - .. figure:: Images/Clients/image779.PNG :width: 341 :figclass: align-center Capture views of Android Lite client * - - Standard - .. figure:: Images/Clients/image781.PNG :width: 164 :figclass: align-center Capture view of Android lite client * - - Guard - .. figure:: Images/Clients/image783.PNG :width: 161 :figclass: align-center Capture view of Guard client * - IOS - Lite - .. figure:: Images/Clients/image785.PNG :width: 480 :figclass: align-center Capture view of IOS Lite client #. :ref:`Face capture view` #. :ref:`Fingerprint Capture view` #. :ref:`Iris Capture view` #. :ref:`User ID input` #. Face ID view .. _Ref32846581: .. _title_face_capture_view: Face capture view ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ .. list-table:: : Face capture views of clients :widths: 1146 1199 6740 * - - Version - * - Windows - Lite - .. figure:: Images/Clients/image787.PNG :width: 289 :figclass: align-center Face capture view of Window lite client * - - Standard - .. figure:: Images/Clients/image789.PNG :width: 264 :figclass: align-center Face capture view of Window standard client * - - Surveillence - .. figure:: Images/Clients/image792.PNG :width: 18 :figclass: align-center * - Android - Lite - .. figure:: Images/Clients/image795.PNG :width: 200 :figclass: align-center Face capture view of Android lite client * - - Standard – :ref:`Low CPU support` is disabled. - .. figure:: Images/Clients/image797.PNG :width: 226 :figclass: align-center Face capture view of Android standard client * - - Standard – :ref:`Low CPU support` is enabled - .. figure:: Images/Clients/image799.PNG :width: 227 :figclass: align-center Face capture view when Low cpu mode enabled in Standard client * - - Guard - .. figure:: Images/Clients/image801.PNG :width: 243 :figclass: align-center Face capture view of Guard client * - IOS - Lite - .. figure:: Images/Clients/image803.PNG :width: 332 :figclass: align-center Face capture views of IOS lite client #. Image preview #. Camera name #. Face rectangle #. Face liveness guidance Face liveness guidance in Standard clients if the Liveness setting has enabled. #. Capture button In Android Guard client, capture button will appear if Manual capture mode is turned on. Refer :ref:`Capturing faces` section for more details. #. Instruction for face capture #. Liveness Instruction #. Settings of the face capture view #. Resolution #. Flashlight #. Switch camera #. Multi face button Available in Lite clients. Refer Single/multi face mode face capturing for more details #. Turn on auto capture/manual capture modes #. Extracting image of the Android Standard client when :ref:`Low CPU support` has enabled #. Status text Status texts are available in NCheck Bio Attendance Standard client for Android when :ref:`Low CPU support` has enabled and Guard client #. Face ID view of IOS Lite client .. list-table:: Status texts of Android Standard and Guard clients :widths: 2436 2436 2430 * - Description - Standard client - :ref:`Low CPU support` has enabled - Guard client * - Face capturing in progress - Detecting.. - Detecting.. * - Face extraction in progress - Extracting.. - Extracting.. * - Face matching in progress in guard client - - Performing matching.. #. Mask detection indicator Mask detection indicator is showing in the view according to the :ref:`Mask detection` setting and :ref:`Mask detection threshold` can be applied from either web control panel :ref:`Client settings view` or :ref:`Client settings for device` Proceed to :ref:`Capturing faces` section for more detail about capturing face in client applications. .. _Ref40867689: Capturing faces ++++++++++++++++++++++++++++++++++++++++++++++++++++++ #. :ref:`Face capturing in Standard client` #. :ref:`Face capturing in lite client` #. :ref:`Face capturing using Face ID in Lite client` #. :ref:`Multi face mode in Lite client` #. :ref:`Face capturing in Surveillance client of Windows and Guard client of Android` .. _Ref45086000: Face capturing in Standard client """""""""""""""""""""""""""""""""""""""""""""""""""""""""""""" Face capture for attendance recording is performed in the following steps. #. Face capture instruction “Stay facing camera” is shown #. The user faces to the camera #. If the face liveness setting is enabled, users can see the liveness guidance in the screen as mentioned in :ref:`Face liveness mode` section. Otherwise Standard client shows face rectangle and captures face automatically. #. The client performs attendance recording #. The Client will validate the user according the :ref:`Authentication mode` .. note:: To enable face liveness, select face liveness mode from the :ref:`Biometric settings view` of NCheck Bio Attendance control panel. .. _Ref32844891: Face capturing in lite client """""""""""""""""""""""""""""""""""""""""""""""""""""""""" o record attendance in the single face mode, #. Face capture instruction “Stay facing camera” is shown #. The user faces to the camera #. Select Capture button #. The client performs attendance recording #. If no template enrolled for the user, NCheck Bio Attendance lite client registered to a user will be asked to enroll face if the :ref:`Self-enroll templates` is enabled in the server as shown in :numref:`Ref33174247` .. _Ref33174247: .. figure:: Images/Clients/image805.PNG :width: 224 :figclass: align-center Self enrollment in Android lite client #. Enroll button Enroll the captured image as face template. #. If templates exist, in successful event record, the Client will validate the user according the :ref:`Authentication mode` . .. _Ref42846752: Face capturing using Face ID in Lite client """""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""" For NCheck Bio Attendance Lite client for IOS, face ID authentication mode can be enabled from :ref:`Use in-built biometric verification on personal clients` setting.The Client will validate the user according the :ref:`Authentication mode` once the capture the face. .. _Ref40787739: Multi face mode in Lite client """"""""""""""""""""""""""""""""""""""""""""""""""""""""""" Multi face mode can be used to record attendances of the group of users from single capturing. This mode is available on NCheck Bio Attendance Lite clients registered with a user group and switched to the multi face mode. To record attendance in the multi face mode, #. Enable multi face mode in the :ref:`Face capture view` #. Capture the face image of the users the multi-face view will be shown as :numref:`Ref32847882` .. _Ref32847882: .. list-table:: Face captured views of the multi face mode :widths: 1440 7020 * - - Lite * - Windows Client - .. figure:: Images/Clients/image807.PNG :width: 432 :figclass: align-center Multi face captured view of Windows lite client * - Android Client - .. figure:: Images/Clients/image809.PNG :width: 300 :figclass: align-center Multi face captured view of Android lite client * - IOS client - .. figure:: Images/Clients/image811.PNG :width: 256 :figclass: align-center Multi face captured view of IOS lite client #. Unidentified users Unidentified users represent #. Users unable to identify when capturing (Ex: Not enough lighting condition, lower quality of the capturing images) #. Users are not available in the registered user group #. Identified users #. Record enable/disable button Select this button to record attendance of the identified/assigned user. #. Edit button This allows to assign unidentified face for selected user. To enable this settings, :ref:`Manual face selection` setting should enabled from the :ref:`Device settings` or :ref:`Biometric settings view` of NCheck Bio Attendance control panel. The face assign view is shown in :numref:`Ref32848336` . In the face assign view select the user from the list to assign the face. .. _Ref32848336: .. list-table:: Face assign view of the multi face mode :widths: 1325 4986 * - - Lite client * - Windows Client - .. figure:: Images/Clients/image813.PNG :width: 222 :figclass: align-center face assign view of Windows lite client * - Android Client - .. figure:: Images/Clients/image815.PNG :width: 222 :figclass: align-center face assign view of Android lite client * - IOS client - .. figure:: Images/Clients/image817.PNG :width: 222 :figclass: align-center face assign view of IOS lite client #. Capture more button User can capture a new image to re-capture unidentified users. #. Record button The Client will validate the user according the :ref:`Authentication mode` .. _Ref45086626: Face capturing in Surveillance client of Windows and Guard client of Android """"""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""" #. Follow the capturing mode #. Manual capture If the manual capturing is enabled, select the capture button #. Auto capture If the auto capture is enabled, stay facing to the camera until the client capture the image #. The client performs matching with the NCheck Bio Attendance server to select the matching event type as follows #. Surveillance client In Surveillance client, the event will be recorded and updated in the result view. Refer :ref:`Result view for Surveillance client for Windows and Guard client for Android` section for more details. #. Guard client In Guard client, once the face is captured, a record view will be prompted in order to compare the captured face and matching person face. Refer :ref:`Record event view` section for more details. .. _Ref37775362: Fingerprint Capture view +++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ For NCheck Bio Attendance standard clients, :ref:`Capture view` indicates finger print scanner is available. Once the fingerprint available, put the finger on fingerprint scanner to record the attendances. For NCheck Bio Attendance Lite clients for Android and IOS, fingerprint authentication mode can be enabled using :ref:`Use in-built biometric verification on personal clients` setting. .. list-table:: Fingerprint capture view of Android and IOS Lite clients :widths: 1885 7121 * - Android Lite - .. figure:: Images/Clients/image819.PNG :width: 226 :figclass: align-center Fingerprint capture view of Android Lite client * - IOS Lite - .. figure:: Images/Clients/image821.PNG :width: 197 :figclass: align-center Fingerprint capture view of IOS Lite client #. Record Event button The Client will validate the user according the :ref:`Authentication mode` .. _Ref41042757: Fingerprint authentication prompt for Android Lite """"""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""" Fingerprint authentication prompt is shown in :numref:`Ref41038454` .. _Ref41038454: .. figure:: Images/Clients/image823.PNG :width: 195 :figclass: align-center Fingerprint authentication prompt #. Fingerprint authentication prompt Once the fingerprint authentication prompt is appeared, Put the finger on the fingerprint scanner. After successful authentication, The Client will validate the user according the :ref:`Authentication mode` #. Cancel button Cancel the fingerprint authentication prompt. .. _Ref37775531: Iris Capture view ++++++++++++++++++++++++++++++++++++++++++++++++++++++++ .. note:: This view is available on NCheck Bio Attendance Standard clients for Windows only. As shown in :ref:`Capture view` , NCheck Bio Attendance Standard client will indicates if the iris scanner is available. .. figure:: Images/Clients/image825.PNG :width: 674 :figclass: align-center Iris capture view #. Name of the iris scanner #. Left eye #. Right eye .. note:: NCheck Bio Attendance Standard client support single and double side iris scanners. After scan the iris, client will validate the user according the :ref:`Authentication mode` .. _Ref37775343: User ID input ++++++++++++++++++++++++++++++++++++++++++++++++++++ The following inputs are allowing in NCheck Bio Attendance Standard clients to record attendances #. :ref:`Employee code input` ` #. :ref:`RFID Input` #. :ref:`Barcode Input` .. note:: To record attendances, each user must have user Employee code, RFID and Barcode id as mentioned in :ref:`Add/Edit users` section .. _Ref38104170: Employee code input """""""""""""""""""""""""""""""""""""""""""""""" User ID input has the following controls #. ID Field #. Submit button .. list-table:: User ID view of Standard clients :widths: 1744 6612 * - - Standard client * - Windows Client - .. figure:: Images/Clients/image827.PNG :width: 384 :figclass: align-center User ID view of Windows standard client * - Android Client - .. figure:: Images/Clients/image829.PNG :width: 291 :figclass: align-center User ID view of Android client .. _Ref32849065: Once the employee code is given, client will validate the user according the :ref:`Authentication mode` .. _Ref37694470: RFID Input """"""""""""""""""""""""""""""""""""""" User allows to use RFID scanner available with Android devices or external RFID scanners with the devices to scan RFID. Capturing RFID #. Put the RFID card/tab on the RFID scanner/Android device #. The Client will validate the user according the :ref:`Authentication mode` .. _Ref32849070: Barcode Input """""""""""""""""""""""""""""""""""""""""" NCheck Bio Attendance Standard for Android client allows to scan the barcode using front or back camera or external barcode reader with your device. Capturing Barcode #. Scan barcode using the Barcode scanner #. The Client will validate the user according the :ref:`Authentication mode` . .. _Ref48722955: Authentication mode ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ The authentication mode can be set to the selected device from the NCheck Bio Attendance web control panel as mentioned in :ref:`Edit device` section or Client control panel (Standalone mode) as mentioned in :ref:`Client peripheral configuration` section. Following table shows authentication types availability for the NCheck Bio Attendance clients. .. list-table:: Authentication modes availability for the clients :widths: 2045 1585 2038 1674 1674 * - Authentication mode - Lite - Standard - Surveillance - Guard * - Identification - .. figure:: Images/Clients/image54.PNG :width: 14 :figclass: align-center - .. figure:: Images/Clients/image54.PNG :width: 14 :figclass: align-center - .. figure:: Images/Clients/image54.PNG :width: 14 :figclass: align-center - .. figure:: Images/Clients/image54.PNG :width: 14 :figclass: align-center * - Verification - .. figure:: Images/Clients/image55.PNG :width: 17 :figclass: align-center - .. figure:: Images/Clients/image54.PNG :width: 14 :figclass: align-center - .. figure:: Images/Clients/image55.PNG :width: 17 :figclass: align-center - .. figure:: Images/Clients/image55.PNG :width: 17 :figclass: align-center * - None - .. figure:: Images/Clients/image55.PNG :width: 17 :figclass: align-center - .. figure:: Images/Clients/image54.PNG :width: 14 :figclass: align-center - .. figure:: Images/Clients/image55.PNG :width: 17 :figclass: align-center - .. figure:: Images/Clients/image55.PNG :width: 17 :figclass: align-center Identification """"""""""""""""""""""" The default authentication mode for NCheck Bio Attendance clients. Following table shows how the identification mode is working in clients. .. list-table:: Identification in clients :widths: 2045 6050 * - Client - Identification * - Lite and Standard client - Once the user identified using either form biometic or user id input, the client shows the :ref:`Result view` . * - Surveillance and Guard client - Once the user is identifed using face biometric, the surveillance client will show the :ref:`Result view for Surveillance client for Windows and Guard client for Android` . The Guard client shows the :ref:`Record event view` appears. Verification mode """""""""""""""""""""""""" In NCheck Bio Attendance standard clients, user can be verified using a biometric input and user id input. The verification UI flow can be changed from the NCheck Bio Attendance web control panel as mentioned in :ref:`Edit device` section or Client control panel (Standalone mode) as mentioned in :ref:`Client peripheral configuration` section as follows. #. User id first The client will be asked for a biometric input once a user id input is given first. #. Biometric first The client will be asked for a user id input once a biometric input is given first When the user is verified, client show the :ref:`Result view` . .. _Ref32906307: Manual event selection view ------------------------------------------------------------------ .. note:: Manual event selection is available for NCheck Bio Attendance Lite for Android and IOS and Standard client for Android only Manual event selection view allows to user to select the event type as check-in or check-out before record the attendance. To enable this feature :ref:`Manual capture start` setting from NCheck Bio Attendance Control panel :ref:`Client settings view` or :ref:`Device settings` should be enabled first. Manual event selection is available for #. :ref:`Manual event selection of Lite clients` #. :ref:`Manual event selection of Standard clients` .. _Ref41045750: .. _Ref41474441: Manual event selection of Lite clients +++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ Manual event selection view for NCheck Bio Attendance Lite for Android and IOS appears according to the authentication mode using the :ref:`Use in-built biometric verification on personal clients` setting. .. list-table:: Manual event selection view of Lite clients :widths: 1345 2430 5241 * - Lite client - Biometric authentication mode - View * - Android - Face - .. figure:: Images/Clients/image831.PNG :width: 241 :figclass: align-center Manual event selection view of Android lite client * - - Finger ID - .. figure:: Images/Clients/image833.PNG :width: 258 :figclass: align-center Manual capture start of finger ID view in Android Lite * - IOS - Face - .. figure:: Images/Clients/image835.PNG :width: 248 :figclass: align-center Manual capture start view of IOS lite client * - - Finger ID - .. figure:: Images/Clients/image837.PNG :width: 231 :figclass: align-center Manual capture start of face ID view in IOS Lite .. figure:: Images/Clients/image839.PNG :width: 241 :figclass: align-center Manual capture start of finger ID view in IOS Lite * - - Face ID - #. :ref:`Capture view` #. Check-in button #. Face Attendance will be recorded as Check-in event once the user face is identified by the NCheck Bio Attendance server. #. Finger ID Attendance will be recorded as Check-in event once the finger is authenticated successfully as mentioned in :ref:`Fingerprint authentication prompt for Android Lite` section. #. Face ID #. Check-out button #. Face Attendance will be recorded as Check-in event once the user face is identified by the NCheck Bio Attendance server. #. Finger ID Attendance will be recorded as Check-out event once the finger is authenticated successfully as mentioned in :ref:`Fingerprint authentication prompt for Android Lite` section. #. Face ID .. _Ref41045755: Manual event selection of Standard clients +++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ Manual event selection views of the NCheck Bio Attendance Standard clients are shown in :numref:`Ref32906423` . .. _Ref32906423: .. list-table:: Manual event selection in NCheck Bio Attendance standard clients :widths: 1848 6411 * - Android Lite - * - Android Standard - .. figure:: Images/Clients/image841.PNG :width: 333 :figclass: align-center Manual event selection view of Android standard client #. Organization logo #. Check-in button In Standard client, select check-in button to proceed to :ref:`Capture view` to record attendance as Check-in event. #. Check-out button In Standard client, select check-out button to proceed to  :ref:`Capture view` to record attendance as Check-out event. .. _Ref45094562: Record event view -------------------------------------------------------- .. note:: This view available in NCheck Bio Attendance Guard client only Once the face captured as mentioned in :ref:`Face capturing in Surveillance client of Windows and Guard client of Android` section, record view appears to side by side comparison of captured face image and matching face image of the user with the details such as user name and employee code as below. .. figure:: Images/Clients/image843.PNG :width: 224 :figclass: align-center Record event view #. Name of the view #. Application logo #. :ref:`Side by side comparison view` #. :ref:`Matching list view` .. _Ref45094008: Side by side comparison view +++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ Side by side comparison view represents both captured face image and matching user details to compare and proceed to record the event. .. figure:: Images/Clients/image845.PNG :width: 198 :figclass: align-center Side by side comparison view of Guard client #. Captured face image Captured face image of the user #. Selected person view #. Employee code selection If the person is not identified successfully by the server Guard can select the user manually by entering the employee code here #. Name and employee code of the selected person #. Event type as check-in or check-out Even type is not available for black list events #. Record button Record the event. The result will be appeared in the result view as mentioned in :ref:`Result view for Guard client for Android` section. Selected person view """"""""""""""""""""""""""""" The person appeared in this view can be recorded by the Guard. The selected person can be, #. :ref:`Whitelist person` #. :ref:`Blacklist person` #. :ref:`False match` .. _Ref45094034: Whitelist person ''''''''''''''''''''''''''''''''''''''''''''' If the selected person is not blocked it is known as whitelist person .. figure:: Images/Clients/image847.PNG :width: 184 :figclass: align-center Whitelist event view of Guard client #. Matching score The score when matching user face biometric with the captured image. #. Matching face image Face image from the biometric face image of the matching users which has the highest matching score. #. Remove button Removed the selected person The Guard allows to record the person as check-in or check-out. .. _Ref45094044: Blacklist person ''''''''''''''''''''''''''''''''''''''''''''' If the selected person is blocked, it is known as blacklist .. figure:: Images/Clients/image849.PNG :width: 226 :figclass: align-center Blacklist event view of Guard client #. Matching score The score when matching user face biometric with the captured image. #. Block indicator Block indicator appears if the user has blocked. #. Matching face image Face image from the biometric face image of the matching users which has the highest matching score. #. Remove button Removed the selected person The Guard can record the event as blacklist. .. _Ref52281670: False match '''''''''''''''''''''''''''''''''''''''' The captured person may not be existed in the database. In such cases, Guard can keep the selected person as empty (false match) and record the event. .. _Ref45094147: Matching list view +++++++++++++++++++++++++++++++++++++++++++++++++++++++++ This view is showing all identified person details. Once Guard selected a person from the list, selected user will be shown in :ref:`Side by side comparison view` either a :ref:`Whitelist person` or :ref:`Blacklist person` . .. figure:: Images/Clients/image851.PNG :width: 455 :figclass: align-center Close match list view of Guard client #. Selected user #. First name #. Employee code #. Matching score The score when matching user face biometric with the captured image. #. Biometric face image Face image from the biometric face image of the matching users which has the highest matching score #. Blocked indicator .. _Ref37694225: .. _Ref37694271: .. _Ref37694700: .. _Ref37694746: Result view -------------------------------------------------------------------------------------------------------- Result view shows the recorded event details. Result view as follows, #. :ref:`Result view for Standard and Lite clients` #. :ref:`Result view for Surveillance client for Windows and Guard client for Android` .. _Ref40889716: Result view for Standard and Lite clients ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ .. _Ref32851058: Result view for Single face mode """"""""""""""""""""""""""""""""""""""""""""""""""""""""""""" In the single face mode, the result view appears for the successful check-in or check-out events as follows. .. list-table:: Result view of the single face mode :widths: 1075 3775 4166 * - - Lite - Standard * - Windows - .. figure:: Images/Clients/image853.PNG :width: 271 :figclass: align-center Result view of Windows lite client - .. figure:: Images/Clients/image853.PNG :width: 271 :figclass: align-center Result view of Windows standard client * - Android - .. figure:: Images/Clients/image855.PNG :width: 223 :figclass: align-center Result view of Android lite client - .. figure:: Images/Clients/image857.PNG :width: 291 :figclass: align-center Result view of Android standard client * - IOS - .. figure:: Images/Clients/image859.PNG :width: 256 :figclass: align-center Result view of IOS lite client - Not Available #. User profile image #. Username #. Event type #. Total work hours of the day #. Total work hours of the week #. Total work hours of the month #. Event recorded time #. Check-in limitation message If the number of check-in are lower than the maximum occupancy for group premises, check-in will be recorded successfully. Otherwise check-in will be restricted. Refer :ref:`Maximum occupancy for group premises` setting in the server for more details. #. Cancel button Cancel the event recorded. This button will disappear in few seconds after the event result view appeared. .. _Ref37695174: Result view for multi face mode """""""""""""""""""""""""""""""""""""""""""""""""""""""""""" .. note:: This view is available in NCheck Bio Attendance Lite clients only. In multi face mode, result view appears with all users for all check-in check-out details as follows. .. list-table:: Result view of the multi face mode :widths: 1468 6756 * - - Lite * - Windows Client - .. figure:: Images/Clients/image861.PNG :width: 249 :figclass: align-center Result view of multi face mode in Windows lite client * - Android Client - .. figure:: Images/Clients/image863.PNG :width: 185 :figclass: align-center Result view of multi face mode in Android lite client * - IOS client - .. figure:: Images/Clients/image865.PNG :width: 277 :figclass: align-center Result view of multi face mode in IOS lite client .. _Ref40889728: .. _Ref32838523: Result view for Surveillance client for Windows and Guard client for Android +++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ As mentioned in :ref:`Record event view` section, NCheck Bio Attendance Guard client records following events. #. Whitelist event If the selected person by the Guard is not blocked and the event type as check-in or check-out #. Blacklist event If the selected person by the Guard is blocked, event will be recorded as blacklist #. False match event If the Guard select no person, the event will be recorded as false match. As mentioned in :ref:`Face capturing in Surveillance client of Windows and Guard client of Android` section, following events can be recorded in NCheck Bio Attendance Surveillance client for Windows. #. Whitelist event Event type as check-in or check-out. #. Blacklist event If the user is blocked, event will be recorded as blacklist #. Unidentified event Unidentified event will be recorded if #. No match available for the captured face image In this case user can select any user from the registered user group and record the event as whitelist or blacklist event. #. Close matches available for the captures face image In this case user can select the user from the close match list and record the event as whitelist or blacklist event. Following table is showing the views for all available events in Surveillance and Guard client. .. list-table:: Result view of events in Guard and Surveillance clients :widths: 1230 4241 3647 * - Matching event type - Surveillance client - Guard client * - Whitelist event - .. _Ref40796529: .. figure:: Images/Clients/image867.PNG :width: 267 :figclass: align-center whitelist event of Surveillance client - .. figure:: Images/Clients/image869.PNG :width: 246 :figclass: align-center Whitelist event of Guard client * - Blacklist event - .. figure:: Images/Clients/image871.PNG :width: 272 :figclass: align-center Blacklisted event in Surveillance client - .. figure:: Images/Clients/image873.PNG :width: 251 :figclass: align-center Blacklist event of Guard client * - Unidentified event (No match found) - .. figure:: Images/Clients/image875.PNG :width: 251 :figclass: align-center Unidentified event of Surveillance client - Not available * - Unidentified event (Close match found) - .. figure:: Images/Clients/image877.PNG :width: 250 :figclass: align-center Close match event of Surveillance client - Not available #. User profile image #. Username #. Event type #. Total work hours of the day #. Event time #. Edit button Edit the selected evet as mentioned in section #. Number of matches in the close match list This view appears for the unidentified events if multiple matched found. Edit event +++++++++++++++++++++++++++++ .. note:: This view is available NCheck Bio Attendance Surveillance client only. The recorded event can be edited in following case #. The captured face has matched with the different person(s) In this case, the captured face is matched with different person and the event will be recorded as Check-in, Check-out or blacklist. If the person is matched with multiple persons, the event will be recorded as unidentified event. #. The captured face has no match The captured face has matched with no person and the event will be recorded as unidentified. In such cases Guard allows to edit the event as follows. .. list-table:: Edit event view of Surveillance client :widths: 2065 6951 * - Event - Edit event View * - Person has matched with different person(s) - .. figure:: Images/Clients/image879.PNG :width: 475 :figclass: align-center Edit event view when matching with different person(s) * - Person has no match - .. figure:: Images/Clients/image881.PNG :width: 390 :figclass: align-center Edit event view when person has no match #. Employee code Guard allows to select the correct person using the employee code. The selected person will be updated in the :ref:`Side by side comparison view` . #. :ref:`Side by side comparison view` #. :ref:`Matching list view` #. Close button Close Edit event dialogue. .. _Ref45102545: Side by side comparison view """"""""""""""""""""""""""""""""""""""""""""""""""""""""" The side by side comparison view allows to compare the captured face of the person with matching parson(s) and record the event in following cases. #. The captured face has a match The captured face can be matched with either the server result or person selected by the Guard. In such cases event can be recorded as Check-in, Check-out or Blacklist if the person has been blocked. #. The face has not a match The Guard allows to record the event as false match if the captured person is not existing in the system. .. list-table:: Side by side comparison view of Surveillance client :widths: 1739 7277 * - Case - View * - Person has matched with person(s) - .. figure:: Images/Clients/image883.PNG :width: 514 :figclass: align-center Side by side comparison view when captured face has a match * - Person has no match - .. figure:: Images/Clients/image885.PNG :width: 480 :figclass: align-center Side by side comparison view when captured face has no match #. Captured face image of the user #. Matched/selected person view .. figure:: Images/Clients/image887.PNG :width: 301 :figclass: align-center Matched/selected person view #. Image Wither the face biometric image of the matched person or thumbnail image of the selected person. #. Matching score #. Employee code of the matched/selected user #. Blocked status This status is shown if the matched/selected person is blocked. #. Delete button Removed the matched/selected person. If the captured face image has no match, Guard can remove the matched/selected person using this button and record as false match. #. Event date and time #. Name of the matched user #. Employee code selection view User able to find the user entering employee code if no match found for the captured face image. Otherwise this will be disabled. #. Check-in button Record the event as Check-in if the matched/selected user is not blocked. #. Check-out button Record the event as Check-out if the matched/selected user is not blocked. #. Blacklist button Record the event as blacklist if the matched/selected user is blocked. #. Unidentified button #. False match button Record the event as false match, if the captured face image has no match. .. _Ref45102554: Matching list view """"""""""""""""""""""""""""""""""""""""""""""" .. figure:: Images/Clients/image889.PNG :width: 479 :figclass: align-center Close match list view of Surveillance client #. Selected user #. Face biometric image #. Matching score #. Employee code of the user #. Blocked indicator This indicator appears if the user is blocked. .. _Ref47602145: Recent events list --------------------------------------------------------- .. note:: This view is available in NCheck Bio Attendance clients for Windows only. Recently recorded attendances are showing in the recent events list. Recent event list view follows Resent event list views of Windows client .. list-table:: :widths: 2695 6321 * - - Recent event list view * - Standard and Lite clients - .. _Ref32852894: .. figure:: Images/Clients/image891.PNG :width: 175 :figclass: align-center Recent event list view of clients for Windows * - Surveillance client - .. figure:: Images/Clients/image893.PNG :width: 175 :figclass: align-center Recent event list view of Surveillance client #. :ref:`Event filter view` #. :ref:`Result view for Surveillance client for Windows and Guard client for Android` .. _Ref40794768: Event filter view ++++++++++++++++++++++++++++++++++++++++++++++++++++++++ .. figure:: Images/Clients/image895.PNG :width: 458 :figclass: align-center #. Event type #. Whitelist #. Blacklist #. Unidentified #. Close match #. Timeline selector Using the timeline selector, the timeline can be changed, and it will support 24 hours of period to backward. It will filter the events according to the timeline selected #. Timeline of the event By default, this shows the current timeline and timeline can be changed using the Time line selector. Client control panel ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ NCheck Bio Attendance Client Control panel available in clients if the :ref:`Offline operation mode` has enabled in Attendance Standard cloud/on-premises server as shown below. .. list-table:: Standard clients control panel availability on offline mode :widths: 1672 3342 3342 * - - Offline mode enabled - * - - Network available - Network disabled * - Cloud - .. figure:: Images/Clients/image55.PNG :width: 17 :figclass: align-center - .. figure:: Images/Clients/image54.PNG :width: 14 :figclass: align-center * - On-premises - .. figure:: Images/Clients/image55.PNG :width: 17 :figclass: align-center - .. figure:: Images/Clients/image54.PNG :width: 14 :figclass: align-center * - Standalone - .. figure:: Images/Clients/image54.PNG :width: 14 :figclass: align-center - .. figure:: Images/Clients/image54.PNG :width: 14 :figclass: align-center Following options are available in NCheck Bio Attendance Standard Client control panel for Android and Windows, .. list-table:: Control panel options of Standard clients :widths: 2515 1440 1800 1908 * - - Cloud - On-premises - Standalone * - :ref:`User management` - .. figure:: Images/Clients/image54.PNG :width: 14 :figclass: align-center - .. figure:: Images/Clients/image54.PNG :width: 14 :figclass: align-center - .. figure:: Images/Clients/image54.PNG :width: 14 :figclass: align-center * - :ref:`Peripheral view of clients` - .. figure:: Images/Clients/image55.PNG :width: 17 :figclass: align-center - .. figure:: Images/Clients/image55.PNG :width: 17 :figclass: align-center - .. figure:: Images/Clients/image54.PNG :width: 14 :figclass: align-center * - :ref:`Event logs` - .. figure:: Images/Clients/image54.PNG :width: 14 :figclass: align-center - .. figure:: Images/Clients/image54.PNG :width: 14 :figclass: align-center - .. figure:: Images/Clients/image54.PNG :width: 14 :figclass: align-center * - :ref:`Reports view` - .. figure:: Images/Clients/image55.PNG :width: 17 :figclass: align-center - .. figure:: Images/Clients/image55.PNG :width: 17 :figclass: align-center - .. figure:: Images/Clients/image54.PNG :width: 14 :figclass: align-center * - :ref:`Settings view` - .. figure:: Images/Clients/image55.PNG :width: 17 :figclass: align-center - .. figure:: Images/Clients/image55.PNG :width: 17 :figclass: align-center - .. figure:: Images/Clients/image54.PNG :width: 14 :figclass: align-center * - :ref:`Admin tasks of Clients` - .. figure:: Images/Clients/image54.PNG :width: 14 :figclass: align-center - .. figure:: Images/Clients/image54.PNG :width: 14 :figclass: align-center - .. figure:: Images/Clients/image54.PNG :width: 14 :figclass: align-center .. _Ref33025011: Login view ------------------------------------------------- .. list-table:: Login views of Clients control panel :widths: 1705 7311 * - Windows client - .. figure:: Images/Clients/image896.PNG :width: 429 :figclass: align-center Login view of Windows standard client * - Android client - .. figure:: Images/Clients/image898.PNG :width: 218 :figclass: align-center Login view of Android standard client #. Username #. Password The default control panel login password of the Android client is Admin. Windows client does not have a default password. The password can be changed as mentioned in :ref:`Standalone password view` section. #. Login button :numref:`Ref37670867` could be appeared when logging to the control panel. #. Cancel button .. _Ref37670867: .. list-table:: Error messages of control panel logging :widths: 1705 7231 * - Error code - Error message * - 2066 - Invalid password. Check the password again. .. _Ref38643055: User management ------------------------------------------------------ .. list-table:: User management views :widths: 1273 7719 * - Windows Client - .. figure:: Images/Clients/image900.PNG :width: 513 :figclass: align-center User management view of Windows standard client * - Android Client - .. figure:: Images/Clients/image902.PNG :width: 248 :figclass: align-center User management view of Android standard client #. Users list view #. User quick view In android Stannard client, select user quick view for :ref:`User view of Android Standard client` . #. Add button Refer :ref:`Add user` section for more details. #. Edit button Refer :ref:`Edit user` section for more details. #. Delete button Delete selected user. Refer :ref:`Edit user` section for more details of delete user. #. Refresh button Refer the user management view. #. :ref:`Manage biometrics` #. Search user #. Enroll from history button Refer :ref:`Enroll from Windows client history` section for more details. .. _Ref34826032: User view of Android Standard client +++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ User view of the Android Standard client preset all user details as follows. .. figure:: Images/Clients/image904.PNG :width: 232 :figclass: align-center User view of Android Standard client #. User first name and last name #. User menu #. Edit Edit user #. Remove Remove user #. Biometrics Manage biometrics as mentioned in :ref:`Manage biometrics` section #. User details view .. _Ref33428784: Add user +++++++++++++++++++++++++++++++++++++++++++++++ .. list-table:: Add new users view :widths: 1126 6851 * - Windows Client - .. figure:: Images/Clients/image906.PNG :width: 471 :figclass: align-center Add user view of Windows standard client * - Android Client - .. figure:: Images/Clients/image908.PNG :width: 482 :figclass: align-center Add user view of Android standard client #. User image thumbnail preview In Android standard client select the image thumbnail to browse the image file from the file system. #. Browse button Browse image from the file system #. First name #. Last name #. Employee code #. Barcode ID Refer :ref:`Capture barcode from client` section for more details. #. RFID tag Refer :ref:`Capture RFID from client` section for more details. #. Email #. Address line 1 #. Address line 2 #. City #. Country #. State #. Zip code #. Telephone #. Apply button Apply button will be disabled if the mandatory fields are empty or :ref:`Validation errors` exist. Refer :numref:`Ref34393986` for all error messages. #. Cancel button .. _Ref34393986: .. list-table:: Error messages of add/edit user in client control panel :widths: 1435 6480 * - Error code - Description * - 3001 - Mobile/telephone number is not valid for the selected country/region. * - 3002 - Invalid email address. * - 3005 - Barcode scanner could not be found. * - 3006 - RFID scanner could not be found * - 2020 - Selected file is not a valid image file. * - 2021 - Employee code already exists. * - 2022 - Barcode ID is already available for different user * - 2023 - RFID is already available for different user * - 2039 - Could not capture barcode. The device has been blocked * - 2040 - Could not capture RFID. The device has been blocked .. _Ref38104478: Capture barcode from client """""""""""""""""""""""""""""""""""""""""""""""""""""""" .. list-table:: Barcode field view :widths: 1705 7311 * - Windows client - .. figure:: Images/Clients/image910.PNG :width: 380 :figclass: align-center Barcode field view of Windows Standard client * - Android client - .. figure:: Images/Clients/image912.PNG :width: 379 :figclass: align-center Barcode field view of Android standard client #. Barcode text field #. Barcode capture button Select Capture button to scan the barcode from the client application as mentioned in :numref:`Ref32940676` . .. _Ref32940676: .. list-table:: Capturing barcode from Client applications :widths: 2062 6930 * - Android client - Scan the barcode after the barcode scan view appeared as shown in :numref:`Ref32936463` . #. Main menu #. Switch camera #. Change resolution #. Barcode scan area After successful scan, barcode id will appear in the barcode field. .. _Ref32936463: .. figure:: Images/Clients/image914.PNG :width: 204 :figclass: align-center Barcode capture view of Android client * - Windows client - #. Select the barcode field #. Scan the barcode from the connected barcode scanner #. After successful scan, barcode id will appear in the barcode field. .. _Ref38104495: Capture RFID from client """"""""""""""""""""""""""""""""""""""""""""""""""""" .. list-table:: RFID field view :widths: 1705 7311 * - Windows client - .. figure:: Images/Clients/image916.PNG :width: 351 :figclass: align-center RFID field view of Windows Standard client * - Android client - .. figure:: Images/Clients/image918.PNG :width: 324 :figclass: align-center RFID field view of Android standard client #. RFID text field #. RFID capture button Select Capture button to scan the RFID from the client application as mentioned in :numref:`Ref32936948` . .. _Ref32936948: .. list-table:: Capturing barcode from Client applications :widths: 1885 7107 * - Android client - #. Scan the RFID after the RFID scan view appeared as :numref:`Ref32936976` #. After successful scan, RFID id will appear in the RFIDID field. .. _Ref32936976: .. figure:: Images/Clients/image191.PNG :width: 137 :figclass: align-center RFID capture view of Android client * - Windows client - #. Select the RFID field #. Scan the RFID from the connected RFIC scanner #. After successful scan barcode id automatically appeared in the RFID field. .. _Ref32994165: Edit user +++++++++++++++++++++++++++++++++++++++++++++++++ .. list-table:: Edit user views :widths: 1748 7266 * - Windows client - .. figure:: Images/Clients/image920.PNG :width: 19 :figclass: align-center .. figure:: Images/Clients/image922.PNG :width: 432 :figclass: align-center Edit user view of Windows standard client * - Android client - .. figure:: Images/Clients/image924.PNG :width: 186 :figclass: align-center Edit user view of Android standard client #. User details view as mentioned in :ref:`Add user` section. .. _Ref32940231: .. _Ref32993777: Manage biometrics ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ To proceed to manage biometric view for particular user in NCheck Bio Attendance Android standard client, Select Biometric button of the :ref:`User view of Android Standard client` section. In the edit user view, if no biometric has been enrolled for user, NCheck Bio Attendance Android standard will show a notification to enroll biometric as shown in :numref:`Ref32994871` . #. Enroll button Select enroll button to select the biometric type as shown in :numref:`Ref32994816` to capture biometric. .. _Ref32994871: .. figure:: Images/Clients/image926.PNG :width: 318 :figclass: align-center “No template enrolled” notification in Android standard client .. list-table:: Manage biometrics view :widths: 1975 7041 * - Windows client - .. figure:: Images/Clients/image928.PNG :width: 253 :figclass: align-center Manage biometrics view of Windows standard client * - Android client - .. _Ref32994816: .. figure:: Images/Clients/image930.PNG :width: 156 :figclass: align-center Biometric type selection view of Android standard client .. figure:: Images/Clients/image932.PNG :width: 207 :figclass: align-center Manage biometrics view of Android standard client #. Enrolled face images list #. Capture face button Refer :ref:`Capture face from standard clients` section for more details. #. Enrolled fingerprint images list #. Capture fingerprints button Refer :ref:`Capture fingerprint from Standard clients` section for more details. #. Enrolled iris images list #. Capture iris button Refer :ref:`Capture iris from Windows standard client` section for more details Refer :ref:`Capture from client applications` section for the error message could be appeared while capturing biometrics. .. _Ref38104407: Enroll from Windows client history +++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ .. note:: This feature is not available for NCheck Bio Attendance Android client. This option allows enroll biometrics from previous recorded events from users who are not enrolled with NCheck Bio Attendance server. .. figure:: Images/Clients/image934.PNG :width: 520 :figclass: align-center Enroll from history view #. Date filter #. Unidentified biometric lists #. Delete button Delete event from the list #. Event date and time #. Enroll button Enroll selected biometrics from the list. :numref:`Ref34394805` is shown the error messages could be appeared when enroll biometrics from history #. Cancel button .. _Ref34394805: .. list-table:: Error messages of Enroll from history :widths: 1615 7401 * - Error code - Error message * - 2024 - Could not enroll selected face/finger/iris image. .. _Ref38104241: Peripheral view of clients ----------------------------------------------------------------- All available peripherals are showing in this view. The peripheral view as follows, .. list-table:: Peripherals list views :widths: 1342 6750 * - Windows Client - .. figure:: Images/Clients/image936.PNG :width: 376 :figclass: align-center Peripherals view of Windows standard client * - Android Client - .. figure:: Images/Clients/image938.PNG :width: 268 :figclass: align-center Peripherals view of Android standard client #. :ref:`Device details view of Windows standard client` #. Edit button Refer :ref:`Edit peripheral view` section for more details. In Android client double click on peripheral quick view. #. Refresh button #. :ref:`Peripheral list view of Windows standard client` #. :ref:`Peripheral quick view of Android standard client` .. _Ref32997924: Device details view of Windows standard client +++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ This view is showing device details as follows. .. figure:: Images/Clients/image940.PNG :width: 386 :figclass: align-center Device details view of Windows standard client #. Device name #. Name of the operating system #. Version of the operating system .. _Ref32997935: Peripheral list view of Windows standard client ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ This view shows all peripheral available with the device as follows. .. figure:: Images/Clients/image942.PNG :width: 426 :figclass: align-center Peripheral list view of Windows standard client #. Peripheral name #. Peripheral ID #. Status Peripheral is enabled or disabled. #. Selected peripheral Double click on the selected peripheral to get the :ref:`Edit peripheral view` . .. _Ref32997946: Peripheral quick view of Android standard client +++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ This view present details of the selected peripheral. .. figure:: Images/Clients/image944.PNG :width: 379 :figclass: align-center Peripheral quick view of Android standard client #. Peripheral type #. Peripheral ID #. Peripheral image This image become green when the peripheral is available with the device. Otherwise become grey color. Select the peripheral quick view to get the :ref:`Edit peripheral view` . .. _Ref32997993: Edit peripheral view +++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ .. list-table:: Edit peripheral views :widths: 1398 6861 * - Windows client - .. figure:: Images/Clients/image946.PNG :width: 390 :figclass: align-center Peripheral edit view of Windows standard client * - Android client - .. figure:: Images/Clients/image948.PNG :width: 203 :figclass: align-center Peripheral edit view of Android standard client #. Peripheral name #. Peripheral code A unique id for the peripheral. Peripheral code cannot be edited. #. Peripheral status Enable/disable the peripheral. #. Save button #. Cancel button .. _Ref33025050: Event logs ------------------------------------------------- .. list-table:: Event logs views :widths: 1162 7290 * - Windows Client - .. figure:: Images/Clients/image950.PNG :width: 499 :figclass: align-center Event logs view of Windows standard client * - Android Client - .. figure:: Images/Clients/image952.PNG :width: 251 :figclass: align-center Event logs view of Android standard client #. Event logs filter view #. Date filter Select the date to retrieve event logs. Default date is current date. #. Username filter Select the username to retrieve event logs. #. :ref:`Event logs list view of Windows standard client` #. Add button Refer :ref:`Add new event log` section for more details #. Edit button In Android standard client select on event log quick view for edit event log. Refer :ref:`Edit event log` section for more details. #. Delete button Delete selected event log. In Android client refer :ref:`Edit event menu of Android standard client` section for delete event log. #. Refresh button Refresh event logs view #. Re-evaluate button Select this button to re-arrange events check-in/check-out sequence of users. #. :ref:`Event log quick view of Android standard client` .. _Ref37695463: Event logs list view of Windows standard client ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ Event log list view of the Android standard client shows all event logs as follows. .. figure:: Images/Clients/image954.PNG :width: 429 :figclass: align-center Event logs list view of Windows standard client #. Username #. Employee code #. Event type as Check-in or Check-out #. Event date and time #. Selected event Double click on selected event to :ref:`Edit event log` . .. _Ref33004928: Event log quick view of Android standard client ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ Event log quick view of Android standard client shows details of the selected event log as follows .. figure:: Images/Clients/image956.PNG :width: 292 :figclass: align-center Event log quick view of Android standard client #. User thumbnail #. Username #. Employee code #. Event type as Check-in or Check-out #. Event date and time Select on event quick view to :ref:`Edit event log` . .. _Ref38104547: Add new event log ++++++++++++++++++++++++++++++++++++++++++++++++++++++++ .. list-table:: Add event logs view :widths: 1834 5220 * - Windows Client - .. figure:: Images/Clients/image958.PNG :width: 256 :figclass: align-center Add event log view of Windows standard client * - Android Client - .. figure:: Images/Clients/image960.PNG :width: 276 :figclass: align-center Add event log view of Android standard client #. Event thumbnail #. Person name #. Date #. Event time #. Event type #. Checkout #. Unidentified #. Not known #. Add button #. Cancel button .. _Ref33004793: Edit event log +++++++++++++++++++++++++++++++++++++++++++++++++++++ .. list-table:: Edit event log views :widths: 1526 5528 * - Windows Client - .. figure:: Images/Clients/image962.PNG :width: 265 :figclass: align-center Edit event log view of Windows standard client * - Android Client - .. figure:: Images/Clients/image964.PNG :width: 289 :figclass: align-center Add event log view of Android standard client #. Event details view as shown in #. :ref:`Edit event menu of Android standard client` .. _Ref33004890: Edit event menu of Android standard client """"""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""" This menu available in the Android standard client to delete the selected the selected event log .. figure:: Images/Clients/image966.PNG :width: 241 :figclass: align-center Edit event menu of Android standard client #. Delete The delete the selected event log .. _Ref33025066: Reports view --------------------------------------------------- .. list-table:: Report views :widths: 991 8018 * - Windows client - .. figure:: Images/Clients/image968.PNG :width: 534 :figclass: align-center Report view of Windows standard client * - Android client - .. figure:: Images/Clients/image970.PNG :width: 218 :figclass: align-center Report view of Android standard client #. Report type #. :ref:`Workhour report` #. :ref:`Event log report` #. Filter report by username #. Select report start date and end date to generate report #. :ref:`Report options of Windows standard client` #. Report data view #. Summarize report by daily, weekly, or monthly .. _Ref33007800: Report options of Windows standard client ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ Report options of the Windows standard clients available shown as below. .. figure:: Images/Clients/image972.PNG :width: 255 :figclass: align-center Report options view of Windows standard client #. Refresh button Refresh report view. #. Print button Print the report. #. Save CSV button Save report in CSV format. #. Save PDF button Save report in PDF format. .. _Ref33007763: Workhour report ++++++++++++++++++++++++++++++++++++++++++++++++++++++ .. list-table:: Details in the workhour report :widths: 1936 6426 * - Windows client - Report columns as follows #. Date The date for the workhour entry. #. Name Name of the employee. #. Employee code #. Productive work hours Work hours without early arrival and late departure. * - Android Client - Report columns as follows #. Workday Day for the entry. #. Full name First name and last name of the user. #. Employee code #. Work hours The number of work hours for the day. .. _Ref33007769: 6.7.5.3 Event log report +++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ .. list-table:: Details in the Event log report :widths: 1885 6387 * - Windows Client - Report columns as follows #. Name Name of the employee #. Employee code #. Direction The event as check-in or checkout #. Time Event time * - Android Client - Report columns as follows #. Workday Day for the entry. #. Full name First name and last name of the user. #. Employee code #. Event time Date and time the event is performed. #. Event type Event type as check-in or checkout. .. _Ref33025095: Settings view ---------------------------------------------------- #. :ref:`General settings of clients` #. :ref:`Shift settings of clients` #. :ref:`Biometric settings of clients` #. :ref:`Client peripheral configuration` .. _Ref38104599: General settings of clients ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ .. list-table:: General setting views :widths: 1975 7041 * - Windows client - .. figure:: Images/Clients/image974.PNG :width: 465 :figclass: align-center General setting view of Windows standard client * - Android client - .. figure:: Images/Clients/image976.PNG :width: 293 :figclass: align-center General setting view of Android standard client #. The interval between consecutive face scans Minimum time difference between two ancillary events to prevent event duplication for the user. #. :ref:`KIOSK mode operation (For Microsoft Windows clients)` #. :ref:`KIOSK mode exit code` #. :ref:`Event log image size` #. :ref:`Standalone password view` #. Enable/disable :ref:`Manual capture start` #. Save button .. _Ref37695231: Standalone password view """"""""""""""""""""""""""""""""""""""""""""""""""""" .. list-table:: Standalone password view of clients :widths: 2065 6951 * - Windows client - .. figure:: Images/Clients/image978.PNG :width: 331 :figclass: align-center Standalone password view of Windows standard client * - Android client - .. figure:: Images/Clients/image980.PNG :width: 394 :figclass: align-center Standalone password view of Android standard client #. Empty password Select this option to login control panel with empty password. #. Current password #. Password New password. #. Confirm password #. Save button Save password details. Save button will be disabled if the mandatory fields are empty or :ref:`Validation errors` exist. Al errors message could be appeared as shown below. .. list-table:: Error messages of password save :widths: 1345 5670 * - Error code - Error message * - 3003 - Password does not match. * - 3004 - Password must contain at least 6 characters with one number. * - 3012 - Current password is incorrect .. _Ref38104608: Shift settings of clients ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ .. list-table:: General settings :widths: 2058 6847 * - Windows Client - .. figure:: Images/Clients/image982.PNG :width: 310 :figclass: align-center Shift settings view of Windows standard client * - Android Client - .. figure:: Images/Clients/image984.PNG :width: 343 :figclass: align-center Shift settings view of Android standard client #. :ref:`Default shift start time` #. :ref:`Default shift end time` #. :ref:`Day start time` #. Save button .. _Ref38104617: Biometric settings of clients ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ .. list-table:: Biometric settings views :widths: 1255 7560 * - Windows Client - .. figure:: Images/Clients/image986.PNG :width: 393 :figclass: align-center Biometric settings of Windows standard client * - Android Client - .. figure:: Images/Clients/image988.PNG :width: 195 :figclass: align-center Biometric settings of Android standard client #. :ref:`Face liveness mode` #. :ref:`Face liveness threshold` #. Face template size Size of each face enrolled template among medium or large. Large face template contains more details than medium. #. :ref:`Recognition threshold` #. :ref:`Verification threshold` #. :ref:`Enrollment threshold` #. :ref:`Face confidence` #. :ref:`Face quality` #. :ref:`Fingerprint quality` #. Iris quality threshold Increase the value if the same user identified differently from time to time. By increasing the value, the system is forced to ignore low quality iris scans. #. :ref:`Hat detection threshold` #. :ref:`High-speed face detection` #. :ref:`Hat detection feature` #. :ref:`Hide user list on windows client` #. :ref:`Mask detection` #. :ref:`Mask detection threshold` #. Save button .. _Ref37695541: Client peripheral configuration ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ .. list-table:: Peripheral configuration views :widths: 1605 7117 * - Windows client - .. figure:: Images/Clients/image990.PNG :width: 492 :figclass: align-center Peripheral configuration view of Windows standard client * - Android client - .. figure:: Images/Clients/image992.PNG :width: 240 :figclass: align-center Peripheral configuration view of Android standard client #. Authentication mode Available authentication modes are, #. Identification Identification is the default authentication mode. Identification is performed on biometric and user id data. User biometric data such as face, finger print and iris are comparing against the database with previously collected biometric samples depending on the :ref:`Recognition threshold` . If the matching score is greater than the :ref:`Recognition threshold` , user is considered as identified. Therefore, this mode may demand large processing time. User id data such as user id, barcode and QR code are comparing against the database and giving the matching users. #. Verification The verification mode can be applied with a user id peripheral and a biometric peripheral in order to verify the user against the previously collected biometric sample. To get verified, matching score should be greater than :ref:`Verification threshold` . .. figure:: Images/Clients/image345.PNG :width: 333 :figclass: align-center Combinations of user id peripheral with biometric peripheral in verification mode #. None #. Capture id first The verification sequence when the verification is selected as the authentication mode. If the capture Id first has enabled, id input should be input before the biometric. Otherwise biometric should be given at first. #. Events Attendances will be recorded in the specific event type as selected from this option. #. check-in #. checkout #. any Both Check-in and Check-out events #. Manage external executable Refer :ref:`Manage external executables` section. #. Save button .. _Ref33018632: Manage external executables """""""""""""""""""""""""""""""""""""""""""""""""""""""" NCheck Bio Attendance Standard clients can be configured to run external programs (Either from external executable or API) during user identification. For an example, an automatic door opening program can be executed upon successful user identification. Following setting should be specified to configure external programs. .. figure:: Images/Clients/image994.PNG :width: 443 :figclass: align-center Manage external executables view #. :ref:`External executable lists` #. :ref:`Add external executable` #. Edit external executable Edit external executable in Windows standard client #. Delete external executable Delete selected external executable. .. note:: NCheck Bio Attendance Android standard client doesn’t support on multiple external executable. It only allows to as single external executable to trigger APIs. .. _Ref33018658: External executable lists """""""""""""""""""""""""""""""""""""""""""""""""""""" External executable list as follows. .. figure:: Images/Clients/image996.PNG :width: 383 :figclass: align-center External executables list of Windows standard client #. Name of the external executable #. Path to the EXE/URL of the API .. _Ref33018672: Add external executable """""""""""""""""""""""""""""""""""""""""""""""""""" .. list-table:: Add external executable view of Windows standard client :widths: 1647 6861 * - Windows client - .. figure:: Images/Clients/image998.PNG :width: 485 :figclass: align-center Add external executable view of Windows client * - Android client - .. figure:: Images/Clients/image1000.PNG :width: 212 :figclass: align-center Add external executable view of Android client #. Name Name of the external executable. #. Path of the external executable Path of the external executable or API URL to invoke. #. Trigger on #. Any Trigger the executable when record check-in or checkout events. #. Check-in Trigger executable when record check-in event. #. Check-out Trigger executable when record checkout event. #. Unidentified Trigger executable when the record is not identified as check-in or checkout. #. Parameter Following parameter(s) can be passed to the external executable when triggering the executable. #. Event (EVENT) Event type as CHECKIN, CHECKOUT or UNIDENTIFIED. #. Sequence id (SEQUENCE_ID ) Id of the event. #. Time stamp (TIMESTAMP ) Date and time of the event. #. User reference (USER_REF ) Employee code of the user. #. User name (USER_NAME) First name and last name of the user event recorded. #. Shift code (SHIFT_CODE ) Shift code of the NCheck Bio Attendance Standard clients. In the standalone mode shfit code is DEFAULT. #. Location (LOCATION ) Longitude and latitude of the event geo-location. Example: {Longitude,lattitude} #. User status (USER_STATUS ) User is blocked or not. Pass 0 if the user has blocked otherwise 1. #. Address (ADDRESS) Address of the user. #. Peripheral code (PERIPHERAL _CODE ) Unique identified number of the peripheral. The applied parameters will be passed to the external executable as below when recording events. .. list-table:: Parameters with external executable path or URL :widths: 1705 7149 * - Type - Format * - External executable - #. Value of the parameters will be separated with empty space #. Example: {parameter value 1} {parameter value 2} {parameter value 3} * - URL - #. As URL parameters #. Example: {url}?{Paramter1}={value}&{Paramter2}={value}&{Paramter3}={value .. note:: NCheck Bio Attendance Standard client for Android is supported for URLS’s only. .. _Ref38104322: Admin tasks of Clients ------------------------------------------------------------- .. list-table:: Admin tasks views :widths: 1705 7311 * - Windows client - .. figure:: Images/Clients/image1002.PNG :width: 431 :figclass: align-center * - Android client - .. figure:: Images/Clients/image1004.PNG :width: 222 :figclass: align-center Admin tasks view of Android standard client #. :ref:`Data import` #. :ref:`Data export` #. :ref:`Database backup and restore` #. :ref:`Database encription` #. :ref:`Biometrics` #. :ref:`Audit logs` .. _Ref33427227: Data import/export +++++++++++++++++++++++++++++++++++++++++++++++++++++++++ This allows to import/export below information. #. User profile information #. First name #. Last name #. Employee code #. Email #. Primary telephone number #. Address1 #. Address2 #. State #. Country #. State province region #. Zip or postal code #. Barcode #. RFID #. Created date and time #. System Id #. Event log information #. Check-in latitude #. Check-in longitude #. Check-in address #. Check-in description #. Check-out latitude #. Check-out longitude #. Check-out address #. Check-out description #. Employee code #. Check-in time #. Check-out time #. Shift start time #. OT start time #. Shift span seconds #. OT span seconds #. OT enabled or not #. OT limit in hours #. Check-in timezone #. Check-out timezone #. Work hours #. Maximum OT hours .. note:: All date time should be MM/dd/yyyy h:mm:ss a format and date format should be MM/dd/yyyy format when export data. To import/export data successfully following, following guidelines must be satisfied. #. The file names of csv files (user profile information and event logs ) should be User profile information : PersonData.csv event logs : EventLogData.csv #. All date format must be MM/dd/yyyy. #. All time format must be h:mm:ss. #. The column names should be equal as above. #. Country, state, provincial code, zip/postal code, email and telephone number should be in correct format. .. _Ref37695696: Data import """""""""""""""""""""""""""""""""""""""" .. list-table:: Date import views :widths: 1800 6459 * - Windows client - .. figure:: Images/Clients/image1006.PNG :width: 351 :figclass: align-center Data import view of Windows Standard client * - Android client - .. figure:: Images/Clients/image1008.PNG :width: 255 :figclass: align-center Data import view of Android standard client #. Importing information #. User profile information #. Event logs information #. Import location Select the file path of the importing file. #. Encrypted password of the importing file #. Status Importing status in successful or fail attempts. #. Import button Import button will be disabled if the mandatory fields are empty or :ref:`Validation errors` exist. :numref:`Ref37674886` is showing error messages could be appeared. #. Close button .. _Ref37674886: .. list-table:: Error messages of import data from clients :widths: 1255 6930 * - Error code - Error message * - 2062 - Data import failed. Invalid password. * - 2063 - Data import failed. The selected file could not be imported. * - 4003 - Unidentified error occurred during data import. Please contact administrator or NCheck Bio Attendance support for more details. .. _Ref33024737: Data export """""""""""""""""""""""""""""""""""""""" .. list-table:: Data export views :widths: 1795 6570 * - Windows client - .. figure:: Images/Clients/image1010.PNG :width: 384 :figclass: align-center Data export view of Windows standard client * - Android client - .. figure:: Images/Clients/image1012.PNG :width: 245 :figclass: align-center Data export view of Windows standard client #. Exporting information #. User profile information #. Event log information #. Select path to export location #. Password to encrypt the exporting file #. Confirm password #. Status Exporting status in successful or fail attempts. #. Export button Export button will be disabled if the mandatory fields are empty or :ref:`Validation errors` exist. :numref:`Ref37675059` is showing error messages could be appeared. #. Close button .. _Ref37675059: .. list-table:: Error messages of export data from clients :widths: 1255 6930 * - Error code - Error message * - 3003 - Password does not match. * - 3004 - Password must contain at least 6 characters with one number. * - 4004 - Unidentified error occurred during data export. Please contact administrator or NCheck Bio Attendance support for more details. .. _Ref33024747: Database backup and restore ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ Database backups and restore allows to back up the database as JSON files in a zip file securely and restore back in the application. The backup file contains, #. Person.json All user information added as mentioned in :ref:`Add user` section. #. Authentication.json All authentication information of users such as biometrics, RFID and barcode. #. eventlogsPairViews.json All check-in and check-out pairs are backup in this file. #. settings.json All settings as mentioned in :ref:`Settings view` section are kept in this file. .. note:: We are recommending to keep backup files safe without alter any information to prevent backup restore failures. Backup and restore feature are not available for NCheck Bio Attendance Android standard client. Database backup """""""""""""""""""""""" This view allows to backup the database as follows. .. figure:: Images/Clients/image1014.PNG :width: 396 :figclass: align-center Backup database view of Windows standard client #. Database backup location #. The password to encrypt backup file Password must have at least 6 characters with on digit. #. Confirm password #. Status Database backup status in successful or fail attempts. #. Back up button Backup button will be disabled if the mandatory fields are empty or :ref:`Validation errors` exist. :numref:`Ref34725525` Show all the error messages could be occurred. #. Close button .. _Ref34725525: .. list-table:: Error messages of backup database in clients :widths: 1525 6030 * - Error code - Error message * - 3003 - Password does not match. * - 4001 - Unidentified error occurred during data backup. Please contact administrator or NCheck Bio Attendance support for more details. Database restore """"""""""""""""""""""""" This view allows to restore backup databases as follows. .. figure:: Images/Clients/image1016.PNG :width: 396 :figclass: align-center Restore database view of Windows client #. Database location #. Database encrypted password #. Status Database restore status in successful or fail attempts. #. Restore button Restore button will be disabled if the mandatory fields are empty or :ref:`Validation errors` exist. :numref:`Ref34725559` Show all the error messages could be occurred. #. Close button .. _Ref34725559: .. _Ref33024758: .. _Ref33024849: .. list-table:: Error messages of data backup and restore view :widths: 1255 6750 * - Error code - Description * - 2015 - Data restore has been failed. Could not decrypt the file with the given password * - 2014 - Data restore has been failed. Invalid backup file * - 4002 - Unidentified error occurred during data restore. Please contact administrator or NCheck Bio Attendance support for more details. .. _Ref38104718: Database encryption ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ .. note:: Database encryption feature is not available for NCheck Bio Attendance Android standard application. Database encryption could be done as follows. .. figure:: Images/Clients/image1018.PNG :width: 458 :figclass: align-center Encrypt database view of Windows standard client #. Password Password must have 8 characters with one uppercase character and one digit. #. Confirm password Save button will be disabled if the password and confirm password fields are empty or validation errors as shown in :numref:`Ref34726461` #. Save button .. _Ref34726461: .. list-table:: Error messages of database encryption :widths: 1525 6030 * - Error code - Error message * - 3003 - Password does not match. .. _Ref38104753: Biometrics +++++++++++++++++++++++++++++++++++++++++++++++++ Re-extract users’ biometric templates from biometric engine and re-enroll. .. list-table:: Re-extraction views :widths: 1785 7221 * - Windows client - .. figure:: Images/Clients/image1020.PNG :width: 453 :figclass: align-center Re-extract template view of Windows standard client * - Android client - .. figure:: Images/Clients/image1022.PNG :width: 322 :figclass: align-center Re-extract template view of Android standard client #. Status Status of the template extraction as in-progress, Finished or failed. #. Re-enroll button Select re-enroll button to begin extraction. The extraction time will be depended on number of templates to re-enroll. :numref:`Ref37675611` is showing the error messages during re-extraction. #. Finish button Select finish button to finish re-enroll task while in-progress or finish. #. Cancel button .. _Ref37675611: .. list-table:: Error messages of biometric re-extraction view :widths: 1255 5490 * - Error code - Error messages * - 2002 - License cannot be obtained * - 2048 - Biometric re-extraction has failed on following images. #. {images list} .. _Ref33024865: 6.7.7.5 Audit logs +++++++++++++++++++++++++++++++++++++++++++++++++++++++++ This view shows date and time with the actions history performed by the user in the control panel. The following actions types are logged by the application. .. list-table:: Admin logs views :widths: 1052 7218 * - Windows client - .. figure:: Images/Clients/image1024.PNG :width: 469 :figclass: align-center Manage audit log view of Windows standard client * - Android client - .. figure:: Images/Clients/image1026.PNG :width: 244 :figclass: align-center Manage audit log view of Android standard client #. Action type Filter audit logs by action type #. Date filter with start and end date #. :ref:`Audit logs list view` The available action types are #. LOGIN Date and time for the admin logins. #. LOGOUT Date and time for the admin logouts. #. ADDEVENTLOG Date and time when event logs added. #. MODIFYEVENTLOG Date and time when event logs modified. #. DELETEVENTLOG Date and time when event logs deleted. #. ADDPERSON Date and time when persons added. #. MODIFYPERSON Date and time when persons modified. #. DELETEPERSON Date and time when persons deleted. .. _Ref33430156: Audit logs list view """"""""""""""""""""""""""""""""""""""""""""""""" .. list-table:: Audit log list views :widths: 1335 7176 * - Windows client - .. figure:: Images/Clients/image1028.PNG :width: 457 :figclass: align-center Audit logs list view of Windows standard client * - Android client - .. figure:: Images/Clients/image1030.PNG :width: 260 :figclass: align-center Audit logs list view of Android standard client #. Username #. Action type #. Description #. Created date and time