> For the complete documentation index, see [llms.txt](https://hub.equipme.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://hub.equipme.io/dokumentation/organization/additional-information.md).

# Further information (custom fields)

Maintain your own custom fields (further information) on locations, employees and groups.

With **"Further information"** you store any additional details on **locations**, **employees** and **groups**, e.g. location code, building, ERP number or contract number.

**Where:** the **"Further information"** tab on the respective detail page and the "Further information" column in the lists.

## Maintaining entries

* **"Add"** → "Create entry" dialog:
  * **"Key"**: name of the field (required, unique per object, max. 150 characters)
  * **"Value"**: content (max. 500 characters)
* You can edit values directly in the table, and you can delete entries.

Anyone who may edit an object may also edit its custom fields.

## Filling custom fields automatically

* **Location import:** Additional columns in the import file are saved as custom fields.
* **Employee import:** "Further information" column.
* **HR sync:** via the fields `eq_metadata_1`, `eq_metadata_2` etc. (see [HR sync](/dokumentation/organization/hr-sync.md#additional-fields-from-the-hr-system)).
* **Automation:** Workflows can read and write custom fields.

{% hint style="info" %}
Additional information on **services** (e.g. serial number), on the other hand, is maintained as **attributes** on the [service detail page](/dokumentation/assets/inventory/asset-details.md#features). To show it as an additional column in the inventory, set it up under [Portal settings → "Additional table columns"](/dokumentation/settings/portal-settings.md#additional-table-columns).
{% endhint %}


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

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

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://hub.equipme.io/dokumentation/organization/additional-information.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.