> ## Documentation Index
> Fetch the complete documentation index at: https://docs.trychert.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Install

> Install Chert Notifications and Chert Agent into your Slack workspace and bind a channel to a project.

Each Chert project binds to one Slack channel. Install through the
Settings page in the Chert console — the OAuth flow handles workspace
authorization and writes a per-project bot token.

## Before You Begin

| Requirement                                                                | How to verify                                                  |
| -------------------------------------------------------------------------- | -------------------------------------------------------------- |
| You are a Slack workspace admin, or your admin has pre-approved Chert apps | Slack → Settings & administration → Manage apps → App approval |
| You have an active Chert project                                           | Your console URL contains `?project=<uuid>`                    |
| The target channel exists                                                  | Public or private — both are supported                         |
| Your workspace can install Slack apps                                      | App installation is enabled at the workspace level             |

<Note>
  Each project gets its own bot token. Installing into multiple
  projects from the same workspace means the workspace sees the same
  Chert app installed once, with the bot present in each bound
  channel.
</Note>

## Install Chert Notifications

<Steps>
  <Step title="Open Settings in the Chert console">
    Open your project at `https://console.trychert.com/?project=<uuid>`,
    then click **Settings**.
  </Step>

  <Step title="Click Connect Slack">
    The button kicks off the OAuth v2 flow. You will be redirected to
    `slack.com/oauth/v2/authorize` with the scopes listed below.
  </Step>

  <Step title="Authorize the app in Slack">
    Pick the workspace, review the requested scopes, and click **Allow**.
    Slack redirects back to Chert with an OAuth code.
  </Step>

  <Step title="Confirm the install">
    Settings shows **Connected to \<workspace>**. The bot token is
    stored server-side and never exposed to the browser.
  </Step>

  <Step title="Pick a channel">
    The channel picker lists every public channel and every private
    channel the bot is a member of. Select the target channel and save.
  </Step>

  <Step title="Invite the bot to private channels">
    For private channels, run `/invite @Chert Notifications` in Slack so
    the bot can post.
  </Step>
</Steps>

### Requested scopes

| Scope               | Reason                                                                 |
| ------------------- | ---------------------------------------------------------------------- |
| `chat:write`        | Post reply notification cards                                          |
| `chat:write.public` | Post without explicit channel invite (public channels)                 |
| `channels:read`     | Populate the channel picker                                            |
| `groups:read`       | Include private channels in the picker                                 |
| `canvases:write`    | Create and update the Overview, Daily Summary, and Lead Lists canvases |

## Install Chert Agent

Chert Agent is a separate Slack app with its own bot user. Install it
through the same Settings page.

<Steps>
  <Step title="Open the Chert Agent connector">
    On Settings, scroll to **Chert Agent**. Click **Connect**.
  </Step>

  <Step title="Authorize and pick a channel">
    OAuth flow mirrors Chert Notifications. Pick the channel where you
    want `@Chert Agent` mentions to be answered.
  </Step>

  <Step title="Try it">
    In the channel: `@Chert Agent how are we doing today?`
  </Step>
</Steps>

<Tip>
  Both apps can live in the same channel. Chert Notifications posts
  reply cards; Chert Agent responds to `@`-mentions and posts proactive
  alerts.
</Tip>

## Channel binding

| Behavior                | Detail                                                                                                                                                                                                  |
| ----------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| One channel per project | Switching channels does not require re-installing — pick a different channel from the Settings picker.                                                                                                  |
| Cross-project isolation | Two Chert projects can target the same Slack channel. Each project's bot token, settings, and canvases are independent.                                                                                 |
| Disconnect              | Settings → **Disconnect Slack** removes the bot token from Chert. Notifications stop immediately. The Slack workspace's app install record is preserved on Slack's side until you uninstall from Slack. |

## See Also

<CardGroup cols={2}>
  <Card title="Configuration" icon="gear" href="/slack/configuration">
    Notification routing, feature flags, and the Nth-reply filter.
  </Card>

  <Card title="Security" icon="shield" href="/slack/security">
    What scopes are used for what, and how tokens are stored.
  </Card>
</CardGroup>