> 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/getting-started/configuring-your-workflow-in-agilecase-with-custom-fields.md).
# Configuring your Workflow in AgileCase with Custom Fields
Effective use of custom fields is key to managing your business practices in AgileCase. Custom fields govern the content of each case type and allow you to specify exactly how information is entered.
You can create custom fields for both cases and contacts; however, this guide focuses on case custom fields, as they are vital for configuring AgileCase.
To manage custom fields, use the **Case** option under **Custom Fields** in the settings menu.
{% stepper %}
{% step %}
## Add a custom field group
Click the **Add Custom Field Group** icon.
{% endstep %}
{% step %}
## Name and describe the group
Fill out a custom field group name and description.
{% endstep %}
{% step %}
## Configure custom fields
Add as many custom fields as needed. You can choose which case types they appear in and edit permissions for the groups you have set up.
{% endstep %}
{% endstepper %}
## Custom Field Types
AgileCase offers a wide variety of custom field types to give you complete control over your workflow. A standard suite of options, such as text fields, numeric and currency fields, and date/time pickers, allows users to enter basic information, while more complex field types allow for a variety of formatting options.
You can select the type of custom field you wish to add from the dropdown menu. A list of custom field types can be found [here](/administrator-documentation/types-of-custom-field.md).
{% hint style="info" %}
All field types can be marked as required to ensure vital information is always entered before a case can progress.
{% endhint %}
With the expansive range of custom fields that AgileCase provides, you can tailor the system to suit your own business structure and workflow. With the ability to totally customize your system, AgileCase can be adapted to any industry.
In the next part, we will show you how to effectively use the timeline feature to create a case plan and ensure each and every case is followed up in a timely manner.
---
# 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/getting-started/configuring-your-workflow-in-agilecase-with-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.