> For the complete documentation index, see [llms.txt](https://knowledge-base.letsgetdigital.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://knowledge-base.letsgetdigital.com/the-admin-panel/settings/additional-data-fields.md).

# Custom fields

If there is a piece of information you want to add to your users and/or companies profiles then you can add these customfields in the advanced settings. This article will explain how this can be done.

## The home page <a href="#the-home-page" id="the-home-page"></a>

To find the custom fields feature within the admin panel:

1. Hover over to settings.
2. Select 'Custom fields'.

## Managing custom fields <a href="#managing-additional-profile-fields" id="managing-additional-profile-fields"></a>

### Creating a new field <a href="#creating-a-new-field" id="creating-a-new-field"></a>

There are a number of different types of fields you can create. They are:

* **Yes/No** - A tick box.
* **Numeric** - A numerical digit-only field.
* **Text** - A text character field.
* **Link** - To add an external URL link.
* **Phone Number** - A phone number field.
* **Address** - An address field.
* **Select** - Option to add multiple different options
* **Document upload** - Possibility to upload documents

***The process for adding each of these is broadly similar:***

1. Open the additional data fields home page.
2. Select the type of field you want to add from the buttons along the top (described above).

![](https://gblobscdn.gitbook.com/assets%2F-LnvOYoR6OwNZ905Jz7E%2F-LtZtp8sccVeOIvDinID%2F-Lt_PmFAVLDS6B9Su4Zi%2FNew%20field%20buttons.gif?alt=media\&token=73076358-4384-46c5-a61f-0bceb7f0eaa0)

&#x20;3\. Complete the fields as applicable (Any fields marked with a \* are mandatory). \
&#x20;4\. Click on 'Save changes'.

![](https://gblobscdn.gitbook.com/assets%2F-LnvOYoR6OwNZ905Jz7E%2F-LtZtp8sccVeOIvDinID%2F-Lt_Q01MqTjATswK6oFZ%2FMaking%20an%20additional%20field.gif?alt=media\&token=0f92da30-c36b-4d72-b58e-bca7d620729b)

{% hint style="info" %}
**Note:** Different or additional options may apply to some of the custom fields you can create, and therefore may not be represented in the video example above.
{% endhint %}

### Editing and deleting new fields <a href="#editing-and-deleting-new-fields" id="editing-and-deleting-new-fields"></a>

Each new field has two icons to its right (Under actions):

​![](https://772941315-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-M5LNCGpK5lyymcFZU4V%2Fuploads%2FJD62sQqZTTUwmPWJMOFV%2FEdit%20icon.png?alt=media\&token=d3a3a6c9-7b57-460f-8fff-b752fd944afc)- Edit icon: Click here to make adjustments similar to when you're creating a new field. \
![](https://772941315-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-M5LNCGpK5lyymcFZU4V%2Fuploads%2FOsfGTAZVFv0QkwsotkAR%2FRemove%20icon.png?alt=media\&token=3fdae07a-22e4-4ab4-a649-33dbd9d03134) - Delete icon: Click here to remove the custom field altogether.

{% hint style="info" %}
**Note:** Edits to your new field will apply immediately for any new users/companies etc, however, old users remain unaffected until edited, even if the new field is now mandatory.
{% endhint %}

## The result <a href="#the-end-result" id="the-end-result"></a>

![](https://772941315-files.gitbook.io/~/files/v0/b/gitbook-legacy-files/o/assets%2F-M5LNCGpK5lyymcFZU4V%2F-Mcnm2h3lDiJl1-u2uNT%2F-McnmGJSkZX4uXZzX5D_%2Fimage.png?alt=media\&token=21e022e0-eebb-451f-a42c-e9a4af10fc01)

​


---

# 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://knowledge-base.letsgetdigital.com/the-admin-panel/settings/additional-data-fields.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.
