Notifications
Clear all
Topic starter
24/06/2026 9:10 pm
TL;DR: Governance tasks and approvals are now being pushed into daily communication channels through a new two-way Slack integration and Notification Center, reducing email chains and platform comment delays while adding centralised notification control, according to Collibra. The governance challenge is no longer whether teams can communicate, but whether they can preserve decision quality and traceability inside faster workflows.
NHIMG editorial — based on content published by Collibra: Enhance collaboration with our new Slack Integration and Notification Center
Questions worth separating out
Q: How should governance teams use Slack without weakening control?
A: Use Slack as a coordination channel, not as the record of truth.
Q: When does notification routing become a governance issue?
A: Notification routing becomes a governance issue when users can suppress, reroute, or ignore events that materially affect control outcomes.
Q: What do teams get wrong about collaboration tools and governance?
A: Teams often assume that putting governance into chat automatically improves governance quality.
Practitioner guidance
- Define which governance events may enter Slack Classify notifications by severity, actionability, and audit requirement before enabling broad channel delivery.
- Preserve end-to-end decision evidence Ensure threaded comments, approvals, and status changes are written back into the governance record so audit teams can reconstruct who acted, when they acted, and what changed.
- Set explicit notification escalation rules Map important, urgent, and informational events to different delivery paths so users do not mute the signals that matter most.
What's in the full article
Collibra's full blog post covers the operational detail this post intentionally leaves for the source:
- Step-by-step setup of the Slack Integration and Notification Center.
- The exact ways users can comment, star important notifications, and route alerts across email, Slack, and Microsoft Teams.
- Product documentation and demo material for configuring notification preferences in practice.
👉 Read Collibra’s post on its new Slack Integration and Notification Center →
Slack-integrated governance: what it changes for data teams?
Explore further
25/06/2026 6:14 am
Governance-in-chat is a workflow optimisation, not a control substitute. Moving notifications and discussion into Slack can reduce delay, but it does not change the underlying need for approved state, traceable ownership, and authoritative records. The programme risk is that teams start treating channel speed as governance maturity. Practitioners should separate faster coordination from stronger control, because the former does not guarantee the latter.
A few things that frame the scale:
- 1 in 4 organisations are already investing in dedicated NHI security capabilities, with an additional 60% planning to do so within the next twelve months, according to The State of Non-Human Identity Security.
- 85% of organisations lack full visibility into third-party vendors connected via OAuth apps, according to The State of Non-Human Identity Security.
A question worth separating out:
Q: How do security and governance teams keep approvals auditable in Slack workflows?
A: Require every approval or comment that changes state to be captured in the authoritative workflow record, then verify that the recorded identity matches the acting user in the collaboration tool. Without that linkage, the conversation may be visible, but the decision is hard to prove later.
👉 Read our full editorial: Collibra’s Slack integration shifts governance into chat workflows
