Field rules
Set validation and visibility rules and check server enforcement.
Field rules protect stored values. Browser feedback helps authors, but the server is authoritative.
Rules by field
| Rule | Supported fields |
|---|---|
| Required | All 12 field types |
| Unique | ShortText, Number, Slug, Reference, Asset, Taxonomy |
| Minimum / maximum number | Number |
| Character or word size | ShortText, LongText, Slug |
| Allow or deny regex matches | ShortText, LongText, Slug |
| Allowed values | ShortText, Number, Asset |
| Date range | DateTime |
| Image width, height, orientation | Asset; checks the selected asset file metadata |
Date range exists in the model but is not available in the current field-rule builder.
Change a rule
- Open the field in Content model and choose only rules supported by its type.
- Add a useful validation message where offered.
- Try a valid and invalid non-production value. Correct existing records before relying on a stricter rule.
- Save with
model.update; loading the definition requiresbackend.readandmodel.readwith matching scope.
Visibility and translation
isHiddenFromApi, isHiddenInAdmin, and isTranslatable are separate field settings. API-hidden fields are absent from generated delivery schema and projection. Admin visibility is not an authorization control, and current editor behavior for Admin-hidden fields is not a public security guarantee.