> ## Documentation Index
> Fetch the complete documentation index at: https://docs.libratech.ai/llms.txt
> Use this file to discover all available pages before exploring further.
# Search
> Find anything across your projects and Databases. One shortcut, everywhere in the app.
A single keyboard shortcut from anywhere in Libra opens a search bar. Whatever you type is matched against everything you have access to — chats, documents, folders, Reviews, Discoveries, Assistants, Workflows and templates — across every project you can open.
⌘ + K
Ctrl + K
Closing the panel clears every filter *value*, so each Cmd+K starts from a clean slate — and a chip you added just for that search goes with it. To keep a filter in the bar for good, open the gear menu at the bottom of the panel and tick it under **Default filters**.
## What Search looks through
Search has two match modes over the same material. By **name** — the default — it matches titles and file names. **Search document content** instead matches passages *inside* your documents, by meaning rather than by the words you typed.
| Type | What the default mode matches |
| --------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| **Chats** | The chat's name. When message-text search is switched on for your workspace, queries of three characters or more also match the text of the messages inside it. |
| **Documents** | The file name and the title you gave the document. To match text *inside* a document, use **Search document content**. |
| **Folders** | Folder names. |
| **Reviews** | Review names. |
| **Discoveries** | Discovery names. |
| **Assistants** | Assistant names. |
| **Workflows** | Workflow names. |
| **Templates** | Playbook names and Discovery template names. |
Assistants and templates that exist in several languages are listed under the title for your interface language.
Search covers **every project you can open**, including the ones shared with you; nothing from a project you aren't a member of appears. If your team has [Databases](/en/features/databases/basics), they are searched alongside projects: the first filter chip reads **Location**, its default is **Everywhere**, and its dropdown lists your projects and your databases as two groups. Without Databases the same chip reads **Project** and defaults to **All projects**.
Playbooks, Discovery templates, Assistants and Workflows don't belong to a project, so they drop out of the results as soon as you narrow **Location** to a single project.
## How to use Search
Press Cmd+K (Mac) or Ctrl+K (Windows), or click **Search all projects** at the top of the sidebar. The same shortcut closes the panel again.
Before you type, the panel lists **Recents** — the chats, documents, folders, Reviews, Discoveries and templates you touched most recently. If what you wanted is right there, click it.
Above them sits an **Actions** group — **Ask Libra** to open a new chat, **New Discovery** to start a Discovery, and **Add Document** to open **Project files** and upload — each tagged **In \** when you're working inside one. **New Discovery** needs edit rights on the project you're in; **Add Document** needs them too, unless you're outside a project. The group disappears as soon as you type or set a filter, and comes back under **Try instead** when a query finds nothing.
Results appear under a **Results** heading with a running count. Each row shows the type icon, the name, and the project — or the database — it belongs to.
If the query comes back with almost nothing, a second, typo-tolerant pass runs automatically; you'll see *Looking for similar matches…* while it does.
The filter icon to the right of the input opens the filter bar, and leaves it open until you close it again. It starts with **Location** (**Project**, if your team has no Databases), **Type** and **Created by**; **Add filter** brings in **Date**, **Practice area**, **Tags** and **Favorite**, and **Clear all filters** resets everything at once.
**Type** narrows to **Chats**, **Documents**, **Folders**, **Reviews**, **Discoveries**, **Workflows**, **Assistants** or **Templates** — the last covering Playbooks and Discovery templates together. **Created by** set to **You** is the quickest way back to your own work. **Favorite** narrows to your starred work: chats, Assistants, Workflows, Playbooks and Discovery templates are matched on their own star, while documents and folders — which carry no star of their own — come through whenever the project they sit in is starred. A Review or Discovery needs both: its own star *and* a starred project.
Click any result, or use the arrow keys and press Enter. Libra goes to the right place: the chat, the document, the Review screen, the Discovery results. If the result lives in a project other than the one you're in, Libra asks **Switch project?** first, so you don't lose your place by accident.
Documents open in the preview panel when they're PDFs. Anything else — a Word file, a spreadsheet, an email export — can't be previewed, so Libra falls back to **Show in sidebar**: it opens **Project files** and highlights the document in the tree with a brief pulse.
## Searching inside a document's text
Some questions don't match a document by name; they match a *passage*. **Search document content** finds those passages by meaning, even when your phrasing doesn't match the words on the page.
Asking *"clauses about who pays for legal fees"* finds passages about indemnification, prevailing-party costs, and attorney fee awards — even when none of those words appear in your query.
The **Search document content** button appears beside **Ask Libra**, to the right of the input, once your query is three or more characters long.
The results list is replaced by a **Document content** section with its own count. Each row carries the document's title, the project or database it sits in, a page badge such as *p.12*, and a two-line snippet with your match highlighted. There is no relevance score on the row — the ranking is the order.
Editing the query while you're in content mode shows *Press Enter to refresh document search.* The previous results stay on screen until you submit, so a mistyped character doesn't wipe them.
Clicking a result opens the document at the cited page with the snippet highlighted, exactly like following a citation. The content button stays highlighted while the mode is active — click it again (its tooltip now reads **Show title results**) to return to matching by name.
Content search doesn't sweep everything at once: it works through your most recently updated projects — and, if you have them, your databases — and stops there, so a file in a matter you haven't touched in months can fall outside it. When it has had to leave projects out, the panel says how many it searched under the **Document content** heading. If one document matters, set **Location** to its project or database first; a scoped search always reaches it.
If your team has **Databases**, the content toggle is independent of the filter bar: every filter you have set stays active as you switch between name results and content results. Without Databases, content search can only honour the **Project** filter — so if **Type**, **Created by**, **Date**, **Practice area**, **Tags** or **Favorite** is set, the button is disabled and its tooltip names the filters to remove.
## Acting on a result without opening it
Most rows carry a **⋯** button at the end — in the Recents list as much as in a set of results — opening the same actions you'd find on the item itself, so you can rename, share or clear something out without leaving the panel. A row you have no action on carries no menu.
You only see the actions you're allowed to perform. Libra asks the server what you can do with each result, so renaming, sharing, archiving and deleting drop out of the menu for anything you only have view access to.
| Result | Actions |
| ------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------- |
| **Chats** | **Open**, **Edit**, **Share**, **Move to project**, **Duplicate**, **Archive**, **Delete** |
| **Documents** | **Show in sidebar**, **Add to chat**, **Download**, **Rename**, **Delete**. A document that lives in a database offers **Open** only. |
| **Folders** | **Show in sidebar**, **Rename** |
| **Reviews** and **Discoveries** | **Open**, **Rename**, **Delete** |
| **Assistants** and **Workflows** | **Open**, **Edit**, **Share**, **Delete** |
| **Playbooks** and Discovery templates | **Open**, **Share**, **Delete** |
## Ask Libra — turn the query into a chat
Sometimes the answer isn't in your workspace yet. **Ask Libra** sits to the right of the input from the first character you type, and it's also the first entry in the **Actions** group before you type anything.
*Ask Libra* doesn't just paste your query into a new chat — it sends it. The chat starts in the active project, so switch projects first if you want it scoped elsewhere.
Type the question — *"how to challenge an arbitration clause under Swiss law"*, say, which is far too specific to match an existing chat or document — and click **Ask Libra**. Libra closes the panel, opens a new chat, and submits your question as the first prompt, so the answer is already being written by the time the Chat view settles.
## Searching inside one database
A database has its own search box in its browser, labelled **Search files**, and it works on the same two modes as Cmd+K — but scoped to that database alone. **Search document content** searches the passages in its files, and **Ask Libra** opens a new chat with the database attached as a source and your question already sent. See [Databases](/en/features/databases/basics).
## Tips for getting better results
Searching for *"Lopez"* still finds *"López"*, and German, Italian, French, or Spanish accents (*perché*, *caffè*, *über*, *straße*) match against content stored without them. You don't need the full title either — any part of a name matches.
When a query returns five results or fewer, Libra follows up with a typo-tolerant pass over the same material, so a transposed letter or a half-remembered spelling normally still surfaces the item.
When you're hunting for a *concept* — *"clauses about indemnification"*, *"passages discussing termination for cause"* — switch to **Search document content**. Default matching is the right tool when you know the document's name or are looking for a chat you had.
If you know which project or database the result is in, set **Location** to it. Everything else drops away, and content search gets a much smaller corpus to work through.
Setting **Created by** to **You** is useful when you're trying to find your own draft or notes among many shared resources.
Query, results and filter values are all cleared when the panel closes, so nothing you searched for last time leaks into the next one. The bar comes back with **Location**, **Type** and **Created by**, plus whatever you ticked under **Default filters** in the gear menu at the bottom of the panel — that choice survives closing the browser. A chip you added with **Add filter** for a single search is not kept.
## Keyboard shortcuts inside Search
| Action | Mac | Windows / Linux |
| --------------------------- | --------------------------------------------- | ------------------------------------------------ |
| Open search | ⌘ + K | Ctrl + K |
| Move between results | ↑ / ↓ | ↑ / ↓ |
| Open the highlighted result | Enter | Enter |
| Close search | Esc or ⌘ + K | Esc or Ctrl + K |
## Next steps
Browse your projects directly.
Reusable document sets that Search treats as Locations.
The panel Search hands you back to.
Find a reusable template.