> 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/user-documentation/the-case-tab/case-type-editing.md).

# Case Type Editing

This lesson will show you how to change the case type and practice area of a case from the case page.

### Editing the practice area

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

{% stepper %}
{% step %}

#### Begin editing the case

Click the **Edit** button in the top-right corner of the page.
{% endstep %}

{% step %}

#### Change the practice area

Use the dropdown menu by the **Practice Area** heading to change the practice area associated with the case.
{% endstep %}

{% step %}

#### Save the new settings

Once you have selected the new practice area you want to associate with the case, click the tick button to save the new settings.
{% endstep %}
{% endstepper %}

{% hint style="warning" %}
Changing the practice area will also change any custom field groups and relationship groups that are associated with the case, and any information within these fields shall be lost upon proceeding.
{% endhint %}

### Editing the case type

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

You can edit the case type of the selected case in the same way as the practice area.

Simply use the dropdown menu and confirm your choice with the tick button.

{% hint style="warning" %}
Like changing the practice area, changing the case type will result in the loss of data from any related fields.
{% endhint %}


---

# 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/user-documentation/the-case-tab/case-type-editing.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.