Skip to main content

​
What is this migration?

Gleanbot is being migrated from the existing native Slack app (custom deployment-level app) to the Slack RTS (Real-Time Search) marketplace app (white icon). This is driven by Slack’s requirement to deprecate Discovery APIs and rate-limit custom Data Access apps by March 3, 2026. The RTS app is the compliant, long-term path.

​
What happens during migration?

​
Bot appearance changes

The old Glean bot (blue icon, custom/deployment-level app) is replaced by the new Glean marketplace app (white icon — the RTS instance). This new app will automatically appear in the workspace or enterprise once the admin authorizes the RTS connector.

​
New bot is added to existing channels

Within 1–2 hours of setting up the RTS instance, the new Glean bot is programmatically invited to all channels the old bot was previously part of. This is done by granting channel invite scopes to the old custom app.

​
Configurations

All Gleanbot-related configurations are automatically migrated from the native instance to the RTS instance:
  • Bot configs (channel settings, response behavior, greenlist/redlist)
  • Redlisted and greenlisted channels are preserved and applied to the new bot
  • App-channel mappings (which AI apps are associated with which channels)
  • /glean configure settings [We missed this], A fix and CP are in progress

​
Digest settings

Digest settings are migrated to the RTS instance. However, digest delivery is currently paused due to Slack rate-limiting concerns.

​
Action packs

Action packs and their associated channel configurations are migrated to the new RTS instance. The necessary changes are made to migrate the agents that use these action packs to the new RTS instance. Because action packs are tied to a datasource instance (DSI), the migration script re-associates them with the RTS DSI.

​
Agents

Agents that were added to Slack channels are preserved. Specifically:
  • Agent-to-channel mappings are migrated to the RTS instance.
  • Agents configured with “send message to channel” actions have their channel doc ID references updated to point to the new RTS instance doc IDs.

​
Users see a new bot responding

After migration, users will see the new white Glean app responding in all channels instead of the old blue custom app. Functionally, the experience will be identical:
  • Same slash commands (e.g. /glean)
  • Same @mentions
  • Same interactive components (buttons, menus, modals), now driven by the RTS app

​
Old app stops responding

Tagging or @mentioning the old custom app will no longer trigger a response.
  • The native bot is disabled as part of the migration.
  • Only the new RTS-powered Glean app will respond.

​
Old bot interaction buttons stop working

Any existing message buttons/interactive components from the old bot. For example, the following will no longer function:
  • “Show Sources”
  • Feedback buttons
  • Action buttons on previous responses
These interactive elements are tied to the old app’s app_id, and Slack routes interactions based on the originating app. Once the old app is silenced, these interactions cannot be processed.

​
Proactive thread summarization paused

The proactive long-thread summarization feature (where Gleanbot automatically summarizes lengthy threads) will not work post-migration. Reason:
  • The RTS marketplace app does not have scopes to listen to all public channel messages passively.
  • This feature relies on receiving webhook events for every message in every public channel and the messages being indexed, which is only possible with the custom app.
There are no followups planned for this feature yet.

​
Frequently Asked Questions

Yes.
  • Gleanbot migration is not partial, it applies to all users in the tenant as soon as the RTS connector is set up and the migration job finishes (typically within a few hours). All users will interact with the new RTS-powered Gleanbot regardless of whether they are in the RTS search greenlist.
  • Once migration is complete, the Slack context used by Gleanbot (e.g., conversation replies, webhooks, etc.) comes from the RTS connector for all users.
  • The RTS search greenlist only controls who can see or access RTS-powered Slack results on the Glean search page, in chat, or via Gleanbot. It does not control who can use Gleanbot in Slack.
  • Users who are not in the greenlist can still access Slack results through the native connector.
  • The only visible change for users is that, instead of the custom blue app, the white marketplace RTS app responds everywhere.
Gleanbot will still respond, but the quality of responses may be degraded for unauthenticated users, because the bot will not have access to their personal Slack context (DMs, private channels, etc.)
Yes.Once the RTS app is installed:
  • Slack routes the /glean command to the most recently installed app — the RTS app.
    • The slash glean commands are removed on the custom app, so the conflict shouldn’t happen in the first place.
Please reach out to Glean support for assistance.
Users will see both apps listed in Slack:
  • Glean (White marketplace app, RTS)
  • Glean Enterprise Graph (Blue custom app native)
However:
  • Only the white RTS app will be active and responsive.
  • The old app is silenced after migration.
  1. Remove slash commands
  2. Reinstall the updated custom app in the workspace.
  3. Setup a new Slack Real-Time Search connector for the same workspace / organisation and complete the Authorization in the Glean Admin console.
  4. Migration of the following happens automatically:
    • Gleanbot configs
    • Agents
    • Actions
The RTS setup validation will fail with:
  • Error code SLACK-10 (for custom apps), or
  • Error code SLACK-13 (for central apps),
blocking the migration until the required scopes are added.