> 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-case-custom-fields.md).
# Creating Case Custom Fields
This lesson will show you how to create custom fields for a case type in AgileCase.
{% stepper %}
{% step %}
## Access case custom fields
Custom fields are central to managing your business processes through AgileCase. As the name suggests, custom fields allow you to create your own fields that will be visible on the case page. This lets you tailor the system to your industry and the unique needs of your business.
To get started, access case custom fields by clicking the "Case" button under "Case Type Settings" in the settings menu.
{% endstep %}
{% step %}
## Add a custom field group
Click "Add Custom Field Group" at the top of the page.
All case custom field groups that you create will be listed on this page and can be accessed for editing through the dropdown menu.
{% endstep %}
{% step %}
## Enter group details
Enter the name and description of your custom field group. Once you are finished, click the "Save Group" button to proceed.
{% endstep %}
{% step %}
## Edit case type availability and group permissions
Set which case types the custom field group will be available to, as well as governing group permissions concerning the custom field group.
Groups can be given permission to view and edit a field group or only to view it. To set permissions, select the group in question and click the appropriate arrow to send it to the correct box.
{% endstep %}
{% step %}
## Add custom fields
With group permissions set, click the "Add Custom Field" button and select the appropriate field type from the dropdown menu.
To see a breakdown of the different field types available, click [her](/administrator-documentation/types-of-custom-field.md)e.
In this example, use a basic text box field. Click the "Text Box" button on the dropdown menu 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 custom field details
Enter the details of your custom field.
Alongside a field name and character limit, it is possible to set a default value for the field, placeholder text that will illustrate what to do, and help text that can be triggered by clicking the small :info: button beside the field title.
You can also designate fields as required, which makes filling them in mandatory for a case. Once you have finished entering your custom field details, click "Save Field" to create it.
{% endstep %}
{% step %}
## Save your custom field group
Once you have finished creating your custom fields, you will see them listed at the bottom of the page, along with a corresponding dropdown menu that allows you to edit or delete them.
When you are happy with your custom fields, click "Save Changes" to save your custom field group.
{% endstep %}
{% step %}
## View your custom fields
With your custom field group complete, you can now view your custom fields in the appropriate case type under the "Details" tab.
{% 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-case-custom-fields.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.