> 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/creating-custom-case-types-in-agilecase.md).
# Creating Custom Case Types in AgileCase
Once you have set up a practice area, the next step is to create a custom case type that you can allocate to that practice area in order to give users a case format that fits their work. Case types are key to optimizing your workflow as they can be allocated custom fields so that all necessary data can be entered in an appropriate format.
{% stepper %}
{% step %}
## Access Case Types
Access the settings menu, then select **Case Types**.
{% endstep %}
{% step %}
## Add a custom case type
Click the **Add Case Type** icon.
{% endstep %}
{% step %}
## Name and associate the case type
Name your case type and associate it with one or more practice areas. To do this, select the relevant practice area from the menu.
Alternatively, select the appropriate case type on the **Edit** menu for that practice area.
To get the most out of your custom case type, you can add a case plan. These allow you to set a timeline for each case type and ensure that it is followed by all users.
{% endstep %}
{% step %}
## Control access using groups
You can also govern which groups can access the case type. Groups allow you to divide the users in your system into teams that can be allocated to case types and practice areas in order to ensure that staff can only access the relevant information.
{% endstep %}
{% step %}
## Create a group
Select the relevant tab from the settings menu, then click the **Add Group** icon.
After naming your group, you can select which users are to be part of the group.
{% endstep %}
{% endstepper %}
Once a group is associated with a case type, only users in that group can see the case type. This allows you to compartmentalise your system so every user cannot access all of the information.
For a more detailed account of how to set up a case type, please refer to the documentation topic [here](/administrator-documentation/case-type-settings/creating-a-new-case-type.md). For information on setting up groups, you can find the topic [here](/administrator-documentation/user-administration-settings/creating-groups-in-agilecase.md).
With a practice area and corresponding case type set up, the next stage will take a look at the relationship system within a single case in order to manage contacts and streamline communications between relevant parties.
---
# 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/creating-custom-case-types-in-agilecase.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.