> For the complete documentation index, see [llms.txt](https://help.rhythms.ai/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.rhythms.ai/getting-started/basics/using-quick-search-in-rhythms.md).

# Using Quick Search in Rhythms

## Introduction

Finding the right OKRs, documents, check-ins, and notes quickly becomes essential as your organization scales. Rhythms' search functionality helps you navigate through objectives, key results, initiatives, and documents with ease — saving valuable time and keeping teams aligned.

## Accessing Quick Search

### Step 1: Open search

On the top left of the Rhythms screen, you'll find a search icon. This universal search works across your OKR content and your documents.

### Step 2: Begin your search

Click the search field and start typing your query (minimum 2 characters). Results appear as you type, helping you find relevant content instantly.

## Search Capabilities

### Filter by content type

Below the search bar, filter tabs let you narrow your results by content type:

* **All**: Shows all matching content, including goals and documents together in one relevance-ranked list
* **Objectives**: Displays only matching objectives
* **Key Results**: Shows only matching key results
* **Initiatives**: Displays only matching initiatives
* **Documents**: Shows only matching documents

### Searching documents

Global search now finds documents, not just goals. Use the **Documents** tab to search across every doc in your Library, or stay on **All** to see goals and documents together. Search matches both document titles and body content, so if you've been navigating the Library tree to find a doc, you can search for any keyword from its title or body instead.

### Search features

Rhythms search understands what you're looking for:

* Search for specific metrics like "500K users" to find related key results
* Search by team names to find all associated OKRs
* Search by time periods like "Q2 2025" to find objectives for specific quarters
* Search by owner names to find their assigned items
* Search for any keyword in a document's title or body to jump straight to that doc

## Search Tips and Best Practices

### Use specific keywords

Rather than searching broad terms, use specific keywords that appear in your OKRs or documents:

* Search for metrics like "active" to find "monthly active users"
* Search for project names or specific initiatives
* Search for technical terms unique to your objectives
* Search for a distinctive phrase from a document to find it quickly

### Search check-in notes

Search extends beyond titles to include check-in notes, so you can find historical context and updates on specific topics.

## FAQ

**How do I open search quickly?** Use the keyboard shortcut Cmd/Ctrl + K, or click the search icon at the top left.

**Can I search the text inside a document, not just its title?** Yes. Document search matches both titles and body content, so a keyword from anywhere in a doc will surface it.

**How do I see only documents in my results?** Select the Documents tab below the search bar to filter results to documents only.

**Does search still cover goals and check-ins?** Yes. The All tab shows goals and documents together, and search continues to include objectives, key results, initiatives, and check-in notes.

## Conclusion

Quick search helps you navigate your Rhythms workspace efficiently. Whether you're looking for specific metrics, team objectives, a document buried in your Library, or historical check-ins, search provides instant access to what you need.

## Related Articles

* [Navigating the Rhythms OKR Platform: A Comprehensive Overview](/goals-and-okrs/okr-foundations-and-structure/find-your-way-around-rhythms.md)
* [Sharing Documents](/documents-and-library/share-a-document.md)
* [Using Views to Organize and Monitor OKRs](/goals-and-okrs/monitoring-and-reports/create-and-share-okr-views.md)


---

# 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 following URL with the `ask` and `goal` query parameters:

```
GET https://help.rhythms.ai/getting-started/basics/using-quick-search-in-rhythms.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `build a script that syncs our docs to a CMS` lets GitBook tailor the answer to that use case.

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.
