Skip to main content
This guide is for administrators deploying or managing the Slack hybrid search connector. It explains how the hybrid connector works, what has changed from previous Slack search experiences, and what to expect for your users. For end-user search tips and guidance, see Slack hybrid search best practices.

​
What is the Slack hybrid search connector?

The Slack hybrid search connector combines two Slack connectors to deliver a unified search experience in Glean:
  1. Slack Real-Time Search (RTS) connector: Leverages Slack’s RTS API for real-time data access via federated search, using Slack’s underlying search technology and deployed via a Slack Marketplace app.
  2. Slack native connector (custom app): Glean’s existing native connector using the Data Access APIs, deployed as a customer-created custom Slack app. This connector operates in one of two modes based on your Slack app’s rate limits:
    • Enterprise graph mode (rate-limited Slack apps): Collects relevancy signals only (e.g., interactions) to build Glean’s enterprise graph. Uses low-bandwidth calls designed to stay within non-Marketplace rate limits.
    • Indexing mode (customers with written rate-limit exception): For customers with written rate-limit exceptions from Slack, the connector continues to collect full Slack data to support a full content index.
For setup instructions, see Set up the Slack hybrid connector.

​
What’s changed from the previous experience

  • Hybrid connector model: Glean now blends Slack RTS federated search with the Slack native connector so users get real-time results from Slack plus Glean’s enterprise ranking and context.
  • Mode-based native connector: The Slack native connector no longer behaves the same for every customer. It now runs in either enterprise graph mode (signals only, for rate-limited apps) or indexing mode (full content index, for customers with a Slack rate-limit exception).
  • End-user authorization: End users will see new Slack authorization prompts the first time RTS is enabled for them, so they can securely grant the Marketplace app access to their Slack account under the new RTS-based model.

​
End-user experience of the hybrid search connector

The hybrid connector blends results from Slack RTS and the native connector to provide a seamless search experience. When users search for Slack content in Glean, results may come from both sources:
  • RTS results: Live, real-time results fetched directly from Slack at query time. These are always up to date and permission-aware.
  • Native connector results: Depending on your configuration, these may include enterprise graph signals that improve ranking, or fully indexed Slack content for organizations with a Slack rate-limit exception.
Results from both sources are blended together in the search results page. Users will not see separate sections or labels distinguishing RTS results from native connector results. This is by design, so users get a single, unified Slack search experience. The Search and Assistant interface remains the same for users — the main difference is that they need to authenticate before they can see Slack results from RTS.

​
Hybrid connector in indexing mode

If your organization has a Slack rate-limit exception and uses the hybrid connector in indexing mode, the user experience closely resembles the previous Slack search experience:
  • Semantic and keyword search over Slack data, supporting a wide range of query patterns.
  • Ability to make multi-hop inferences using cross-app ranking signals and Glean’s enterprise graph.
  • Support for analytical, data-intensive questions.

​
Hybrid connector in enterprise graph mode

If your organization uses the hybrid connector in enterprise graph mode, set the following expectations with your users:
  • Users should include relevant context such as channel names, names of people, dates, or timeframes to help retrieve results.
  • Broad or deeply analytical queries may experience higher latency, incomplete coverage, or timeouts and partial answers.
  • Private channels and DMs rely on keyword search.
To improve results in enterprise graph mode:
  • Break up big questions into smaller, more focused prompts.
  • Use Slack mainly for context, and rely on documents, tickets, or wikis for heavy analysis where possible.
  • Retry after a short delay if a rate-limit message appears — Slack enforces back-off under load for 1–2 minutes.

​
Content coverage

Slack hybrid search supports searching across:
  • Public channel messages and threads
  • Private channel messages and threads (channels the user has access to)
  • Direct messages (DMs) and group DMs
  • Files and attachments: Files shared in Slack (PDFs, images, documents). This can be limited in enterprise graph mode.
  • Slack Canvases. This can be limited in enterprise graph mode.
  • Slack Connect channels: External Slack Connect channels can be limited in enterprise graph mode.

​
End-user authorization

Each user must individually authorize Glean to access their Slack data. Because the hybrid connector uses two separate Slack apps, users must complete authorization for both the RTS Marketplace app and the native/custom app.
  • Non-dismissible authorization banner: End users will see a Slack authorization banner in Glean that cannot be dismissed until they have fully completed all required Slack authorizations. Because the Slack hybrid connector may require dual authorization (both the RTS Marketplace app and the native/custom app), the banner may continue to appear even after a user has authorized one of the two apps. The banner is removed only after all authorization steps are complete. Remind your users to check that they have completed Slack authorization.
  • No reauthorization needed: If your users have already authorized for the RTS Marketplace app and the custom app, no additional end-user authorization is needed for the hybrid connector. They will not be prompted to reauthorize.
Users who have not yet authorized will see the authorization banner on the Glean Search or Home page. After clicking Connect Slack and completing the prompts, Slack results will appear in their searches. Users can manage their Slack connection in their Glean Settings page at any time. If users report missing Slack results:
  1. Verify that they have authorized Slack in Glean — make sure they have completed authorization for both the RTS Marketplace app and the custom app.
  2. Check that they have access to the channels or messages they are searching for.
  3. Ask them to try the same search in Slack directly to confirm the content exists.

​
Glean in Slack changes

The Glean in Slack experience will change for all users after the hybrid connector is enabled:
  • During the migration process, Glean in Slack will be temporarily unavailable for approximately 10 – 20 minutes.
  • A new Glean Marketplace app (white icon — the RTS instance) will automatically appear in the workspace or enterprise once the admin authorizes the RTS connector. Users can mention it with @Glean.
  • There will no longer be support for daily digests and proactive thread summarizations.