Skip to content

Documentation

Custom Fields

Add your own attributes, such as building, department or cost centre, to every asset record.

Overview

Custom fields extend every asset record with the context your team needs, such as a building, a department, an asset tag or a cost centre. You define each field once on Admin → Custom Fields, and it appears in the Custom Fields card on the Overview tab of every asset’s detail page, where people with assets:write fill in its value. Managing field definitions needs admin:manage.

Screen tour

  1. Create field: opens the New field panel.
  2. Field count: how many custom fields your tenant has, for example 2 fields.
  3. Type: the kind of value the field stores: Text, Number, Date, Boolean or Select. Hover the badge for a description of the type.
  4. Required: Required means every asset must have a value. Optional means assets may leave the field blank.
  5. Options: for Select fields, the first two options, then +N for the rest. Hover to see the whole list. Other types show —.
  6. Edit and Delete: the pencil opens the Edit field panel. The bin deletes the field after you confirm.

The table also shows each field’s Name, its Sort value (the order on the asset detail page, lower values first) and when it was Created. Hover the date to see the exact time.

Before you add the first field

When your tenant has no custom fields, the page shows No custom fields yet with a set of common examples to start from: Building, Department, Asset tag, Cost centre and Owner. Click Create your first field to open the New field panel and define one of them, or a field of your own.

Create a field

  1. Click Create field (or Create your first field when the list is empty).
  2. Under Basics, enter a Name, for example Building. This is the label people see on every asset.
  3. Under Configuration, choose the Type. The panel describes each type as you choose it. See Field types.
  4. Set the Sort order. Lower values appear first on the asset detail page.
  5. For a Select field, enter the Options, one per line.
  6. Under Validation, turn on Required if every asset must have a value.
  7. Click Create field.

A confirmation such as Field “Building” created appears, and the field shows in the list and on every asset’s Custom Fields card.

If you leave Name empty, the panel shows Give the field a name so users know what it captures. and keeps your other entries.

Edit a field

  1. Name: the field label shown on every asset.
  2. Type: the kind of value the field stores. The line below it describes the selected type.
  3. Sort order: the field’s position on the asset detail page. Lower values appear first.
  4. Options: the choices of a Select field, one per line. Blank lines are ignored.
  5. Required: when on, every asset must have a value. The text beside the switch says Every asset must have a value. or Assets may leave this field blank.
  6. Update field: saves your changes. Cancel, the close button or Esc closes the panel without saving.
  1. Click the pencil icon (Edit field) on the field’s row.
  2. Change the Name, Type, Sort order, Options or Required setting.
  3. Click Update field.

A confirmation such as Field “Department” updated appears. Asset detail pages show the change the next time they load. To change the choices of a Select field, edit the Options list: add a line for each new option and remove the lines you no longer need.

Delete a field

  1. Delete field: permanently removes the field and its values. Click Cancel to keep it.
  1. Click the bin icon (Delete field) on the field’s row.
  2. Read the dialog, for example Delete “Cost centre”?. It explains that this permanently removes the field definition and its values from every asset, and that This action cannot be undone.
  3. Click Delete field.

A confirmation such as Field “Cost centre” deleted appears.

Field types

TypeStoresValue on the asset
TextA single line of text: building names, tags or short notes.Any text.
NumberA numeric value such as a count, cost or measurement.A number, for example 42 or 19.99.
DateA calendar date, stored without a time of day.A date in the form YYYY-MM-DD, for example 2026-10-13. A full RFC 3339 timestamp is also accepted.
BooleanA yes-or-no value.true or false.
SelectOne choice from a list of options you define.Exactly one of the field’s Options.

DeviceQuest checks each value against the field’s type when someone saves it on an asset, and rejects a value that doesn’t fit, such as text in a Number field or a choice that isn’t in a Select field’s Options.

Required fields

When a field is Required, the asset’s Custom Fields card marks it Required, and assets that have no value for it show a notice such as 1 required field is missing — add a value below. An empty value is rejected for a required field.

Fields

FieldDescriptionRules
NameThe label shown on every asset, for example Department.Required. Up to 255 characters. Leading and trailing spaces are removed.
TypeText, Number, Date, Boolean or Select.Required. Default Text.
Sort orderPosition on the asset detail page.A whole number. Default 0. Lower values appear first.
OptionsThe choices of a Select field.Shown for Select only. One option per line; blank lines and surrounding spaces are ignored.
RequiredWhether every asset must have a value.Off by default.

Audit trail

Creating, updating and deleting a field is recorded in the audit log as custom_field.created, custom_field.updated and custom_field.deleted. Setting a value on an asset is recorded as custom_field.value_set. See Audit log.

Keyboard shortcuts

KeyAction
EscClose the New field or Edit field panel without saving.
Tab / Shift+TabMove between the panel’s controls. Focus stays inside the open panel.