> For the complete documentation index, see [llms.txt](https://gitbook.com/docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://gitbook.com/docs/create-content/searching-your-content/quick-find.md).
# Search & Quick find
Search and navigate your documentation fast with quick find
GitBook’s **Quick find** palette lets you search for content in your current organization, and jump to pages fast.
### Use Quick find
****You can open the **Quick find** palette by hitting the **Quick find** button at the top of the sidebar or by pressing **⌘ + K** on Mac or **Ctrl + K** on PC.
### Search results
Results from the section you're currently in appear at the top, followed by results from elsewhere in your organization.
To search another organization, switch organizations first using the switcher at the top of the sidebar.
{% hint style="info" %}
We do not currently support the ability to prioritize certain content in Quick find results.
{% endhint %}
### Permissions
**Quick find** is compliant with your team’s permission settings, meaning that users will only be able to search the content they have permission to access.
### Content indexing
We index your content by grouping it into sections. Sections are denoted using H1, H2 or H3 Headings, with the content that follows them forming part of a section.
Each result shows the first three lines of information below the section header. If your section is too big, your keyword match may not appear in the preview — but don’t worry, quick find still found a match!
---
# 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 by asking a question.
Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:
```
GET https://gitbook.com/docs/create-content/searching-your-content/quick-find.md?ask=&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 `automate deployments from our CI pipeline` 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.
