Setting up Slack as a Source

By connecting Slack, you can capture valuable context, streamline knowledge creation, and ensure important updates aren’t lost in message threads. Learn how to set up the integration, search for Slack messages in Guru, and empower your team to turn conversations into trusted knowledge.

❗️

Important

Setting up Slack as a Source is different from connecting Guru to _answer questions in Slack. You can learn more about connecting Knowledge Agents to Slack here.

Use these directions to connect Slack to source information to then answer questions.

👥

Access Required

*Guru Access: You need to be an Admin, Source Creator, or relevant custom role to set up Sources

Slack Access: You'll need your Slack credentials in order to authorize access with Guru.

If you want to set up your permissions in Guru you will not need to be an Admin in Slack.

If you want to inherit your team's permissions from Slack you'll need to be an Admin in Slack.

If you are connecting a private Slack channel as a Source you must be a Slack Admin.

Note: Since this video was released, several improvements have been made. As a result, some features may look different in your current view of the Guru web app.


Setting Up Slack as a Source

  1. Navigate to Manage > Sources.
  2. Select Slack from the icon menu.
  3. If you've already enabled the Guru integration, you'll see your Slack workspace listed. If you have not yet connected Guru and Slack, you can authorize this by choosing I want to connect a different Slack workspace.
  4. Next you'll need to connect Guru to specific channels in Slack. Invite the Guru app to channels you want to use as a source. In Slack, click the channel name and select the Integrations tab followed by Add apps. Hit the refresh button below to update the channel list.
  5. Next, choose who will have access to this Slack channel as a source in Guru. If you want to set up permissions to content in Guru, specify which Guru Groups should have access to the content once synced. Otherwise, if you choose "inherit permissions" - Knowledge Agents will respect the permissions from the source application.
    1. If you want to set up your permissions in Guru you will not need to be an Admin in Slack.
    2. If you want to inherit your team's permissions from Slack you'll need to be an Admin in Slack.
  6. Admins have the option of adding a Source Owner for each Source. Source Owners can add Viewers or other Owners, and delete the Source.
  7. An Owner can be added during this initial setup stage, or later by clicking manage access for that Source.
  8. Guru will send a confirmation email when the initial sync is complete. This will also be indicated in the web app when you see the Sync status change from "Initializing" to "Synced."

Objects synced from Slack

All content within selected channels from the beginning of time - including bot messages, except for Guru bot messages.


Permissions

When setting up Slack as a source you can either establish permissions in Guru, or inherit them from Slack directly.

  • Inherited Permissions
    • See above the level of access needed to inherit permissions. If the authenticating user selects to inherit permissions from Slack, they will first define the scope of content that will be synced based on what they have access to, and others access within that will be respected. Guru recommends authenticating with a service user to ensure that the desired content is synced in.
  • Setting up Permissions in Guru
    • You can also permissions that content in Guru. Learn more here. If someone is not provided with access in Guru to this source, they will not see Slack results in searches or when chatting with Guru.

Frequently Asked Questions about setting up Slack

How frequently does the Slack source sync?

Slack channels are indexed in near-real time. As messages are posted in a Slack channel, they are then sent to Guru for indexing.

What does the "Record" count indicate once you set up Slack as a source?

The "Record" count for Slack as a source indicates the number of threads synced, not the number of messages. This sync is continuous, however, so it is expected that this number would change. That is why "N/A" applies to the Sync Status field for this object.