> ## Documentation Index > Fetch the complete documentation index at: https://docs.coderabbit.ai/llms.txt > Use this file to discover all available pages before exploring further. # Triage in Slack > Get your Triage queue as a scheduled digest, send reviewer requests to the people who should act on them, and approve or close a pull request without leaving Slack. export const OpenBetaBadge = ({tip = "This feature is currently in open beta. We are actively improving it based on your feedback. If you encounter any issues or have suggestions, please share them on our Discord community or visit the support page.", title = "Open Beta", cta = "Contact support", href = "/support", disabled = false}) => { return {title} ; }; export const TeamPlanBadge = ({tip = "This feature is available on Team (formerly Pro+), Advanced, and Enterprise. Please refer to our pricing page for more information about our plans and features.", title = "Team Plan", cta = "Read more", href = "https://coderabbit.ai/pricing", disabled = false}) => { return {title} ; }; export const SlackBadge = ({tip = "This feature is available with CodeRabbit Agent for Slack.", title = "Slack", cta = "Learn more", href = "/slack-agent", disabled = false}) => { return {title} ; }; export const GitLabBadge = ({tip = "This feature is available on GitLab.", title = "GitLab", cta, href, disabled = false}) => { return {title} ; }; export const GitHubBadge = ({tip = "This feature is available on GitHub and GitHub Enterprise.", title = "GitHub", cta, href, disabled = false}) => { return {title} ; }; | A queue only works if you look at it. Triage's Slack surfaces exist so you do not have to: the digest brings the top of the queue to you on a schedule, reviewer requests arrive as a direct message from the person who sent them, and the common actions are buttons on the message. Slack delivery requires a connected Slack workspace and a link between your CodeRabbit account and your Slack account. Setting that up is covered in [CodeRabbit Agent for Slack](/slack-agent/connections). It is also rolling out gradually, so it may not be switched on for your organization yet. ## What Slack lets you do | Workflow | What it does | Requires | | - | - | - | | **[PR digest](#the-pr-digest)** | Scheduled Slack message with the top of your queue, once or twice a day | Connected Slack workspace, your linked Slack identity | | **[Reviewer requests](#reviewer-requests)** | Direct message to a reviewer when someone requests them from Triage | Reviewer's Git-provider-to-Slack identity linked; their reviewer notifications on | | **[PR-level pings](#pr-level-pings)** | Share a specific pull request to a channel or group DM | Review seat; connected workspace; your linked Slack account | | **[Acting from Slack](#acting-from-slack)** | Approve, request changes, close, merge, or repair from message buttons | Your linked Git-provider authorization | | **[Follow a pull request](#follow-a-pull-request)** | Get one pull request's activity in a dedicated Slack thread | Tracked open PR; connected workspace; linked identity; channel access | ## The PR digest The digest is a scheduled message listing the pull requests most worth your attention right now, scoped to what you can see and to your part in each one. ### Schedule Set the cadence in **Follow settings** on the Triage page: | Setting | What you get | | - | - | | **Once daily** | One digest, at 9:00 in your own timezone. | | **Twice daily** | A second digest roughly six hours after the first. | **Twice daily** is the default, and you can turn the digest off entirely. You can also narrow the digest to specific repositories, and to your role on each pull request, in the same settings. If you have quiet hours configured, the first digest arrives when your quiet hours end rather than at 9:00. **Follow settings** shows exactly when the next one is due, in your timezone. ### What it contains Up to four sections, in this order, with the most urgent pull requests in each: | Section | What is in it | | - | - | | **Needs Your Review** | Your review has been requested. | | **Needs Your Action** | Your pull requests that need you — including anything ready to merge and anything worth reviewing for closure. | | **Close candidates** | Stale or superseded work you could clear out. | | **Up Next** | What is coming after the above. | Each pull request carries its title, its priority reasoning, its age, and buttons for the obvious next step — approve, request changes, close, or ask CodeRabbit to repair it. A section you have nothing in is left out entirely. The digest is a **summary, not an inventory**. It shows a few pull requests per section and tells you how many more there are, with a link back into Triage for the rest. **No digest is sent when you have nothing waiting.** Triage does not send an all-clear. An unchanged digest is also not re-sent, so a second delivery means something actually moved. Anything you have marked with **Ignore close candidate** is left out of your digest, though other people still see it in theirs. ### If your provider authorization lapses The digest is scoped to repositories you can access, so it needs your Git-provider authorization to build. When that authorization expires, Triage sends a single message asking you to reconnect your Git provider instead of sending a partial digest that quietly omits repositories. ## Reviewer requests When you ask someone to review a pull request from Triage, and their Git provider account is linked to Slack, they get a direct message from you: who is asking, the pull request, CodeRabbit's summary of it, and an **Approve** button. These reviewer requests are sent when a person asks for one. Separately, an enabled [Slack reminder rule](/triage/rules#send-slack-reminders) can automatically notify the author and reviewers of matching PRs, subject to identity mapping and notification settings. The same requests are collected under **Review requests** in the CodeRabbit app's Slack Home tab, so a reviewer can see everything waiting for them in one place rather than hunting through direct messages. Each one offers **Approve**, **Comment**, and **Ignore**. The Home tab is rebuilt with every new request, so it always shows the current set. ### Linking identities Sending a request to Slack requires knowing which Slack account belongs to which Git provider account. When Triage is confident of the match it uses it; when more than one Slack account could be the right person, it asks you to confirm before sending, rather than messaging the wrong colleague. Reviewers who have turned reviewer notifications off do not receive these messages, and Triage tells you so instead of failing silently. ## PR-level pings Where enabled for your organization, choose **Ping in Slack** from a Triage card's action menu to share that pull request in a Slack channel or group DM. This is independent of reviewer assignment: it does not request a review in your Git provider or add reviewer notifications to Slack Home. You need a Review seat, a connected Slack workspace, and your linked Slack account. Choose **Channel** to search the current workspace's channels, or **DM** to select teammates from that workspace. Group DMs include you and your selected teammates. If prompted, connect your Slack account before choosing the destination. CodeRabbit checks your current Slack connection and channel membership again before delivery. A channel being listed does not guarantee delivery: the bot must be able to access it and verify that you are a member. Add an optional message and select **Send message**. CodeRabbit includes the pull request title and link. The **Slack message queued** confirmation means the request was accepted for delivery. A ping sends one message; use [Follow](/triage/slack#follow-a-pull-request) for ongoing updates. ## Acting from Slack The buttons on a digest or a review request run against your Git provider as **you**, using your own authorization: | Button | What it does | | - | - | | **Approve** | Submits an approving review, with no comment. It does not merge, comment, or resolve threads. | | **Request changes** | Submits a changes-requested review. | | **Close PR** | Closes the pull request. | | **Merge** | On GitHub, **enables auto-merge** on the pull request — GitHub merges it once its own requirements are met. It does not necessarily merge right now. | | Repair buttons | Ask CodeRabbit to fix CI, resolve conflicts, or apply fixes, exactly as the equivalent action in Triage does. | If CodeRabbit has no current Git-provider authorization for you, the button tells you to connect your Git provider rather than failing quietly. ## Follow a pull request **Follow** on a card sends that pull request's activity to a Slack channel or direct message of your choosing, in its own thread. Use it for a change you want to track without it being your review. Choose **Follow** from the card's action menu, pick a channel or send it to yourself, and choose whether to use your default event settings or pick specific events. Following a pull request needs a tracked, open pull request, a connected Slack workspace, your linked Slack identity, and CodeRabbit access to the channel you pick. To stop, open **Follow settings** and choose **Unfollow**. ## Rule-based reminders Use [Triage rules](/triage/rules#send-slack-reminders) to remind PR authors and reviewers when conditions match, such as review required or an urgent PR with no human activity for 24 hours. These rules have their own delivery time, timezone, cooldown, and activation flow. They are separate from your personal digest schedule, one-time pings, and Follow subscriptions. ## What's next Connect a Slack workspace and see everything else CodeRabbit can do there. Do the same things from the queue, with the full context of the card in front of you. This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.