> ## Documentation Index
> Fetch the complete documentation index at: https://docs.selah.so/llms.txt
> Use this file to discover all available pages before exploring further.

# Search your notes, captures, and concepts in Selah

> Find anything you've written in Selah. Search covers captures, notes, and your knowledge graph, and returns results even when you use different words.

Search lets you find anything across your captures and notes in a single query. It's useful when you remember studying something but can't remember exactly what you wrote or where it landed — type a topic, a phrase, a scripture reference, or a person's name, and Selah will surface what's relevant.

## What search covers

Every search runs across:

* **Captures** — the quick thoughts and observations you've saved to your stream
* **Notes** — your structured study notes, including their titles and content
* **Knowledge graph** — your theological concepts inform the results, helping surface content connected to a topic even when it doesn't contain your exact words

## How results are found

Selah looks for matches in two ways at once: by the exact words you type, and by the meaning behind them. This means you can find a capture even if you used different language when you wrote it — for example, searching for *forgiveness* can surface a capture you wrote about *being pardoned* or *releasing a debt*.

You don't need to remember your exact phrasing. Search for how you're thinking about something now, and Selah will find what you wrote then.

## Running a search

<Steps>
  <Step title="Open Search">
    Click **Search** in the sidebar, or navigate directly to `/search`.
  </Step>

  <Step title="Type your query">
    Enter a word, phrase, scripture reference, or name in the search bar. There's no minimum length.
  </Step>

  <Step title="Submit">
    Press **Enter** or click **Search**. Results appear immediately below.
  </Step>

  <Step title="Filter by type">
    Use the **All**, **Captures**, and **Notes** tabs to narrow results to one content type.
  </Step>
</Steps>

## Reading and navigating results

Each result shows:

* A **type badge** — either *Note* or *Capture* — so you know what kind of content it is
* The **title** (for notes)
* A **snippet** of the content
* The **date** it was created

Click any result to go directly to it. Notes open in the note editor. Captures take you to the Capture stream where the item lives.

## Tips for better searches

<AccordionGroup>
  <Accordion title="Try scripture references">
    Typing a reference like *Romans 8* or *John 3:16* will find notes and captures where you discussed that passage, even if the exact text of the verse isn't in your content.
  </Accordion>

  <Accordion title="Search by theological terms">
    Terms like *justification*, *sanctification*, *covenant*, or *atonement* work well — especially if you've been building up notes around those doctrines.
  </Accordion>

  <Accordion title="Search for people's names">
    Looking for something you studied about Paul, Moses, or another biblical figure? Their name is a strong search term.
  </Accordion>

  <Accordion title="Use a few words, not a full sentence">
    A 2–4 word query often works better than a long question. *Spirit suffering Romans* will find more than *what did Paul say about suffering and the Holy Spirit*.
  </Accordion>

  <Accordion title="Try different words if nothing comes up">
    If a search returns no results, try a synonym or a different angle on the topic. The empty-results message will prompt you to do this as well.
  </Accordion>
</AccordionGroup>

<Note>
  Search does not currently cover your Prayer Board. To review your prayers, visit the [Prayer Board](/features/prayer-board) directly.
</Note>

## Related

* [Capture](/features/capture) — add content that search will find
* [Notes](/features/notes) — write structured notes that show up in search results
* [Knowledge Graph](/features/knowledge-graph) — browse concepts that inform your search
* [Companion](/features/companion) — the Companion uses a similar search internally when answering your questions