> 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/deleting-a-case-type.md).
# Deleting a Case Type
This lesson will show you how to delete a custom case type.
{% stepper %}
{% step %}
### Access the case types page
To delete a custom case type, first access the case types page by clicking the icon in the settings menu under "Case Type Settings".
{% endstep %}
{% step %}
### Set as inactive
On the case types page, use the dropdown menu opposite the case type you want to delete and click "Set Inactive". This will move the case type to the recovery bin.
If you want to recovery a case type that has been set inactive, click [here](/administrator-documentation/system-settings/recovering-deleted-items.md) to find out how.
{% endstep %}
{% step %}
### Error message
When you try to delete a custom case type you may receive this error message.
This means that the case type is currently associated with a practice area and/or a case plan. In order to proceed and delete the case type, remove the case plan and practice area then repeat the steps in this lesson.
{% 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/deleting-a-case-type.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.