> ## Documentation Index > Fetch the complete documentation index at: https://docs.quintai.dev/llms.txt > Use this file to discover all available pages before exploring further. # Alerts and approvals in Slack, Teams and PagerDuty > Connect a Slack, Microsoft Teams or PagerDuty channel, send a test, and know what will arrive in it. At the end of this page you have one channel connected, verified and enabled, and you know what Quint will post to it. Connecting a channel needs the **Admin** or **Owner** role. A Slack or Teams channel receives three kinds of message: alerts, approval requests from workloads, and policy recaps with their match-threshold notifications. PagerDuty receives alerts and, when a workload opts in, block notices; recaps are not sent to PagerDuty. ## Before you start * A Slack incoming webhook URL, a Teams Workflows webhook URL (Power Automate Workflows), or a PagerDuty integration key. Create these in the other product first. * Quint treats each of these values as a secret. ## Connect a channel **1. Open the Connect sheet** Open **Integrations** under **Workspace**. In **Alert delivery**, click **Create channel** and choose the destination. The sheet is titled **Connect a channel**. **2. Fill in the destination's fields** > [tab] Slack > > **Incoming webhook URL** (required). Saving posts a verification message to the Slack channel the webhook belongs to. > [tab] Microsoft Teams > > **Workflows webhook URL** (required). This is a Power Automate Workflows URL, not a classic Office 365 connector URL. > [tab] PagerDuty > > **Integration (routing) key** (required) and **Default severity**: **Critical**, **Error**, **Warning** or **Info**. The default is **Warning**. PagerDuty incidents Quint opens are resolved automatically. **3. Save** Slack, Teams and PagerDuty are verified live when saved, so a bad credential is caught here rather than at the first alert. **4. Send a test** Click **Send test** on the new channel. Quint sends one test event to the destination. Confirm it arrived before you rely on the channel. **5. Enable it** Click **Enable**. Until then the channel is saved but receives nothing. **Disable** stops delivery without deleting the credential. **Remove Channel** deletes it. ## What arrives **Alerts.** Any alert that matches the channel's filter. The refused-action alert is on the **Alerts** tab of **Policies** (see [Alerts](https://docs.quintai.dev/policies/notifications.md)); the three built-in alerts (an agent said it would do one thing and did another, unusual activity, and the risk score passing your limit) are on **Settings › Notifications** (see [Built-in alerts](https://docs.quintai.dev/settings/notifications.md#built-in-alerts)). Both pages show where an alert is sent; this page is where a channel is turned on or off. **Security events.** A message when someone changes members, keys or settings in the workspace. Each realtime channel (Slack, Microsoft Teams, PagerDuty and the alert webhook) has a **Send security events** switch on this page, with the subline "Member, key and settings changes."; batch exporters do not. Only channels with the switch on receive them. While the switch is on, one status word stands beside it: **Working**, **Not working**, **Not sending right now**, **Waiting for the first alert** or **Status not known yet**; the last also appears in place of the switch while Quint has no recorded state for the channel yet. Each word means what it does for alerts; see [How a channel's status is decided](https://docs.quintai.dev/policies/notifications.md#technical-details). Security events are not set on **Policies › Alerts** or **Settings › Notifications**. **Approval requests.** When a workload's policy holds a tool call for a person to decide, the channels chosen on that workload receive the request. The message carries a link that opens the request in **Approvals**, with the banner "Showing the request from your notification." Deciding needs a sign-in from the last 10 minutes. PagerDuty receives block notices from a workload only when **Also send block notices to PagerDuty** is on in that workload's settings. See [Decide an approval](https://docs.quintai.dev/dashboard/decide-an-approval.md). **Scheduled summaries.** A summary (recap) is a scheduled report of what your rules matched, as counts and rule names only, delivered to one Slack, Teams or alert-webhook destination. A match threshold on a summary sends a message to the same destination when refuse matches reach a number you set within a fixed UTC window. See [Alerts](https://docs.quintai.dev/policies/notifications.md). **Risk score limit.** Under **Settings › Notifications**, **Built-in alerts**, the risk score limit (0 to 100) sets the score at which an alert goes to every enabled destination whose filter matches. With no limit set, that alert is off. A Policy Writer, an Admin or an Owner can change it. ## If this fails | What you see | What it means | What to do | | - | - | - | | The save is refused, or no verification message arrives in Slack | The other product rejected the URL or key during live verification | Create the webhook or integration again in Slack, Teams or PagerDuty and paste the new value. | | **Send test** succeeds but no alerts ever arrive | The channel is not enabled, or no alert rule fires | Click **Enable**. Then check the risk score limit under **Settings › Notifications**: with no limit set, that alert is off. | | "This request is not in your queue: it was decided, it expired, or you are not one of its approvers." | The approval you clicked is no longer yours to decide | Click **Show all requests** to see what is still waiting. | | "Sign in again to approve." | Your sign-in is older than 10 minutes | Click **Sign in again**, then decide. Nothing was sent. | | "You are not an approver for this workload." | You are not in the workload's approver list | Ask an **Admin** or **Owner** to use **Change approvers** on the workload. | | "Viewers can see requests but cannot decide them." | Your role is **Read** | Ask an **Admin** or **Owner** to change your role. | | An agent reports "approval requests from this workload are blocked because it has no working notification channel" | The workload has no enabled channel to send requests to | Open the workload's settings and connect a channel under **Channels**. | | A held request expires with nobody notified | The workload has no approvers | On the workload, use **Change approvers**. Without approvers a held call waits until it expires and is then denied. | ## Next * [Notifications and built-in alerts](https://docs.quintai.dev/settings/notifications.md) * [Alerts](https://docs.quintai.dev/policies/notifications.md), to send a scheduled summary to this channel * [Webhooks and event fields](https://docs.quintai.dev/integrations/webhooks-and-event-fields.md), for a signed webhook instead of a chat channel * [Workloads](https://docs.quintai.dev/dashboard/workloads.md), where approvers and channels are set This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.