Skip to main content
This upgrade impacts how Glean accesses Slack data. Review the Limitations and functionality differences section before proceeding.
Use this guide if you already have the Slack connector configured in Glean using a central Slack app. For more information, see Identify data source type.

Current configuration

Your Slack connector is currently configured with the shared, legacy central Slack app managed by Glean. In this configuration:
  • The connector was originally set up using a central Slack app, not a customer‑owned custom app.
  • Real‑time search (RTS) is not yet wired through the dedicated RTS Slack app for this connector.

New configuration after the upgrade

After you complete this upgrade:
  • You keep the existing Slack connector that was set up with the central Slack app, and
  • You add a new customer‑owned custom Slack app and authorize the RTS Slack app, both linked to the same Slack instance.
From the new Additional App setup tab on the existing Slack connector, you:
  • Create a new custom Slack app that points to your legacy Slack instance.
  • Copy the app’s Client ID, Client secret, and Signing secret into Glean.
  • Authorize Glean to access your Slack workspace using this custom app and the RTS Slack app.
The end state is:
  • The original connector continues to exist, but
  • RTS and the new custom Slack app are configured through the Additional App setup flow, and future behavior is driven by this combined setup rather than by the central app alone.

Slack central app upgrade steps

1. Confirm your current configuration

Before starting, verify that you are currently using the Slack Central setup:
  1. In the Glean Admin Console, navigate to Data Sources.
  2. Search for your existing Slack data source and click Setup.
  3. Review the configuration fields:
    • Central App Setup: You should see a basic configuration with Slack domain and Slack ID fields.
    • Custom Instance: If you see additional fields like Client Secret or App-Level Token**, you are on a Slack custom instance and should refer to the Custom App upgrade guide instead.

2. Reauthorize your Slack Central App

You must refresh the connection for your existing Central app before adding RTS:
  1. On the existing Slack data source setup page, click Authorize.
  2. Click Allow on the Slack authorization screen.
  3. Wait for the success message confirming your Slack Central app is successfully reauthorized.

3. Add the Slack Real-Time Search (RTS) data source

  1. Click Add Data Source in the Glean Admin Console.
  2. Search for Slack and select Slack Real-Time Search.

4. Configure Slack identifiers

Locate and enter the specific identifiers for your Slack workspace:
  1. Slack domain: Log into Slack on the web. Click your workspace name dropdown to find your domain (e.g., companyname.slack.com). Copy and paste the domain into the Glean dashboard.
  2. Slack team ID: Locate the Team ID directly from the URL in your browser while logged into Slack (it typically starts with T). Copy and paste this into the Glean dashboard.

5. Authorize and finalize

  1. Click Authorize on the Slack RTS setup page.
  2. Once authorized, click Start Sync.
  3. Wait for the synchronization process to complete. You have now successfully migrated to Slack RTS.

Limitations and functionality differences

  • Applies only to central‑app Slack connectors: This upgrade flow is intended for Slack connectors that were originally created using the central Slack app. Other setups, such as those that already use a custom Slack app or the Slack Enterprise Grid / Discovery API connector, have different upgrade paths and are not covered here.
  • Additional App setup does not configure Gleanbot on the new app: The Additional App setup tab guides admins through creating a new custom Slack app, entering its Client ID, Client secret, and Signing secret, and authorizing Glean to access Slack. This flow creates a custom Slack app “without Gleanbot,” so it does not enable Gleanbot or other bot‑driven interactive features on the new app.