Notify

Variable Send a notification to the right team. The team learns about the issue without anyone creating tracked work, then decides whether to act.

Good for low-priority issues or when you want human confirmation before acting.

How it works

Tero sends a message to Slack or email with context about the issue. The notification includes what Tero found, the impact, and a link to take action in Tero.

Setup

Connect your notification channel:

Slack

Send notifications to channels or DMs based on service ownership.

Example

Tero identifies that payment-service is logging full request payloads including credit card data (masked, but still present). You approve the policy and select “Notify.” Tero sends a Slack message to #payments-team:

Tero identified an issue in payment-service

payment-service is logging full request payloads (~15KB per log).
This generates 2.1M logs/day at $3,200/day in costs.

The payloads contain masked credit card data. While masked,
this may still be a compliance concern.

→ Review in Tero: https://app.tero.dev/policies/abc123

The team sees the message, investigates, and decides how to respond. They might open a PR, create a ticket, or dismiss if it’s intentional.

When to use

Notify works best when:

You want awareness without formal tracking
The issue is low priority
You want human confirmation before automated action
Multiple people should see it but one person will own the response

Create tickets Set SLOs

Introduction

Issues

Master Catalog

Policies

Integrations

Reference

How it works

Setup

Slack

Example

When to use

​How it works

​Setup

Slack

​Example

​When to use

How it works

Setup

Example

When to use