Overview
Document Field Configurations on Document Verification Templates define how extracted or Documents AI-generated insights are stored and referenced across Persona products like Workflows, Cases, and API responses.
These configurations ensure data from a Document Verification run are stored as structured data, enabling you to later automatically flag, route, or act on documents based on your specific compliance and business requirements.
Configure Document Fields Configurations
- Navigate to the Dashboard, and click on Inquiries > Templates (or Verifications > Templates).
- Find and select an Inquiry template with Document AI, or Create a new template.
- In the top right, click Configure.

- In the left navigation, click Document AI.

- Scroll down to Document Fields, or click Document Fields in the left navigation.

- To add a new document field, click the Add document field button.

- In the right toolbar, fill out the following fields:
- Name (required): A name for this field or attribute that allows you to identify what the value represents. If saving an Insight to this newly created field, it is recommended to provide a label that will help you understand how the value of this field was generated.
- Key (required): Auto-generated from the name. Used in API responses and across Persona products.
- Type (required): Choose Array, Boolean, Integer, Float or String (default). Depending on which type is picked there may be additional fields to fill out. See Type Table below.
- Redaction policy: Choose none (default) or never.
- Write policy: Choose none (default) or write once.
- Click Add button to save the new field, or Cancel to discard it.
- To remove a document click the … button then click Remove.

- Click Save on the top right.
Type Table
| Type | Description | Additional options |
|---|---|---|
| String (default) | Stores text values such as names, categories, or short responses. | - Default value (optional): Define a fallback text value. - Max length (char): Maximum 255 characters (default). |
| Array | Stores multiple values in a single field. Useful when the extraction or analysis returns a list of items. | — |
| Boolean | Stores a true/false value, often used for flags or checks. | Default value (optional): Choose true or false if you want a value applied automatically when none is detected. |
| Integer | Stores whole numbers (e.g., counts or IDs). | Default value (optional): Define a numeric fallback value. |
| Float | Stores decimal numbers (e.g., amounts or scores). | Default value (optional): Define a numeric fallback value. |
Why Document Field Configurations are important
Document Field Configurations define the data structure or schema that supports your ability to store Documents AI-driven Insights and extracted data from a Document Verification run, and the ability to action on that structured data. They’re essential for ensuring that data is consistently stored and can be referenced reliably across your Persona ecosystem.
They’re especially useful when you need to:
- Standardize data storage for Extractions and Insights across templates, Workflows, and Cases.
- Use Documents AI-generated outputs from Insight Configurations in downstream decisioning or automation.
By defining fields that capture both extracted and Documents AI-generated data, Document Field Configurations give you a unified, compliant structure for all document-based intelligence within Persona.
Access by plan
We're here to chat through your specific needs. Feel free to reach out to your Customer Success Manager or contact the Persona support team.
| Startup Program | Essential Plan | Growth Plan | Enterprise Plan | |
|---|---|---|---|---|
| Document Field Configuration | Not Available | Limited | Available | Available |