> For the complete documentation index, see [llms.txt](https://docs.kaana.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.kaana.com/product/getting-started/search-tips.md).

# Search Tips

Learn how to effectively search and find what you need in Kaana.

## Using the Search Bar

The search bar at the top of the page searches across:

* Projects
* Tasks
* Contacts
* Documents
* Organizations
* Issues

{% stepper %}
{% step %}

### Basic Search

* Click the search bar (or press `/`)
* Type your search term
* Press Enter or click Search
* Results appear organized by type
  {% endstep %}

{% step %}

### No Results Found?

* Check spelling
* Try different terms
* Use partial words
* Clear filters
* Check the correct section
* Verify you have access
  {% endstep %}
  {% endstepper %}

## Quick Results

As you type, quick results appear:

* Click a result to go directly to it
* See top matches from each category
* Press Enter for full search

## Search Techniques

### Exact Phrases

Use quotes for exact matches:

```
"project kickoff"
```

Finds items with exactly "project kickoff"

### Partial Matches

Search finds partial matches:

```
mark
```

Finds "Marketing", "Benchmark", "Mark Smith"

### Multiple Terms

Space-separated terms find items with all terms:

```
budget 2024
```

Finds items containing both "budget" and "2024"

## Filtering Results

### By Type

After searching, filter by type:

* Projects only
* Contacts only
* Documents only
* etc.

### By Date

Filter by when created or updated:

* Last 7 days
* Last 30 days
* Custom date range

### By Status

For projects and tasks:

* Active only
* Completed only
* All statuses

## Category-Specific Search

### Projects Search

Find projects by:

* Project name
* Description
* Owner name
* Tags

### Contacts Search

Find contacts by:

* Name
* Email address
* Company
* Phone number

### Documents Search

Find documents by:

* File name
* Description
* Tags
* Uploader

### Tasks Search

Find tasks by:

* Task title
* Description
* Assignee name
* Project name

## Recent Searches

Your recent searches are saved:

* Click the search bar
* See recent searches
* Click to search again

## Search History

View your complete search history:

* Access from your profile
* See what you've searched
* Quick access to past searches

## Keyboard Shortcuts

| Shortcut  | Action           |
| --------- | ---------------- |
| `/`       | Focus search bar |
| `Enter`   | Execute search   |
| `Esc`     | Close search     |
| `↑` / `↓` | Navigate results |

## Tips for Better Results

### Be Specific

More specific = better results:

* "Q4 budget review" instead of "budget"
* "John Smith Acme" instead of "John"

### Use Key Terms

Focus on unique identifiers:

* Project codes
* Client names
* Specific dates

### Check Spelling

Search requires correct spelling:

* Double-check names
* Try alternate spellings
* Use partial matches

### Use Filters

After searching:

* Narrow by type
* Filter by date
* Sort by relevance

{% hint style="warning" %}
What's Not Searched

* File contents (only file names)
* Archived items (by default)
  {% endhint %}

<details>

<summary>Did this answer your question?</summary>

😞 😐 😃

</details>


---

# 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.kaana.com/product/getting-started/search-tips.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.