> For the complete documentation index, see [llms.txt](https://help.tahua.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.tahua.io/product-news/2026/readme/primary-verifier-select-field-designation.md).

# Applicant Verifier Select field designation

## Problem

A Formnflow form template can contain multiple Verifier Select fields — for example, one where the applicant chooses their verifier and a separate one where staff record a verifier for an individual team member. Previously, every Verifier Select field triggered `assign_verifier!` when its value changed, so any field could silently overwrite the funding application's verifier.

## How it works

A new boolean column, `primary_verifier_select`, is added to each Verifier Select field. Only the field flagged as the primary verifier select drives `assign_verifier!`; all others store their value normally without side effects.

**Default behaviour on creation:**

* The first Verifier Select field added to a template is automatically designated as the primary one (`primary_verifier_select: true`).
* Every subsequent Verifier Select field defaults to `false`.

**Mutual exclusion:**

* Enabling `primary_verifier_select` on one field automatically disables it on all other Verifier Select fields in the same template, ensuring exactly one field controls verifier assignment at any time.

## UI changes

In the form builder, a checkbox labelled **"Applicant verifier select"** appears in the field context bar whenever a Verifier Select field is focused. Checking it designates that field as the primary verifier select; unchecking designates it as a secondary field.

## Data migration

Existing templates require a one-off data migration (see `DATA_MIGRATIONS.md`) to mark the earliest Verifier Select field per template as the primary one.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://help.tahua.io/product-news/2026/readme/primary-verifier-select-field-designation.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.