Notifications
Beyond posting on the pull request, inline can push alerts to Microsoft Teams and email so the right people hear about a confirmed vulnerability, a CI failure, or a compliance gap without watching the portal.
# Alert categories
Notifications are organized by category, so a channel only hears about what it cares about:
| Category | Fires on |
|---|---|
| Security | Confirmed Sentinel alerts. |
| Compliance | Confirmed compliance exposures and agreement expiry. |
| CI/CD | Actions failure, flaky, and duration alerts. |
| Pentest | Validated pentest findings and engagement summaries. |
| Digest | Periodic roundups. |
# Microsoft Teams
inline posts rich Adaptive Cards to a Teams channel through a Power Automate (“Workflows”) incoming webhook:
- In Teams, create a Workflows webhook for the channel you want, and copy its URL.
- In the portal under Settings → Notifications, add a Teams channel, paste the URL, and choose which categories it should receive.
- Send a test message to confirm it’s wired up.
Each channel records the status of its last send, so you can spot a broken webhook. The webhook URL is stored securely and never shown back in full.
inline uses the modern Power Automate Workflows webhooks, not the retired legacy Office 365 connectors.
Confirmed high-severity findings and summaries can also go out by email. Recipients are resolved from each person’s notification preferences, with per-repository opt-outs — so someone can follow security alerts for one repo without being paged for everything.
# Choosing what’s noisy
Every category is opt-in per channel. A common setup: a security channel that hears Security and Pentest, a build channel that hears CI/CD, and email digests for leads. Because inline only notifies on confirmed findings (not raw candidates), these channels stay signal, not noise.