Validation overview
Validation is managed from three pages, one per kind of thing being written:
| Page | Route | Backend call |
|---|---|---|
| Field validation | GET /admin/validation/new, POST /admin/validation |
UpdateFieldValidation, or ApplyValidationSet when a set is named |
| Reusable rule | GET /admin/validation/rules/new, POST /admin/validation/rules |
UpsertValidationRule |
| Validation set | GET /admin/validation/sets/new, POST /admin/validation/sets |
UpsertValidationSet |
All three require the struct:validation manage permission.
The distinction mirrors the backend model:
- a field validation is attached to one column (
data_key) of one table in one profile; - a reusable rule is the same validation payload under a name, with no profile or table, so several fields can share it;
- a validation set groups reusable rules in order and can be applied to a column in one call.
Validation itself runs server-side; the web pages only configure it. For the authoritative behavior see the server’s validation documentation and Table data.
The shared payload
Section titled “The shared payload”Field validations and reusable rules share the same payload, described in Field validation. Rules and sets are described in Reusable rules and Validation sets.