> 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-a-practice-area.md).

# Creating a Practice Area

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

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

Practice areas are used to divide your business into manageable chunks on AgileCase. Practice areas can be associated with groups and case types, allowing you to allocate the right people and the right information to each practice area.

For example, a legal practice may have areas such as conveyancing, employment law, and criminal law. Using practice areas efficiently allows you to create a system in which all of the relevant information will be readily available for each user.

To create a new practice area, begin by selecting the appropriate option on the “settings” page.

There are several default practice areas available. However, these can be deleted or altered as you see fit in order to best serve your business.

{% stepper %}
{% step %}

## Add a practice area

Click the “Add Practice” icon and name your chosen area.
{% endstep %}

{% step %}

## Associate a case type

Align the practice area with the particular case type that it requires.
{% endstep %}
{% endstepper %}

Practice areas and case types are two sides of the same coin—the relationship between them is what allows you to associate a particular case format with each area of your organization.

For example, an employment case will have a very different structure to a criminal case, so different case types with unique custom field groups can be assigned to each practice area in order to optimize your workflow in both areas by eliminating unnecessary fields and information.

For a more detailed guide on setting up a practice area, please refer to the documentation topic [here](/administrator-documentation/getting-started/creating-a-practice-area.md).

In the next stage, we will examine the other side of this process by looking at setting up some custom case types and take a deeper look at the relationship between custom case types and practice areas.


---

# 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-a-practice-area.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.
