Every field your agency needs

Fields you define

Under Instellingen → Aangepaste velden (Settings → Custom fields) you decide, per record type, what extra data you keep: a segment or a region code on the client, a risk profile on the project, a renewal date on the website. Every field has a type, so a date is a date and a choice is a choice, not a loose text box everyone fills in differently. A new module that attaches to the client can carry fields of its own right away: the screen picks the new record type up on its own, because definitions belong to a record type rather than to the product as a whole.

Eleven types, required where it counts

Pick the type that fits the data and mark a field required when a record is not complete without it. Per type you set the rules: options for a select, a minimum and maximum for numbers, a default or a line of help text on the field.

• Text, long text, number, yes/no
• Date and date-with-time
• Select and multi-select
• Email, URL and phone

The API guards the quality

Validation happens on write, not just in the screen. The server reads your definitions, checks type, required fields and allowed options, and rejects a record that does not comply with a clean error. Your data stays clean through the API or an import too, not only when someone politely uses the form.

Everywhere, in your language

One generic field view renders your definitions in the input forms, on the detail page and as a column in the list; you touch no code anywhere. Labels are stored per language, so a field reads differently in Dutch and English without becoming a second field. And because it is just data, the read tools for AI carry your custom fields, with their labels, into the answer.