> 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-custom-field-tabs.md).
# Creating Custom Field Tabs
This lesson will show you how to create your own top-level tabs for your custom fields. This allows you to arrange your custom fields in an intuitive way, grouping related fields under the appropriate tab.
{% stepper %}
{% step %}
## Open Case Type settings
Select the **"Case Type"** option on the settings menu, then use the dropdown opposite the case type you wish to add a tab to.
On the dropdown menu, select **"Edit Case Type Tabs"** to begin creating your new tab.
{% endstep %}
{% step %}
## Add and name a new tab
On the **"Case Type Tabs"** page, generate a new tab by clicking **"Add New Tab"**.
Once a tab has been generated, click the newly generated **"New Tab"** icon to name the tab and use it to arrange your fields.
{% endstep %}
{% step %}
## Save the tab
Enter an appropriate title for the tab under which your custom fields will be listed.
Click **"Save"** to create the new tab, **"Close"** to close the window without saving the new title, or **"Delete"** to delete the new tab entirely.
{% endstep %}
{% step %}
## Move custom fields to the tab
Use the arrow icons beside your custom fields to move them under the tab of your choice.
{% endstep %}
{% endstepper %}
Your chosen custom fields will now be listed under the new tab on the case page.
---
# 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-custom-field-tabs.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.