> 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.md).
# Case Type Settings
One of the key features of AgileCase is the ability to create custom cases. Custom cases let you configure the content of the cases you create, allowing you to tailor AgileCase to the specifics of your business.
Custom cases are created using the relationship between three main elements: Practice areas, Case plans and Case types.
Practice areas divide up the areas of your business. For example, "general work", "consulting" or "accountancy" could all be practice areas within your business.
Each practice area can be allocated one or more case types. Case types control the availability of custom field types which allow you to create your own fields so that data specific to the case type can be recorded in each case.
Case plans control the milestones assigned to a case in order to chart its progress. Milestones are the central events of the case type and therefore will differ depending on the different format followed by each case type.
The relationships between these three elements allows you to customize the layout of each kind of case your business requires.
This chapter will go in to detail on the processes involved in creating your own custom cases and how to optimize them for your business.
---
# 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.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.