> For the complete documentation index, see [llms.txt](https://docs.labii.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.labii.com/user-guide/navbar/search/global-search.md).

# Global search

## Overview

Global Search helps you find information across the entire workspace from one place. Instead of opening each table or project separately, you can enter a keyword once and review matching results in grouped categories.

Search results are grouped into:

* **Tables**
* **Projects**
* **Records**

Any category without matches is hidden automatically.

## How to use

{% stepper %}
{% step %}
Click **Search** from the navbar.
{% endstep %}

{% step %}
Enter one or more keywords in the search panel.
{% endstep %}

{% step %}
Review results shown automatically under **Tables**, **Projects**, and **Records**.
{% endstep %}
{% endstepper %}

{% hint style="info" %}
Use specific terms such as sample IDs, project names, or unique record text to narrow results faster.
{% endhint %}

<figure><img src="/files/Efjw6ZAQWhK7eReE45sJ" alt=""><figcaption></figcaption></figure>


---

# 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.labii.com/user-guide/navbar/search/global-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.