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

# Search

> Search synced knowledge people can already access, plus optional Jira and web results.

Flow search includes content synced from your knowledge sources. When enabled, it can also include connected Jira issues and web results.

## Capabilities

* Search across synced knowledge content
* Team-scoped source filtering for team views
* Jira issue search when Jira is connected
* Optional web search where available

## Configuration

| UI step | Required | Purpose |
| - | - | - |
| Knowledge sources | For Flow knowledge search | At least one synced source in the organization |
| Jira connection | For Jira search | [Jira Service Management](/integrations/ticketing/jira-service-management) connection |
| Search settings | Optional | Jira and web search options where available |

## Set up search

<Steps>
  <Step title="Connect at least one knowledge provider and sync content.">
    See [Knowledge overview](/integrations/knowledge/overview) for provider setup.
  </Step>

  <Step title="To include Jira issues, connect Jira and complete user authorization where Flow prompts for it." />

  <Step title="Configure Jira or web search options in product settings if they are available for your deployment." />
</Steps>

## Scopes and permissions

For SharePoint, SharePoint Scoped, Google Drive, Dropbox, Box, and
ServiceNow, org-wide search uses the crawled provider access list. A person can
find a file when the source already grants them access and Flow has stored that
grant. Their team does not need to connect that source. Connecting a source to
a team does not grant read.

When Flow cannot determine who the source allows, it does not grant everyone
access. Some SharePoint pages stay limited to the team that connected the
source. ServiceNow can use an explicit team or organization setting.

Team-scoped search is a filter, not a read lock. It includes sources that team
owns or later connected, then applies the same source access. Confluence Cloud
can use crawled Confluence permissions or a Flow publication audience. Notion
stays on the Flow publication audience. Both are described in
[Knowledge overview](/integrations/knowledge/overview). Organization admins
cannot bypass source access.

Jira search uses the access granted to the Jira connection. Web search does not require customers to add a separate third-party search API key.

## Related topics

* [Knowledge overview](/integrations/knowledge/overview)
* [Jira Service Management](/integrations/ticketing/jira-service-management)


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.