> ## Documentation Index
> Fetch the complete documentation index at: https://docs.korint.io/llms.txt
> Use this file to discover all available pages before exploring further.

# Custom fields

> Learn how custom fields adapt core entities to your product.

## Custom fields

Each policy, asset, and customer has a list of custom fields which is configured at a product level, making it easy to adapt the three core entities to any insurance product's needs.

### Custom field attributes

* name
* type: string, free text, number, enumeration, date
* Business requirements
  * whether it is required to quote the policy, to sign the policy, or not required at all
  * whether its modification is allowed during the contract
  * whether its modification during the contract should require a new quote or a new signature
* Validation rules such as maximum length, minimum and maximum values.

### Voice input (speech-to-text)

Free-text custom fields can offer **voice input**: next to the text area, a microphone button lets the user dictate their answer and have it transcribed into the field as they speak. This is convenient on mobile and for longer free-text entries such as a claim description.

<Note>
  Speech-to-text is enabled per product and relies on the browser granting microphone access. Where it is not configured — or the browser denies the microphone — the field simply falls back to normal typing, so no information is ever lost.
</Note>

***

***Example 1: B2B car insurance***

* Policy custom fields: killing questions results
* Asset custom fields: car value, fiscal power, energy
* Customer custom fields: siret, address, number of employees, ceo email

You could configure this product's custom fields as such:

* the asset's fiscal power and energy are compulsory for quote calculation
* the asset's fiscal power and energy can only be modified in a mid term agreement with a new quote and signature
* the asset's car value is not required for quote, but because it appears in the contract document it is required for signature of the policy
* the asset's car value can be modified in a mid term agreement with only a new signature
* the customer's ceo email can be modified at any time

***Example 2: B2C home insurance***

* Policy custom fields: documents are validated by broker
* Asset custom fields: address, size, type (House or apartment)
* Customer custom fields: first name, last name, monthly salary

You could configure this product's custom fields as such:

* the asset's size and type are required for quoting
* the asset's size and type can only be modified in a mid term agreement with a new quote and signature
* the asset's address is required for the initial signing, but afterwards can be modified at any time
* the customer's first name and last name can be modified in a mid term agreement with a new contract signature

***

Once configured for a product, Korint will use these custom fields for various operations such as quoting, billing, and reports.