Sending Asset Notifications to Slack Team Channels Using Group Subscriptions in DataHub Cloud – DataHub Customer Support Portal

Area: Product Issues

Sub-Area: Subscriptions & Notifications — Slack Integration

Issue

Prior to DataHub Cloud v0.3.17, users could manually specify a Slack channel or member ID when subscribing to an asset, allowing notifications to be routed directly to a team channel. Starting in v0.3.17, this manual channel-entry field was removed. Personal subscriptions now require each user to connect their DataHub account to Slack via OAuth, and notifications are always delivered as a direct message (DM) to that user's verified Slack identity. There is no longer a supported way to redirect an individual subscription to an arbitrary Slack channel. Users who want notifications delivered to a shared team channel must use DataHub's group-based subscription mechanism instead.

You Might Be Asking

Why can't I type a Slack channel name or ID when subscribing to an asset anymore?
How do I get asset change notifications sent to a team Slack channel instead of my personal DM?
Is it possible to route subscription notifications to a shared channel without using groups?

Solution

To route DataHub asset subscription notifications to a Slack team channel, you must use group-based subscriptions. This is the only supported mechanism for channel-level notification delivery in DataHub Cloud v0.3.17 and later. Follow the steps below:

Create or identify a DataHub Group for your team.
Navigate to Settings → Groups and create a new group (or reuse an existing one) that represents the team that should receive notifications.
Configure the Slack channel on the Group.
Open the group, go to the Notifications tab, and enter the Slack channel where notifications should be delivered. You will need the Slack channel ID (e.g., C0123ABCDEF), which can be found by right-clicking the channel name in Slack and selecting Copy link or View channel details.
```
# Example: Slack channel ID format
Channel ID: C0123ABCDEF

# This is entered in the Group's Notifications tab in the DataHub UI.
# It is NOT a URL — use only the channel ID string.
```
Add team members to the Group.
In the group's Members tab, add all teammates who should be associated with this group subscription.
Subscribe the Group to the asset.
Navigate to the asset you want to monitor (e.g., a dataset, dashboard, or pipeline). Use the Subscribe dropdown and select Manage for Groups, then choose the group you configured. Do not use the standard "Subscribe Me" option if your goal is team channel delivery.
```
# Navigation path in DataHub UI:
Asset Page → Subscribe (dropdown) → Manage for Groups → Select your group
```
Verify the configuration.
Trigger a qualifying event on the asset (such as a schema change or ownership update) and confirm the notification arrives in the designated Slack channel.

Additional Notes

The removal of the manual Slack channel entry field for personal subscriptions was an intentional product change introduced in DataHub Cloud v0.3.17, not a regression or bug. The OAuth-based flow was implemented to ensure verified identity linkage between DataHub users and their Slack accounts. Individual subscriptions are scoped to personal DMs by design; there is currently no supported configuration to override this behavior for individual subscriptions. If team channel routing is a requirement, the group subscription workflow described above is the only supported path. If your team has a strong need for per-asset channel targeting without groups, consider submitting a product feedback request through your DataHub support channel.

Issue

You Might Be Asking

Solution

Additional Notes

Related Documentation