Skip to main content
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

1

Connect at least one knowledge provider and sync content.

See Knowledge overview for provider setup.
2

To include Jira issues, connect Jira and complete user authorization where Flow prompts for it.

3

Configure Jira or web search options in product settings if they are available for your deployment.

​
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. 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.