Custom Fields
Custom fields let you capture organization-specific attributes for Assets and People.
Examples:
- Cost center
- Device spec (CPU/RAM)
- Purchase order number
- Contract end date
- Manager
Where it lives
Open Configuration → Custom Fields.
Entities supported (current UI)
- Assets
- People
Field behavior (current UI)
When creating a field, you can choose:
- Entity (asset or person)
- Type: text, number, date, checkbox, or dropdown
- Optional constraints:
- mandatory
- unique
- searchable
- Optional category scoping for assets
On narrow screens, the entity and type pickers collapse to dropdowns so the admin modal stays usable on mobile.
Dropdown fields use a predefined list of values stored as plain text. The list is trimmed on save, empty entries are rejected, and duplicate values are rejected case-insensitively. Dropdown fields must have at least one option. When you edit an existing custom field, the current entity, type, and dropdown options are preselected in the modal.
Only text and number fields can be marked unique. If you switch a field to date, checkbox, or dropdown, the uniqueness control is hidden in the UI and rejected by the API. Checkbox fields are not mandatory, so the mandatory control is hidden when the type is checkbox.
Checkbox fields are stored as boolean values and render as checkboxes in item and person forms. In list and detail views, they display as Yes or No.
When a checkbox field is added later, older assets and people default that field to No in detail views and false in forms.
Only text and number fields can be marked searchable, so the searchable control is hidden for other field types. Searchable custom fields are included in global search and in list search across the entity views that support search.
Dropdown fields render as a single-select control in asset and person forms. Existing saved values stay visible when an option is removed from the definition, but new saves must use one of the current options.
Where custom fields show up
- In create/edit forms (based on Layout configuration)
- In list views, when enabled in Layouts
- In CSV import mapping (you can map columns to custom fields)
- In QR label builder (custom asset fields can be printed on labels)