> For the complete documentation index, see [llms.txt](https://docs.griaule.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.griaule.com/gbs/en/applications/gbs-identity.md).

# GBS Identity

![GBS Identity](https://content.gitbook.com/content/7Bx0xNdsdGHpCZ20yxbn/blobs/hNV9Ily3QXVgm9JhZrZb/images/capa-gbs-identity.png)

## 1. Overview

GBS Identity is a web application intended for the creation and lookup of **biometric records** of individuals. Each record (internally called an *encounter*) brings together:

* **Biographical data** — keys, name, parentage, date of birth (depending on the environment configuration).
* **Biometrics** — facial image, fingerprints, and signature.

After submission, the system registers the individual in the ABIS and triggers a **1:N biometric search** that returns matching profiles. The operator can then view the information of the profiles found in the database, validating the identity.

Main capabilities for the operator:

* Create and submit records, even without a connection (offline mode).
* Search record history.
* View biometric search results.
* Monitor the status of biometric devices and dependent services.
* View aggregated metrics for captures, submissions, and matches.

## 2. Prerequisites

### 2.1 Browser and installation

* Recommended browser: up-to-date Google Chrome or Microsoft Edge.
* GBS Identity is a **PWA** (Progressive Web App). It can be used *offline* and can be installed on the computer.
  * After the first access with internet, application resources are stored in *cache* locally, allowing offline use.
  * To install it as an operating system app, click the installation icon in the browser address bar. GBS Identity will then open as a dedicated window, without needing the browser, and will be available in the *Windows menu*.

{% hint style="info" %}
**Important:** the first access must always be done with internet, so that the browser installs the *Service Worker* and downloads the components needed for offline use.
{% endhint %}

### 2.2 Extension and biometric devices

Biometric capture takes place through the **Live Capture Extension**, which communicates with the computer's USB devices (face camera, fingerprint reader, and signature pad). Before starting a record, make sure that:

* The **Live Capture Extension** is installed in the browser.
* The **Live Capture Connector** is installed on the operating system (*drivers* and *plugins* for the devices).
* The physical devices are connected via USB and turned on.

The status of each component can be checked at any time on the page **System Diagnostics** and in the indicator in the upper-right corner (see Section 5).

### 2.3 Connection and server

* For immediate submission of records, internet connectivity and availability of the identification server (ABIS) are required.
* When offline, the record is saved locally and sent automatically as soon as the connection and the server become available again.

## 3. Access and login

GBS Identity uses the new integrated authentication of the GBS suite through *GBS Auth*. In this mode, *authentication* is mediated by the identity provider *(IdP - Identity Provider)* of the client's organization. When accessing the application, you are redirected to the identity provider's login screen. After authenticating with your credentials, the browser returns to GBS Identity with your session already open.

The user's name appears in the upper-right corner of the header. The available features depend on the **permissions** assigned to your profile.

To end the session, click the avatar (upper-right corner) and select **Log out**. You will be redirected back to the login screen.

![Logout menu](https://content.gitbook.com/content/7Bx0xNdsdGHpCZ20yxbn/blobs/nY9QvHt1zAaoiH0xEDUs/images/login-logout.png)

## 4. Application layout

Every page has the same structure: left sidebar, fixed header at the top, and central content area.

![Application layout](https://content.gitbook.com/content/7Bx0xNdsdGHpCZ20yxbn/blobs/ttC7OKLh9txcr20WeJ9i/images/layout-aplicacao.png)

### 4.1 Sidebar (left)

Shows the main navigation items. It can be collapsed/expanded using the button at the bottom.

| Item           | What it does                                                                              |
| -------------- | ----------------------------------------------------------------------------------------- |
| **Home**       | Home page. Shortcut to create a new record and view recent activity.                      |
| **New Record** | Opens the record creation form (only if you have write permission).                       |
| **Records**    | Lists and searches all records (all users, if you are an administrator) or only your own. |
| **Metrics**    | Panel of aggregated usage indicators (only for users with metrics permission).            |

Menu items you cannot access (due to lack of permission) are hidden. The application version is displayed at the bottom of the sidebar.

### 4.2 Header (top)

The header shows the title of the current page and, on the right side, the following icons (from left to right):

* **Ready to Send** — shortcut to the *Submission Log* (page with records pending synchronization). Appears when there are records waiting to be sent.
* **System status indicator** — signals in real time whether all components (devices, extension, ABIS, internet) are operational. Clicking opens the page of *System Diagnostics*. Colors: `GREEN` everything ok, `YELLOW` warning (something non-critical failed), `RED` critical (prevents new records).
* **Start page tour** (help icon) — starts a contextual guided tour with explanations about each element on the current screen.
* **User avatar and name** — opens the account menu, with the option **Log out**.

### 4.3 Guided tour and onboarding

On each page, the help button (icon with "?") starts an **interactive tour** with step-by-step explanations of the screen elements. Tours are available in:

![Tour button](https://content.gitbook.com/content/7Bx0xNdsdGHpCZ20yxbn/blobs/njjfZ61yvBchFbJNfjBA/images/botao-tour.png)

* **Home** — general presentation of the application, offline mode, and installation as a PWA.
* **New Record** — explanation of the biographical and biometric steps.
* **Records** — search and reading of the listing.
* **Record details** — reading of biometric search results.

The steps shown in the tour adapt to your permissions and the state of the screen. Use the buttons **Previous**, **Next** and **Finish** to navigate.

![Onboarding tour](https://content.gitbook.com/content/7Bx0xNdsdGHpCZ20yxbn/blobs/N5CeprOGotH2xOCSv8uj/images/tour-onboarding.png)

## 5. System status and diagnostics

### 5.1 Indicator in the header

A small panel in the header continuously monitors each component. Clicking it takes you to the page **System Diagnostics**.

<figure><img src="https://content.gitbook.com/content/7Bx0xNdsdGHpCZ20yxbn/blobs/dlvaFIwAZQp4tfYPGYMd/images/indicador-diagnostico.png" alt="Indicador de Diagnóstico"><figcaption><p>Diagnostics Indicator</p></figcaption></figure>

### 5.2 System Diagnostics page

![System Diagnostics page](https://content.gitbook.com/content/7Bx0xNdsdGHpCZ20yxbn/blobs/kAorwHTA6WkAkL8WQBaG/images/pagina-diagnostico.png)

Accessible via the header indicator or the account menu. It checks six components:

| Component                         | What it checks                                                                         | Critical?                 |
| --------------------------------- | -------------------------------------------------------------------------------------- | ------------------------- |
| **Capture System**                | Live Capture Extension installed and Connector active (main biometric capture engine). | Yes                       |
| **Facial Capture Device**         | Camera detected, access permission granted by the browser.                             | Yes                       |
| **Fingerprint Scanner**           | Driver, SDK, USB device, and access.                                                   | Yes                       |
| **Signature Pad**                 | Driver, SDK, USB device, and access.                                                   | Yes                       |
| **Identification Service** (ABIS) | Connection to the biometric search system.                                             | No (limits functionality) |
| **Internet Connection**           | Network connectivity.                                                                  | No (limits functionality) |

Each component is displayed in a card with its status — `ONLINE`, `OFFLINE`, `CRITICAL`, `UNAVAILABLE`. When there is a failure, the card shows a **Resolution Steps** section with specific instructions.

### 5.3 Status banners

{% hint style="danger" %}
**Critical problem identified** — at least one essential component (extension or biometric device) is unavailable. **It will not be possible to start new records** until it is resolved. Follow the steps indicated in the corresponding card.
{% endhint %}

{% hint style="warning" %}
**System Warning** — non-critical components are unavailable (ABIS or internet). You can continue to use the system with limited functionality (for example, records are saved locally for later submission).
{% endhint %}

### 5.4 Common sub-statuses

| Status               | Meaning                                      | Typical action                                                             |
| -------------------- | -------------------------------------------- | -------------------------------------------------------------------------- |
| Denied               | The browser blocked access to the device.    | Check the permissions in the address bar.                                  |
| Not Found            | The device was not detected by the system.   | Check the USB connection and cable.                                        |
| In Use               | The device is being used by another program. | Close other software that may be using the device.                         |
| Not installed        | The driver or extension was not installed.   | Install the Live Capture Extension/Connector (clickable link on the card). |
| Incompatible version | The installed version is not supported.      | Update the driver/extension to the recommended version.                    |

## 6. Home

![Home page](https://content.gitbook.com/content/7Bx0xNdsdGHpCZ20yxbn/blobs/BHh5fyCBs3O91C2GkyGG/images/home.png)

It is the application home page, accessible via the item **Home** of the sidebar. It contains two blocks:

### 6.1 Start New Record

Highlighted button at the top. Click and it opens the new record creation page (Section 7). Appears only if you have create permission.

### 6.2 Recent Activity

List of the **5 most recent records** you have access to, with name (when available), creation date, and current status. Each item is clickable and takes you to the record details page.

![Recent activity](https://content.gitbook.com/content/7Bx0xNdsdGHpCZ20yxbn/blobs/McGpe9hqdNK5zBMYdGtx/images/atividade-recente.png)

Behavior:

* **Online:** shows the 5 most recent records from the server.
* **Offline:** shows the 5 most recent records stored locally (not yet sent).
* When there are records with status **Search Requested**, the dashboard updates automatically every 10 seconds to reflect the progress until all are completed.

The link **See more →** opens the full records page (online) or the Submission Log (offline).

## 7. Create a New Record

This is the core feature of GBS Identity. The standard flow has five steps, shown in sequence with a progress indicator at the top:

{% stepper %}
{% step %}

### Biographical Data

Fill in the individual's information. The fields shown depend on the installation configuration.

Required fields appear in red. Some fields have automatic masking and immediate validation — if the value is invalid, the message appears below the field and the **Next** button is disabled.

Click **Next** to move forward.

![Biographical data step](https://content.gitbook.com/content/7Bx0xNdsdGHpCZ20yxbn/blobs/t13XG2VDK7vDTt8q4OGe/images/etapa1-dados-biograficos.png)
{% endstep %}

{% step %}

### Facial Capture

The live capture component displays the camera image. By default, capture starts automatically and the system uses **ICAO** quality verification to ensure a suitable image.

When the image is captured successfully, the message appears *"Face captured successfully"* and the button **Capture Again**. Evaluate the image on the screen: if necessary, retake it before continuing.

![Facial capture step](https://content.gitbook.com/content/7Bx0xNdsdGHpCZ20yxbn/blobs/aYkbQd4QK1VFqDp606GG/images/etapa2-captura-facial.png)

The button **Next** is only enabled after a successful capture. Use **Previous** to return to the biographical data step.
{% endstep %}

{% step %}

### Fingerprints

The scanner requests the fingerprints in sequence. Place the finger indicated by the interface and wait for capture — the system automatically advances to the next finger.

![Fingerprint step](https://content.gitbook.com/content/7Bx0xNdsdGHpCZ20yxbn/blobs/dWrys1SwyIwNrOozdVxO/images/etapa3-impressoes-digitais.png)

The capture mode is configurable by installation. The reference image above shows a four-finger collection. Fingers that have not yet been captured are highlighted.

![Fingers pending capture](https://content.gitbook.com/content/7Bx0xNdsdGHpCZ20yxbn/blobs/7VjdAFpOLXeacwyVGyIZ/images/etapa3-dedos-pendentes.png)

If a finger cannot be captured (amputation, injury), follow the extension interface to mark the reason (capture can be skipped through the device-specific options when enabled by configuration).

The message *"Fingerprints captured successfully"* appears when the set is complete.
{% endstep %}

{% step %}

### Signature

Ask the individual to sign on the signature pad. The signature is displayed on the screen in real time.

* If the signature is unsuitable, use **Capture Again**.
* When the signature is captured, *"Signature captured successfully"*.
* If the individual is unable to sign (illiterate, injury, infant, etc.), select the option **Does not sign**. The system will display *"Signature not captured"* and will allow you to continue even without a signature.
  {% endstep %}

{% step %}

### Review the entered data

Displays a summary of all entered data:

* **Biographical data** filled in.
* **Biometric data** — for each modality (Face, Fingerprints, Signature), indicates whether it was *Captured* or *Not captured*, with preview when available.

Read carefully. To correct something, use **Previous** and go back to the previous steps — the data already captured is preserved.

When everything is correct, click **Submit**. During submission, both buttons are disabled.

![Review step](https://content.gitbook.com/content/7Bx0xNdsdGHpCZ20yxbn/blobs/GdRD3FnDHhnYlw8cSpcQ/images/etapa5-revisao.png)
{% endstep %}
{% endstepper %}

{% hint style="info" %}
The set of steps and required fields may vary according to the deployment configuration. In some installations, GBS Identity operates in **fast** mode (a slim form with minimal capture — by default, only fingerprints) instead of the **full** mode described above. In any case, the system only allows you to move forward when the step requirements have been met.
{% endhint %}

### Cancel record

![Record form header](https://content.gitbook.com/content/7Bx0xNdsdGHpCZ20yxbn/blobs/dBaT0CsRcWs85Q4ax7bT/images/cabecalho-formulario.png)

* **Cancel** (top right): aborts the record and discards everything that has been captured (with confirmation).

{% hint style="warning" %}
**Warning: this action cannot be undone.** When canceling or leaving an in-progress record, all captured biographical and biometric data (face photo, fingerprints, signature, and any other associated information) are permanently deleted. The system always displays a confirmation modal before discarding data.
{% endhint %}

### After submission

![Screen after record submission](https://content.gitbook.com/content/7Bx0xNdsdGHpCZ20yxbn/blobs/f2oXGeAaqAlYg55ASXvD/images/apos-envio.png)

The behavior depends on the connection state at the time of submission:

| Scenario                | What happens                                                                    | Message                                                                                     |
| ----------------------- | ------------------------------------------------------------------------------- | ------------------------------------------------------------------------------------------- |
| Online + ABIS available | The record is sent immediately. You are redirected to the record details page.  | *"Record submitted successfully"*                                                           |
| Offline                 | The record is saved on the device (IndexedDB) and added to the send queue.      | *"You are offline. Record saved locally and will be sent when the connection is restored."* |
| Online send failure     | The record is saved locally and the system will try to resend it automatically. | *"Send failed. Record saved locally and will be resent automatically."*                     |

## 8. Offline mode and Submission Log

GBS Identity was designed to work without a connection. You can start and complete a record normally when offline — it will be stored in the browser and sent automatically as soon as there is a connection and the server is available.

### 8.1 How the system identifies offline status

* The browser lost access to the internet, or
* The identification server (ABIS) is down.

In both cases, the header will show yellow/red status indication and some pages will display specific banners.

### 8.2 Ready to Send

When there are records waiting to be sent, a button **Ready to Send** appears in the header. Clicking opens the page **Submission Log**.

![Ready to Send button](https://content.gitbook.com/content/7Bx0xNdsdGHpCZ20yxbn/blobs/T0DW0jLg9Rb1FTtOhG3q/images/botao-prontos-para-enviar.png)

### 8.3 Submission Log page

Lists all locally stored records pending submission. For each one, the following are displayed:

* Name (or *"Unnamed Record"* when not filled in).
* Date of last update.
* Indicator **Sending** in real time during synchronization.
* Indicator **Error during sending attempt** when a failure occurs.

When the system is online, ABIS responds and there are pending records, the button appears **Resend records** at the top of the page. Click it to force a new sending attempt.

When the queue is empty, the page displays *"No pending records to send"*.

### 8.4 Offline server banner

On the page **Records** and in **Metrics**, when ABIS is unavailable, an orange banner appears:

{% hint style="warning" %}
**OFFLINE MODE — Offline Research Server.** The ABIS research server is currently unavailable. Only records ready to send are visible. Online records cannot be accessed until the connection to the server is restored.
{% endhint %}

## 9. List and search records

Accessed via the item **Records** in the sidebar. The page has three sections: filters, paginated list, and pagination.

![Record listing](https://content.gitbook.com/content/7Bx0xNdsdGHpCZ20yxbn/blobs/lYxn0q5vR8dQijai9IeT/images/lista-registros.png)

### 9.1 Filters

| Filter                    | How it works                                                                                              |
| ------------------------- | --------------------------------------------------------------------------------------------------------- |
| **Search by...**          | Text field with a key type selector. The value is automatically formatted according to the selected type. |
| **Start date / End date** | Filters by the record collection start date. You can use only one of the two.                             |

Buttons **Search** (applies the filters) and **Clear** (resets all filters and repeats the search). Pressing the `Enter` key in the search field also triggers the search.

The applied filters **are preserved** when navigating to other pages. When you return to Records, your search remains displayed.

### 9.2 Record list

Each item displays:

* Name (or *"Unknown record"*, when there is no "Name").
* Identifying documents.
* Number of candidates found (after the biometric search is complete).
* **Status badge** indicating the processing state:

| Status               | Meaning                                                                           |
| -------------------- | --------------------------------------------------------------------------------- |
| `Registering`        | The individual is being registered in ABIS.                                       |
| `Registered`         | The enrollment has been completed.                                                |
| `Failed to register` | The enrollment failed.                                                            |
| `Processing`         | The 1:N biometric search was requested and is in progress.                        |
| `Search Failed`      | The biometric search failed on the server.                                        |
| `Completed`          | Processing has been completed — the candidates (if any) are available for review. |

Each item has the button **View** to open the details (Section 10).

### 9.3 Pagination

At the bottom of the list, page controls (first, previous, next, last) and selection of the number of records per page (10, 15, or 50). Pagination only appears when there are online results.

## 10. Record details and biometric search

Accessed via the button **View** on each record or via the recent activity card on the dashboard. The page has three sections:

![Record details page](https://content.gitbook.com/content/7Bx0xNdsdGHpCZ20yxbn/blobs/MPEE1H8WlDKQRz6zzRUG/images/detalhes-registro.png)

### 10.1 Current Record

![Current record card](https://content.gitbook.com/content/7Bx0xNdsdGHpCZ20yxbn/blobs/Z0m176WAPPb4UuzmXCLT/images/registro-atual.png)

Card at the top, showing all data from the newly created record:

* Captured facial image.
* Biographical data.
* Current status (badge).
* Indication whether any finger has an anomaly (amputated, injured, etc.).

As long as the record status is *Registering*, *Registered* or *Search Requested*, this page automatically updates every 5 seconds.

### 10.2 Biometric search result

![Biometric search result](https://content.gitbook.com/content/7Bx0xNdsdGHpCZ20yxbn/blobs/QS4pdjuCFw4uhw8QgMVi/images/resultado-pesquisa.png)

Right below the current record, it shows the search result:

* **"X profiles found"** — total number of candidates in the upper-right corner of the section.
* **"No profiles found"** — when the search returned no candidates.

When there are no candidates, the system explains:

{% hint style="info" %}
**No matching profiles:** The biometric search in the database returned no matching profile.
{% endhint %}

### 10.3 Candidate card

Each candidate found is displayed in a card with:

* **Candidate facial image**.
* **Record type**: `CIVIL` (from the civil database) or `RECORD` (another *encounter* already existing in Identity).
* **Biographical data** summarized.
* **Creation date** of the candidate record.
* **PGUID / TGUID** — unique identifiers of the candidate.
* Button **View Details**.

To close the detailed information, click **Hide Details**.

### 10.4 Key verification alerts

In addition to the 1:N biometric search, GBS Identity performs a **1:1 verification** for each key provided. These alerts appear as highlighted banners:

{% hint style="warning" %}
**Warning:** The *(key)* provided is already registered in a profile in the database that **has no biometric match** with the record. This may indicate document fraud — investigate before accepting the record.
{% endhint %}

{% hint style="info" %}
**Warning:** The *(key)* provided **is not registered in the database**. The provided document is not in the system.
{% endhint %}

### 10.5 Back

The button **Back** at the top returns to the source page: **Records** (if you came from the listing) or **Home** (if you came from the dashboard).

## 11. Complete registration

When a record was created in **fast** mode (biometrics only) and the biometric search returned no candidates, the operator can **complete the registration** by adding more biometrics and biographical data. This improves the quality of the record stored in ABIS for future searches.

### 11.1 When the button appears

On the record details page, when no candidate is found and the record is of the quick type (and has not yet been completed), the button appears **Complete Registration**.

If the record already has candidates or has already been completed, the button does not appear and the system displays *"Record cannot be completed"* if you try to open the completion URL manually.

### 11.2 Completion flow

When clicking **Complete Registration**, the same five-step form used for a new registration opens, already **pre-filled** with the biographical and biometric data from the original record. Add the missing information and proceed to the review step.

Upon submission, the system updates the record in ABIS and returns the new search result. You are redirected back to the details page.

If you cancel or try to leave with pending changes, the system displays a modal:

{% hint style="warning" %}
**Discard Changes — Warning: Your changes will be lost.** Canceling will discard all changes made to this record, including newly captured biographical and biometric data.
{% endhint %}

## 12. Metrics

Accessed via the item **Metrics** in the sidebar (permissioned users only). Displays three aggregated usage indicators for a selected period.

### 12.1 Period filter

At the top of the page, choose **Start Date** and **End Date**. Available shortcuts: **Today**, **Last Month**, **This Year**. The button **Search** is only enabled when both dates are filled in.

After searching, a summary line is displayed (e.g., *"Selected period: 01/05/2026 - 27/05/2026 (27 days)"*) and the three metric cards.

### 12.2 Indicators displayed

![Metrics panel](https://content.gitbook.com/content/7Bx0xNdsdGHpCZ20yxbn/blobs/6C6xVXC99r2VMUK15k89/images/metricas.png)

| Indicator                      | What it measures                                                                                                  |
| ------------------------------ | ----------------------------------------------------------------------------------------------------------------- |
| **Total Offline Captures**     | How many records were captured without a connection (offline) during the period. Useful for tracking field usage. |
| **Total Sent Records**         | How many records were actually sent to ABIS during the period.                                                    |
| **Records without candidates** | How many records, when submitted to biometric search, had no corresponding candidate.                             |

### 12.3 Service unavailability

This page requires ABIS to be online. If you access it while offline, you will be redirected to the home page with the message *"The identification service is currently not accessible for metrics consultation"*.

## 13. Messages, warnings, and troubleshooting

### 13.1 Common toasts and notifications

| Message                                                                                   | Meaning / Action                                                                               |
| ----------------------------------------------------------------------------------------- | ---------------------------------------------------------------------------------------------- |
| *Record sent successfully*                                                                | Online sending completed. Record available for consultation.                                   |
| *You are offline. Record saved locally and will be sent when the connection is restored.* | The record is safe on the device. Check the header for signs that the connection has returned. |
| *Pending record synchronized successfully*                                                | A record that was in the queue was sent.                                                       |
| *Failed to synchronize record. We will try again.*                                        | Temporary error. The system will automatically retry.                                          |
| *Record format error. Contact support*                                                    | The local record is corrupted or in an invalid format. Contact support with the record ID.     |
| *Failed to load records. Try again.*                                                      | Temporary error in the server call. Reload the page or search again.                           |
| *New record page unavailable while the devices are inactive*                              | Check the System Diagnostics page (Section 5).                                                 |
| *Record not found. A new record will be created.*                                         | The ID in the URL does not exist. The system created a blank record.                           |
| *Failed to initialize record. Try again.*                                                 | Error preparing the new record screen. Reopen the page.                                        |

### 13.2 Application update (PWA)

When a new version is detected, a floating notice appears **"New version available — Refresh the page to use the latest app version"**, with the buttons:

* **Update now** — reloads the app to the new version.
* **Later** — postpones the reminder.
* **Dismiss** — closes the notice (it will be shown again later).

### 13.3 Diagnostics: what to do if something is red

| Symptom                        | Probable cause                                                         | What to do                                                                                            |
| ------------------------------ | ---------------------------------------------------------------------- | ----------------------------------------------------------------------------------------------------- |
| Capture System in red.         | Live Capture Extension not installed or disabled.                      | Install the extension (link on the Diagnostics page). Restart the browser.                            |
| Facial Device in red.          | Camera not connected or permission denied.                             | Check the USB cable. Grant camera permission in the browser address bar.                              |
| Fingerprint Scanner in red.    | Driver missing, device in use by another program, or USB disconnected. | Reconnect the USB. Close other capture software. Install the indicated driver.                        |
| Signature Pad in red.          | Same family of causes as the scanner.                                  | Reconnect and test.                                                                                   |
| Identification Service in red. | ABIS down or VPN/firewall blocking.                                    | Keep working offline — records will be sent when the service is back. Contact support if it persists. |
| Internet connection in red.    | No network (Wi-Fi/Ethernet) or router down.                            | Check the device network. Keep working offline — GBS Identity works without internet.                 |

## 14. Sign out and switch sessions

Click the **avatar** in the upper-right corner and select **Log out**. The system ends the session on the identity provider and returns you to the login screen. Unsent local data (pending records) remains stored on the device and will be synchronized in the next session of the same user.

{% hint style="info" %}
**Important:** local data is linked to the user identifier. When switching users on the same device, each user will see only their own pending records.
{% endhint %}

***

## Glossary

<table data-search="false"><thead><tr><th>Term</th><th>Definition</th></tr></thead><tbody><tr><td><strong>Record</strong> (encounter)</td><td>Set of biographical and biometric data collected from an individual in a session.</td></tr><tr><td><strong>ABIS</strong></td><td>Automated Biometric Identification System — service that stores, indexes, and searches biometrics.</td></tr><tr><td><strong>Enrollment</strong> (registration)</td><td>Process of inserting the individual into ABIS so they become part of future searches.</td></tr><tr><td><strong>Verification (1:1)</strong></td><td>Comparison of the individual's documents against a specific record in the database, identified by the same key.</td></tr><tr><td><strong>Search (1:N)</strong></td><td>Biometric comparison of the individual against the entire database, returning matching candidates.</td></tr><tr><td><strong>Profile found</strong></td><td>Existing record in the database that has biometric correspondence (face, fingerprint, or signature) with the newly created record.</td></tr><tr><td><strong>CIVIL</strong></td><td>Candidate source: coming from the civil database (citizen database).</td></tr><tr><td><strong>RECORD</strong></td><td>Candidate source: coming from other encounters already existing in Identity.</td></tr><tr><td><strong>PGUID / TGUID</strong></td><td>Unique identifiers assigned by ABIS to the individual (PGUID) and to the biometric record (TGUID).</td></tr><tr><td><strong>Live Capture Extension</strong></td><td>Browser extension that allows the web application to access biometric devices.</td></tr><tr><td><strong>Live Capture Connector</strong></td><td>Operating system application that acts as a bridge between the browser extension and the device drivers.</td></tr><tr><td><strong>PWA</strong></td><td>Progressive Web App — a web application model that can be installed as a native app and work offline.</td></tr></tbody></table>


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.griaule.com/gbs/en/applications/gbs-identity.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.