Griaule Mobile

First Access Flow

• By clicking "Sign in with organization", you can scan a QR Code or enter the URL manually

• To obtain the QR Code, speak with the person responsible for your organization

  • If your organization does not have a URL, create one and contact Griaule Support to register it

• If you want to change your organization, click "Change organization" and repeat the previous steps

Features

The features below are included in version 1.7 of Griaule Mobile

Search Motivation

When performing a search (either verification or identification) it is mandatory to register a reason why this search is being performed. This information will be sent in the transaction metadata, and can be searched later for:

• Audit

• Display in reports

• Display in the search history

A checkbox below the window with the option "Remember reason" is shown; when selected, it will keep the motivation field filled the next time it is opened (regardless of whether the operations are different). The field will stop being filled only when it is deselected and a search is performed, then it will be shown blank on the next search.

This feature is optional and configurable at the organization level

To enable it, the field must be changed mobile.confs in the table sphinx.settings

• Name: requireSearchReason

• Path: operations.requireSearchReason

• Type: Bool

• Default: false

• Required: No

  "operations": {
    "requireSearchReason": true, // new field
    "identify": {
      "faceCapture": {
        "frontCameraDefault": true,
        "isEnabled": true,
        "rotationEvaluation": false,
        "showPreview": false,
        "smileEvaluation": false
      }

Transaction History

The transaction history feature displays all transactions made by the user, allowing a report related to that transaction to be exported.

Currently, transactions are saved locally on the phone.

If BCC Web does not support the metadata field, the data "reason for search" and "collected biometrics" will not be available

Verification

In the case of 1:1 operations the following are displayed:

• Score

• Reason

• CPF (search key)

• Date and Time of the transaction

• Submitted biometrics

When requesting the report, it is generated immediately, with no additional steps required

Identification

In the case of 1:N operations the following are displayed:

• Highest score obtained among the candidates

• Reason

• Date and time

• Submitted biometrics

When requesting the report, a window is displayed with the candidates brought in the query, requiring the selection of the individual to generate the report between the two people

In the case where the 1:N operation returns only one candidate, the report is generated immediately

Report Generation

There is the possibility of generating a negative report (case in which the verification/identification fails to identify someone in the database).

Reports can be generated in two ways:

• Through the Candidate Profile screen

  • Allows generating only one report

• Through the history screen

  • Allows generating multiple reports at once

Individual Report

To generate the individual report, there is a button available in the upper right corner of the Profile screen; when generated, the report includes:

• Search Data

• Selected Profile Data

The report does not include a "MATCH" decision, only the Score resulting from the operation, since the final match decision is up to the operator.

Multiple Reports

By pressing an operation on the history screen it will be selected, allowing multiple operations to be selected to generate reports automatically.

The reports include:

• Search Data

• Data of all candidates who matched

If BCC Web is not in a version that supports sending metadata, the data "reason for search" and "collected biometrics" will not be available