> 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/editing-case-type-tabs.md).

# Editing Case Type Tabs

This lesson will show you how to configure Custom Field Case Type Tabs in order to customize the tab layout, order and configuration of your Custom Field Groups within a Case setting.

{% stepper %}
{% step %}

## Select "Edit Case Type Tabs" on the case types page

<figure><img src="/files/tyUjfT6tuhy7T4RnX8B4" alt=""><figcaption></figcaption></figure>

When you open the dropdown menu opposite a case type on the case types page you will see an option "Edit Case Type Tabs". This allows you to configure the tab layout of your Custom Field Groups for the Case Type chosen.

In order to begin doing this, click the "Edit Case Type Tabs" option.
{% endstep %}

{% step %}

## "Details" Default Tab

Initially, when entering the "Edit Case Type Tabs" option for the first time, all Custom Field Groups associated with the Case Type will appear under the default "Details" tab as shown below.

<figure><img src="/files/6iQs4I0qXmp3dEy9JW4u" alt=""><figcaption></figcaption></figure>

Using the up and down ordering arrows alongside each option you have the ability to change the order in which your Custom Field Groups are shown under the Details Tab within a case.

For example, if you were to use this option to move the "Price" Custom Field Group to the bottom of this list, the case view for the Details tab would look like this, with the Price tab last in the order.

<figure><img src="/files/PjFw6e0g7w99IpjZY6Yw" alt=""><figcaption></figcaption></figure>
{% endstep %}

{% step %}

## Create a new Tab

Clicking "Add new Tab" will cause a new, blank tab to be created below the current Default Tab.

<figure><img src="/files/uDYZoM4fwIiXGjjpk7pD" alt=""><figcaption></figcaption></figure>

All new tabs are added with a name "New Tab", "New Tab 1" etc.
{% endstep %}

{% step %}

## Rename a Tab

To rename a newly added or pre-existing tab, click on the name on the tab which is colored in blue. This will open this dialog.

<figure><img src="/files/YVwm1rZYbv6oSza5w7oR" alt=""><figcaption></figcaption></figure>

Simply change the name of the tab and click "Save".

{% hint style="info" %}
The Details tab cannot have its name changed.
{% endhint %}
{% endstep %}

{% step %}

## Add Custom Field Groups to a tab

To position Custom Field Groups on a new tab simply use the up and down ordering arrows alongside each Custom Field Group to position the Custom Field Group in the new tab.

<figure><img src="/files/ZfBWcWT4OjJg7QdRKCZ7" alt=""><figcaption></figcaption></figure>

In this example, clicking the down arrow on the "Price" Custom Field Group places it onto the "Renamed New Tab" tab.
{% endstep %}

{% step %}

## Delete a tab

To delete a pre-existing tab, click on the name on the tab which is colored in blue. This will open this dialog.

<figure><img src="/files/YVwm1rZYbv6oSza5w7oR" alt=""><figcaption></figcaption></figure>

Click the "Delete" button and the selected Tab will be deleted.
{% 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/editing-case-type-tabs.md?ask=<question>&goal=<endgoal>
```

`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.