> For the complete documentation index, see [llms.txt](https://typo.gitbook.io/typo-help-docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://typo.gitbook.io/typo-help-docs/platform/ops/alerts.md).

# Alerts

Typo's automated notification engine helps remove bottlenecks in your development cycle by delivering real-time updates and scheduled health reviews directly to your developers and team channels.

* **For Developers (Real-Time)**
  * **PR Review:** Sent to assigned reviewers right when a PR is raised.
  * **PR Approved:** Sent to the author as soon as their code is signed off.
  * **PR Review Comments:** Sent to the author for every comment or feedback thread left.
  * **PR Merged:** Sent to the author confirming their code is successfully merged.
* **For Teams (Scheduled Summaries)**
  * **Daily PR Summary:** A daily recap of all open, merged, and pending PRs—perfect for tracking unblocked work before standard standups.
  * **Weekly PR Summary:** A retrospective breakdown highlighting development pipeline trends and backlog health.

<div align="left"><figure><img src="/files/ZuycC6GRX6CU5j1XZHY1" alt=""><figcaption></figcaption></figure></div>

#### **How to Configure Alerts**

1. Choose an Alert: Go to the Alerts configuration page in Typo and click on the specific alert type card.
2. Select Teams: Use the dropdown menu to find and assign specific developer teams, or select the "Select all teams" checkbox for global settings.
3. Choose Channels: Toggle your preferred notification channels:
   * Alert on Mail: Sends a structured email notice.
   * Alert on Slack: Sends automated notifications directly to personal Slack DMs or designated team workspaces.
4. Save: Hit the Save button to activate the configuration instantly.

<div align="left"><figure><img src="/files/oLiqikqDwyYb4I68PCBp" alt=""><figcaption></figcaption></figure></div>