> 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-a-new-case-type.md).

# Creating a new Case Type

This lesson will show you how to create a custom case type in AgileCase.

{% stepper %}
{% step %}

### Access case types

<figure><img src="/files/zzMl5xgggj4rNarBJ3ul" alt="" width="177"><figcaption></figcaption></figure>

One of the key aspects of case management in AgileCase is the relationship between practice areas, case types and case plans. How you relate these elements will shape the structure of the system and allow you to customize AgileCase to work for your business in your specialist field.

In brief, a practice area is a department within your business, for example "General Work" or "Consultancy". A case type governs the content of a case. For example a case type "Consulting" will contain the fields relevant to a consultancy project.

Finally the case plan sets out a timeline consisting of preset milestones so you can ensure each case stays on track- naturally, different case types will require different case plans. The element we will cover here is custom case types.

To access custom case types, click the "Case Types" button in the settings menu under "Case Type Settings".
{% endstep %}

{% step %}

### Add a new case type

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

You will be directed to the case types page. Here you can see the default case type "General Work" and the practice areas in which it is available. If a case type has a specified case plan and is limited to be visible only to certain groups, these will also be shown here.

To create a new custom case type, click the "Add Case Type" button.
{% endstep %}

{% step %}

### Enter the case type details

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

Now you can define your custom case type by entering a name and short description. Selecting a case plan lets you choose the set of milestone that will be used in each case of this type, you can read more about these here.

You can also select which practices this case type will be available to, this allows you to limit your custom case types to only the relevant practice area.

You can read more about practice areas [here](/administrator-documentation/case-type-settings/creating-a-new-practice-area.md).

Finally you can select which groups the case type will be available to. Only users in these groups will be able to use the custom case type. For more about groups, click [here](/administrator-documentation/user-administration-settings/creating-groups-in-agilecase.md).

After you have finished entering the case type details, click "Save Case Type" to create the new custom case type.
{% endstep %}

{% step %}

### Your custom case type has been created

<figure><img src="/files/7n2aJAClKcpncXPkYICO" alt=""><figcaption></figcaption></figure>

Your new case type should now be visible along with the default "General Work" setting. You can use the dropdown menu opposite to edit and delete case types, you can also edit custom fields appearance, which you can find out about [here](/administrator-documentation/case-type-settings/editing-custom-fields-appearance.md).
{% 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-a-new-case-type.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.