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.

What you can add fields to

• Assets
• People

Common field types

• text
• number
• date
• checkbox
• dropdown

Typical configuration options

When creating a field, you can choose:

• Entity (asset or person)
• Field type
• Whether the field is required
• Whether the field should be searchable or unique where supported
• Category scoping for asset fields when you only need the field on certain asset types

Good use cases

• cost center
• serial number from another system
• warranty provider
• department-specific ownership fields
• compliance or inspection metadata 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)