# Custom fields

**Custom fields** can be used optionally to add additional information to the devices, e.g. Serial Number, Battery Replacement Date, or GPS coordinates. By adding important information to a device, it helps to manage the device fleet more efficiently.

### 1. Custom fields during device creation

A **Custom Field** can be added to a device during the step of device creation. *+ Add Custom Field* needs to be selected.

![Custom fields during device creation](/files/QP2RtuU6wfDVwfUjGhu5)

An existing or a new **Custom Field** can be selected or created. Following **field types** can be chosen to define a Custom Field further:

* Number
* Text
* Date
* JSON
* GPS coordinates

![Different field types of Custom field](/files/PTUmP4bVqsX1dSLWHkqn)

{% hint style="info" %}
Custom fields can be also displayed as columns on the **Asset Inventory Overview**. 

Via filter on the **Asset Inventory Overview,** Custom fields can be searched to view all Assets with the same Custom field description.
{% endhint %}

### 2. Adding custom fields in custom fields management section

A **custom field** can be added or edited in the Custom Fields management in the workspace settings. Already existing custom fields can be viewed and modified. A new custom field can be created or a set of custom fields can be imported using bulk import (see the template below). For *Text* and *Number* field types it is possible to add, edit or remove select options that should be available as possible custom fields values. 

<figure><img src="/files/nKqRCG1HyDmIWyQpzgQU" alt=""><figcaption><p>Bulk import of custom fields</p></figcaption></figure>

A bulk import template for custom fields can be downloaded here:

{% file src="/files/1gORs1gTXOiRFhDjLPJo" %}


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://docs.akenza.io/akenza.io/get-started/your-organization/how-to-use-custom-fields-on-akenza.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.