> ## Documentation Index > Fetch the complete documentation index at: https://docs.jelou.ai/llms.txt > Use this file to discover all available pages before exploring further. # Document analysis level > Choose how strict the document verification is and which parameters each level checks. The **document analysis level** controls how strict the review of the ID document is. Think of airport security: more checks mean more security, but more people left waiting. The same applies here: the more validations are active, the higher the strictness and the lower the approval rate. A lower level doesn't remove security: it changes the depth of the analysis. You configure it in the **Document verification** tab of the [Biometrics Webview configuration](/en/guides/integraciones/identidad/biometrics-configuration). If you need help defining the best configuration for your document, use the [Onboarding with Jelou CLI](/en/guides/integraciones/identidad/biometrics-onboarding). ## Available levels | Level | What it includes | Use case | | - | - | - | | **Standard** | Document type and origin, expiry date, and physical security elements. All three validations must pass. | Recommended level: it balances anti-fraud protection and conversion for each country. | | **Advanced** | Everything in Standard, plus the document's overall result. Optionally, automatic reading zone, data consistency, and photo quality. | High-risk flows or regulated sectors. Works best with modern, easy-to-read documents. | | **Custom** | Type and expiry always on, plus the combination of parameters you choose. | Companies with specific business rules. Configured only by the person assigned by the client and requires prior coordination with Jelou. | We recommend the **Standard** level. It strikes the best balance between anti-fraud protection and conversion for each country. The **document type and origin** and **expiry date** variables cannot be disabled under any selected level. ## What each field is This is how each element looks on a document. The numbers in the image match the table. Illustration of a sample ID document with eight numbered elements: header, holder data, expiry date, hologram, automatic reading zone, holder photo, captured photo, and full document | No. | Document element | What it is | Field that uses it | | - | - | - | - | | 1 | Header | Indicates the document type and the country. | Document type and origin | | 2 | Holder data | Names, number, and dates. They are read with OCR, an automatic text reading. | Data consistency | | 3 | Expiry date | Defines whether it is valid. | Expiry date | | 4 | Hologram and patterns | Physical protections of the document. | Physical security elements | | 5 | Automatic reading zone | Strip with the encoded data, such as the MRZ. | Automatic reading zone | | 6 | Holder photo | Compared with the selfie. | Facial comparison | | 7 | Captured photo | Sharpness, light, framing, and glare. | Captured photo quality | | 8 | Full document | Brings all the checks together. | Overall document result | ## What each level checks | Field in the platform | What it checks | In the image | Standard | Advanced | | - | - | - | - | - | | Document type and origin | That it is a recognized type from the correct issuing country. | 1 | Always on | Always on | | Expiry date | That it is within its validity period. | 3 | Always on | Always on | | Physical security elements | Holograms, chips, security codes, and background patterns. | 4 | On | On | | Overall document result | Full analysis. If any control fails, the document is rejected. | 8 | Not applicable | On | | Automatic reading zone | That the encoded data is read and consistent. Only if the document has this zone. | 5 | Not applicable | Optional | | Document data consistency | Compares what is visible (OCR) with what is encoded in the automatic zone. | 2 and 5 | Not applicable | Optional | | Captured photo quality | Sharpness, lighting, framing, and absence of glare. | 7 | Not applicable | Optional | ## Custom level With the **Custom** level you choose which parameters to enable. Document type and origin and expiry date are always on. **Before disabling the Physical security elements parameter** This parameter verifies holograms, chips, security codes, and background patterns, and is a barrier against high-resolution printouts or photocopies. Disabling it lowers the document's security level. If you need to do it: 1. Ask Jelou to assign the **external\_client\_biometry** role to your company, sending the email address of the person who needs it. 2. With the role enabled, log in to Brain and disable the validation. 3. The system shows a consent modal: type "I know and accept the risks" to confirm. That acceptance is logged for audit. If you need help defining the best configuration for your document, use the [Onboarding with Jelou CLI](/en/guides/integraciones/identidad/biometrics-onboarding). In populations with many old or worn documents, a stricter level increases rejections or referrals to human review ([HIL](/en/guides/integraciones/identidad/hil)). Assess the typical document quality of your user base before enabling it. ## Recommended configuration by country * Disable the **Overall document result**. * Don't leave the automatic reading zone, document data consistency, or the overall result as required. * Apply a **Custom** configuration with these parameters active: * Document type and origin. * Expiry date. * Physical security elements. * You can keep the automatic reading zone on. * If your users carry many old documents, such as the blue-background ones, disable captured photo quality. Leaving the **automatic reading zone** and **captured photo quality** disabled means the system won't require the document to have an MRZ or penalize it if the image quality isn't high. This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.