Passport/ID Field
The Passport/ID field collects proof of identity. The applicant uploads a passport or an ID card, Full Fabric reads the document, records whether it is valid, and fills in the details the document proves. Staff get a verdict and a set of verified values instead of a file they have to open and check by hand.
Adding the Field
Passport/ID is a field type in the schema builder, next to File upload. It can be added to an application template (any of its tabs) and to the profile schema.
| Setting | Behaviour |
|---|---|
| Accepted documents | Passport or national ID card. The document type is detected on upload; there is nothing to configure and nothing for the applicant to choose. |
| Documents per field | One. Uploading a new document replaces the previous one and starts a new validation. |
| Accepted files | A photo, a scan or a PDF, like a File upload field. |
| Instructions | Per-locale instructions, shown to the applicant above the upload control. |
Everything else a field offers (visibility rules, required rules, role permissions, field mappings) works as for any other field. See Custom Fields.
What the Applicant Sees
The field renders as a file upload. Once the document has been validated, the proven details appear under the file as label and value rows, followed by the verdict line. The rows are read-only: the only way to change them is to upload another document. The classic application form and the new application form behave the same way.
Proven Details
Validation reads the machine-readable zone of the document and confirms it with the document's own check digits. A valid read fills in:
| Detail | Example |
|---|---|
| Surname | ERIKSSON |
| Given names | ANNA MARIA |
| Document number | L898902C3 |
| Nationality | Utopia |
| Date of birth | 12 August, 1974 |
| Sex | F |
| Expiry date | 15 April, 2012 |
| Issuing country | Utopia |
Countries are shown with their localized names. The values cannot be edited by the applicant or by staff, and they are not accepted from forms or the API: they only ever come from a document.
Validation Verdicts
Every upload is validated in the background by the Document validator, a system agent that ships with every institution. It reads the document on Full Fabric's own servers, without an AI model, so it works with AI switched off. See Automation.
| Verdict | Shown as | Proven details |
|---|---|---|
| Valid | Green check on the file, no message | Filled in |
| Expired | "This document expired on 15 April, 2012." | Kept, with a warning |
| Unrecognized | "No document was detected in this file." | Cleared |
| Invalid | "This document could not be validated.", "This file is password-protected." or "This file could not be opened." | Cleared |
| Not validated yet | "Validation pending…" | Empty until the validator runs |
An expired document is still a genuine read of a real document, so its details stay. An unrecognized or invalid one leaves the field empty and the applicant can try again.
Note: The verdict and the proven details are visible to signed-in staff wherever the application or the profile is visible: application view, profile sidebar, lists and exports.
Where Staff See It
| Surface | What is shown |
|---|---|
| Application view | The file, the proven details as a table and the verdict line, on the tab that holds the field |
| Profile sidebar, Files panel | The file with its verdict badge and a one-line summary: holder name and expiry date, for example "ERIKSSON, ANNA MARIA · expired 15 April, 2012" |
| Application lists | The upload with its verdict badge, as a column |
| Personal profile | For a Passport/ID field on the profile schema, the same upload, details and verdict on the staff member's own profile page |
Profile Field
A Passport/ID field on the profile schema receives the proven values from an application through the usual field mappings, the same way an Address field does. Identity proven on one application is then known on the profile, and a later application does not have to prove it again.
Filtering, Segments and Exports
- Application lists and segments can filter by validation status: valid, expired, unrecognized, invalid, or not validated yet.
- Lists and segments can also filter by the proven values, like any other application field.
- Exports carry the validation status and justification alongside the file, plus the proven values. Selecting the field in the column picker adds one entry and produces one column per value, as an Address field does.
Merge Tags
Letters, offers and emails can print the proven values with sub-tags of the field:
| Tag | Renders |
|---|---|
=profile.<field>.surname |
Surname; likewise given_names, document_number, sex |
=profile.<field>.nationality, =profile.<field>.issuing_country |
Localized country name |
=profile.<field>.nationality_code, =profile.<field>.issuing_country_code |
The raw code read from the document |
=profile.<field>.date_of_birth, =profile.<field>.expiry_date |
Date in the standard format, with the usual _as_yyyymmdd and _as_ddmmyyyy variants |
Application-level fields use the application tab prefix instead of profile. The letter editor's field references dialog and the email editor's tag list offer every sub-tag, so there is no need to type them by hand. A field with nothing proven yet renders blank.
Converting an Existing Upload Field
Institutions that already collect passports through a File upload field can have that field converted to Passport/ID by Full Fabric. The conversion keeps the field, its uploads and everything that references it (rules, mappings, exports, letters), and validates the documents already uploaded at a controlled pace. Applications holding more than one file on the field are listed for review instead of being guessed at.
Note: Contact Full Fabric support to request a conversion; it is not self-service.