> ## Documentation Index
> Fetch the complete documentation index at: https://docs.warrn.io/llms.txt
> Use this file to discover all available pages before exploring further.

# Alert intelligence

> The per-service AI Triage toggle and how it interacts with the team's master switch.

A service has one AI toggle: **Auto Triage**. When on, Warrnagen automatically investigates new alerts on this service, looks at your codebase, logs, recent deploys, past incidents, and connected tools, and attaches an investigation summary to the alert.

## Team is the master

The service toggle only does something if the parent team's **AI Triage** master switch is also on. If the team switch is off:

* The service toggle is shown disabled with a tooltip explaining why.
* No service in that team runs agentic triage, regardless of its own setting.

This means turning on AI Triage for a service is a two-step check: team on, then service on.

## Why per-service control matters

Even within a team that has AI Triage on, you might want to keep one service quiet:

* A noisy legacy service where AI investigations would add no signal.
* A service in early development where you don't want investigation cost yet.
* A service the team explicitly handles manually.

Turn the service's Auto Triage off and that service skips AI Triage while the rest of the team keeps it.

## Other intelligence settings

[Auto-Group Alerts](/components/teams/alert-intelligence#auto-group-alerts) and [past-alerts lookback](/components/teams/alert-intelligence#past-alerts-lookback) are team-level and apply to every service in the team. Services don't override them.