> For the complete documentation index, see [llms.txt](https://docs.agilecase.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.agilecase.com/administrator-documentation/case-type-settings/creating-basic-contact-custom-fields-person-or-company.md).
# Creating Basic Contact Custom Fields (Person or Company)
This lesson will show you how to create basic types of contact custom fields in AgileCase.
{% stepper %}
{% step %}
### Access contact custom fields
Just like in cases, it is possible to create custom fields for your contacts in AgileCase. Contact custom fields allow you to specify additional information to be entered about your contacts, letting you tailor the system to the needs of your business.
To begin creating contact custom fields, click the "Contact" button on the settings menu under "Case Type Settings".
{% endstep %}
{% step %}
### Add a custom field group
On the contact custom fields page, click "Add Custom Field Group" to begin creating your own custom field group. Field groups that you have already created will be listed here so they can be edited.
{% endstep %}
{% step %}
### Fill in the custom field group details
After clicking "Add Custom Field Group" you will be able to fill out the field group details.
First choose a name for the field group and enter a description. Next select what contacts this field will be available for; you can choose from contacts listed as a person or a business as well as contacts in a certain case type or contacts with a certain label. "Person" and "Business" contact custom fields follow the same basic formula whilst the other two are more complex and can be read about in later lessons.
After you have finished filling in the group details, click "Save Group" to continue.
{% endstep %}
{% step %}
### Set group permissions
After creating a custom field group you must set the group permissions. This allows you to choose which groups can view or edit this custom field group. To do this, click on the group under "Available Groups" then use the appropriate arrow to put it in the "View & Edit Permissions" or "View Only Permissions" box.
{% endstep %}
{% step %}
### Begin adding custom fields
Once you have set group permissions you can begin to add custom fields. To do this click the "Add Custom Field" tab and select the type of field you want to create from the dropdown menu.
To learn about the different field types available, use the lesson [here](/administrator-documentation/types-of-custom-field.md).
In this example, use an internal user search field, so click the "Internal User Search" button to proceed. There are also options to toggle group labels which you can read about here, and table controls which are covered in this lesson.
{% endstep %}
{% step %}
### Fill in the field details
Now fill in the details of the custom field. The label governs the title of the field and the placeholder allows you to add phantom placeholder text to help guide users.
The help text function allows you to write a prompt on how the field should be used. Once you are happy with your custom field click "Save Field" to create the custom field.
{% endstep %}
{% step %}
### Save the custom field group
Once you have created a custom field it will be listed at the bottom of the page. To edit or delete custom fields, use the (1) dropdown menu opposite and select the appropriate option.
Once you have created all the custom fields you need, click (2) "Save Changes" to save the custom field group and continue.
{% endstep %}
{% step %}
### View your custom fields
Your custom fields will now be visible under the "Details" tab on the contacts page. You can now begin entering the necessary information; once you have finished, use the "Save Changes" button to finalize your input.
{% endstep %}
{% endstepper %}
---
# 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 current page URL with the `ask` query parameter, and the optional `goal` query parameter:
```
GET https://docs.agilecase.com/administrator-documentation/case-type-settings/creating-basic-contact-custom-fields-person-or-company.md?ask=&goal=
```
`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.
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.