Notifications
OnTrackio + Slack
Notifications where IT actually looks: direct messages to the right person, not a channel everyone mutes.
What you get
- Direct messages to the person concerned: renewal owners, asset holders, approvers
- A team-channel webhook fallback when no bot token is configured
- Per-user notification preferences: each person chooses in-app, email, or Slack per notification type
- A security floor: breach and offboarding notices cannot be muted by preference
- Slack seat data in the license register, so utilisation and reclaim decisions see actual use
How it connects
Two modes. The quick one is an incoming webhook to a team channel. The good one is a bot token: OnTrackio looks the person up by email and delivers the notification as a direct message, which is the difference between informing someone and informing a channel they muted in 2024.
What it deliberately does not do
Notifications flow out; nothing flows back. Slack messages cannot approve requests or modify the register, by design: state changes happen in the product where they are authenticated and audit-logged.
Frequently asked questions
Can users turn Slack notifications off?
Per type, yes: everyone gets a channel-by-type preference matrix covering in-app, email, and Slack. A small set of security notices, breach alerts and offboarding notices among them, sits on a floor that preferences cannot mute, and the product is honest in the UI about which those are.
Do we need a Slack admin to set this up?
For the team-channel webhook, anyone who can create an incoming webhook. For direct messages, someone who can create a bot token with the two scopes the guide lists: email lookup and message writing.
Does OnTrackio see our Slack messages?
No. The integration sends messages and looks up users by email. It has no read scopes for conversations, and the sub-processor list on the security page shows exactly where data flows.
All integrations: the full list. Identity posture, sub-processors, and residency: the security page.
See Slack connected to a live workspace
A 30-minute demo covers the setup, the day-two behaviour, and the honest boundaries. Public pricing, no discovery-call gauntlet.