Notifications
Notifications route policy violations from Team Server to the teams that need to act on them.
What Gets Notified
Only policy violations trigger notifications. Violations come from:
- Builds, which belong to a pipeline (your CI/CD jobs)
- Workloads, which belong to a deployment (the hosts running your deployed software)
Team Server groups all violations from one build or workload into one alert.
Only violations generate notifications. Team Server does not send alerts for build failures, pipeline discovery, policy edits, or integration health.
Available Channels
- Slack: Post alerts to one or more channels and workspaces.
How Notifications Are Delivered
Delivery is event-driven:
- The Runtime Sensor detects a policy violation and reports it to Team Server
- Team Server records the violation and queues a background notification job
- The job posts an alert to every configured channel whose scope covers the affected pipeline or deployment
Delivery is event-driven. There is no notification scheduler job.
Delivery uses Team Server background workers. Configure workers.mode; BackgroundAsync is recommended. See Workers.
Each Integration Has Its Own Scope
An integration alerts only on its selected pipelines and deployments. Overlapping integrations each post their own alert.
Who Can Configure Notifications
| Role | Grants |
|---|---|
| Viewer | View integrations and their settings |
| Operator | Everything a Viewer can do, plus create, edit, test, and delete integrations |
| Administrator | Everything an Operator can do |
Viewers see integration pages in read-only form. See Access Control for the complete permission model.