> For the complete documentation index, see [llms.txt](https://help.openloyalty.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.openloyalty.io/implementation-guide/members-and-activity/members/member-list/single-member-view/custom-fields.md).
# Custom Fields
The **Custom fields** tab allows you to view and manage additional information collected about a member. These fields extend the standard profile data (such as email, phone number, or date of birth) and let you tailor the program to specific business needs.
***
### Viewing Custom Fields
In this tab, you can see all custom fields defined at the tenant level and their current values for the selected member.
Each field includes:
* **Custom field name** – the label given during setup (e.g., *Fav stores*, *Shoe size*).
* **Value** – the member’s saved response (e.g., *California Store*, *39*).
If a field is set as *required*, it must be filled when creating or updating the member profile.
***
### Editing Custom Fields
Administrators can update custom fields by clicking **Edit custom fields**.
* When updating, you’ll see input fields corresponding to the defined custom field types (e.g., text field, dropdown list from predefined values).
* Required fields must be completed before saving changes.
* Once saved, updates appear immediately in the member’s profile.
***
To find out more about the custom fields module, please refer to this section of the User Guide:
{% content-ref url="/pages/KgmV2yRaVf9Feivip98n" %}
[Custom Fields](/implementation-guide/members-and-activity/members/custom-fields.md)
{% endcontent-ref %}
---
# 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 dynamically by asking a question.
Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:
```
GET https://help.openloyalty.io/implementation-guide/members-and-activity/members/member-list/single-member-view/custom-fields.md?ask=&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 `build a script that syncs our docs to a CMS` 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.
