> ## 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.

# Share customer-facing change summaries

> Set up a weekly CodeRabbit automation that posts the customer-visible changes in a Slack channel, grouped as New, Changed, Fixed, and Heads-up, with a sentence Support can use for each.

Cloud Only (This feature is available on CodeRabbit Cloud only. It is not available on self-hosted CodeRabbit deployments.)

## What you get

Once a week, CodeRabbit posts the customer-visible changes in a channel such as `#customer-updates`, grouped under New, Changed, Fixed, and Heads-up. Each item says who is affected and gives Support a sentence to explain it, with pull request and issue links. Changes without release evidence are labeled unverified, and a week with no customer-visible changes gets one line saying so.

## Before you start

| Requirement | Who does it | Where |
| - | - | - |
| Your repositories as connections. Add Linear or Jira so items link their issues. | A CodeRabbit admin | [Connections](https://docs.coderabbit.ai/connections.md) |
| The connections in the channel's scope | A CodeRabbit admin | **Slack** > **Channel mappings** |
| CodeRabbit in the channel, if it's private | A channel member | `/invite @coderabbit` in the channel |

Runs are billed like CodeRabbit Agent for Slack. See [Who can use Automations](https://docs.coderabbit.ai/automations.md#who-can-use-automations).

## Set it up

**1. Open the template**

In the channel, run `/automations` and start a new automation. In **Purpose**, choose **Share customer updates**. **When to run** is **Weekly schedule**; choose the day, **Time**, and **Timezone**.

**2. Name the repositories**

If only some repositories are customer-facing, name them in the **Agent instructions**, for example "Only include changes in the `web-app` and `api` repositories."

**3. Save**

Select **Save and activate**. The automation is active right away, without a trial run.

## Test it

Run `/automations` in the channel and select **Run now** on the automation, or select **Run now** on its page in the web app. **Run now** works while the schedule is active. See [Run now, pause, resume, and delete](https://docs.coderabbit.ai/automations/manage.md#run-now-pause-resume-and-delete).

## Check the runs

Each run starts a new thread in the channel with the week's summary. Each run is also listed on the automation's page. See [Automation details](https://docs.coderabbit.ai/automations/manage.md#automation-details).

If the summary includes internal changes or misses customer-facing ones, tighten the repository list or describe what counts as customer-visible in the instructions.

## What's next

> [card] [Automations in Slack](https://docs.coderabbit.ai/slack-agent/automations.md)
>
> Manage, pause, and edit the automation from its channel.

> [card] [Answer questions in Slack](https://docs.coderabbit.ai/automations/guides/answer-questions-in-slack.md)
>
> Answer code and product questions in a help channel.

> [card] [Automation guides](https://docs.coderabbit.ai/automations/guides.md)
>
> Set up incident response, ticket triage, and more from their templates.


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.