Skip to main content

​
Who this guide is for

Use this guide if:
  • Your organization uses a Slack Enterprise Grid connector based on the Discovery API.
  • You already have a custom Glean Slack app installed in your Enterprise Grid organization.
  • You need to update that app and enable Slack Real‑Time Search (RTS) for Enterprise Grid.

​
Current vs new configuration

​
Current configuration

In the current setup:
  • Your Enterprise Grid connector uses Slack’s Discovery API.
  • Glean uses a custom Slack app installed in your Enterprise Grid organization.
  • A central Slack app is also associated with your instance; the main difference is that your organization has added a custom app on top of that.

​
New configuration after the upgrade

After you complete this upgrade:
  • Your existing custom Slack app is updated with a new manifest:
    • The app name and bot display name change to Glean Enterprise Graph.
    • Slash commands (such as /glean) are removed.
    • Interactivity is disabled.
    • Additional bot scopes are granted: channels:manage, channels:write.invites, groups:write, groups:write.invites, im:write, mpim:write.
  • You authorize the Slack RTS app for Enterprise Grid via the slackRtsEnterprise self‑serve page.
  • The manifest used in self‑serve is specific to your deployment.
You continue to use the Enterprise Grid Discovery API connector, but RTS and the updated app manifest now control how Glean connects to Slack.

​
Upgrade steps

​
1. Collect Slack Enterprise account details

  1. Make sure you are a Slack admin (with permissions to install and manage apps in your Enterprise Grid organization).
  2. Open Slack on the web at https://app.slack.com/client.
  3. In the top‑left, click your organization name and note the Slack Enterprise domain, which appears in the format:
    • <domain>.enterprise.slack.com
  4. From the same browser session, note the URL of the page you are on. It has the form:
    • https://app.slack.com/client/E12345678/C12345678
  5. Copy the enterprise ID from this URL (the part that starts with E…). You will paste this into Glean as the enterprise ID during RTS setup.

​
2. Update your existing custom Slack app manifest

If your Enterprise Grid organization already has a custom Glean Slack app installed:
  1. On the Slack RTS setup page in Glean click Show setup instructions.
  2. Locate the section providing the Slack app manifest and copy the code block.
  3. In a new browser tab, go to the Slack app admin panel and open the existing custom Slack app that your Slack data source is currently using (typically named Glean).
  4. Navigate to App Manifest in the left sidebar.
  5. Paste the new manifest from Glean, overwriting the old one, and click Save Changes.
  6. Click Install App, then click Reinstall to Your Workspace.
  7. Click Allow to confirm the updated permission scopes.
  8. Once successful, go back to the Glean Admin console.
This ensures the updated app does not conflict with other Glean Slack apps that use the same name and slash commands, and that it has the required bot scopes for Enterprise Grid RTS.

​
3. Authorize Glean to access your Slack Enterprise Grid instance

  1. In Glean, open the Slack RTS Enterprise self‑serve page (the slackRtsEnterprise app page in the Admin Console).
  2. When prompted, click Authorize and follow the generated Slack link.
  3. Complete the authorization flow in Slack.
  4. When authorization succeeds, the RTS Enterprise connection is set up; no further actions are required in this guide.

​
Limitations and functionality differences

  • Applies only to Enterprise Grid with an existing custom Glean app: This guide assumes your Enterprise Grid connector already uses a custom Glean Slack app. If your Enterprise Grid connector uses the Discovery API and does not have a custom Glean app, this flow is not supported in self‑serve, and Glean provides separate, one‑off documentation for those customers.
  • No change to the underlying Discovery API connector: You are not asked to replace your existing Enterprise Grid Discovery API connector with a new Slack native connector. Only the custom app manifest and RTS Enterprise configuration are updated.
  • Per‑deployment manifest: The manifest used in the RTS Enterprise self‑serve experience is specific to each deployment. Do not reuse a manifest from another customer or environment; always copy the manifest provided in your own RTS Enterprise setup page.