> 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/user-documentation/finding-your-information/general-search.md).

# General Search

This lesson will show you how to use the search function in AgileCase.

### Searching AgileCase

You can search your AgileCase system using the "Search Practice" text box beside your username. Entering text in this box will search the whole system for a matching result.

### Search results

Once you have carried out a search you will be taken to the search results page. This will list your results and give you the option to choose their order and filter by entity type.

### Filtering a search

You can also filter the criteria for your search using the sidebar. This allows you to select what entities will show up in the search and lets you specify a practice area, case type, and case status to be searched.

### Filtering a search (continued)

You can also filter your searches by client, label, user created by, and user last edited by. You can also select a date range to refine your search to a particular time period.


---

# 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/user-documentation/finding-your-information/general-search.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.