---
title: Slack
description: Connect Slack to give Knowledge and workers your channels as context, let them propose messages for approval, and start and steer Developer sessions from a Slack thread.
---

Slack is used three ways. Each is a separate permission.

| Use | What it does |
|---|---|
| **Context** | Channels and threads become searchable, permission-aware context for Knowledge and workers. |
| **Messages** | Knowledge and workers can **propose** a message; it's sent only when you approve that exact text. |
| **Sessions from Slack** | Start and steer Developer sessions from a Slack thread with `/ysra`. |

## Connect

**Workspace → Integrations → Slack → Connect**, and approve the app in your Slack
workspace. Once installed, Ysra creates a Knowledge connection for it.

## What gets synced

- Conversations the app can access — channels and private channels it's been
  added to — including thread replies.
- Each message keeps its channel, thread and author, and a link back to Slack.
- Syncing resumes where it stopped, in the background. Check status and **Sync
  now** from the connection.

Only channels the app can access are synced. To include a private channel, add
the app to it.

## Proposed messages

When an expert or worker with the right capability wants to post, you get a card
with the target — a channel, private channel or person, optionally a thread —
and the exact text. **Approve**, **Edit** (which makes a new proposal) or
**Reject**. See [Actions and approvals](../knowledge/actions.md).

## Developer sessions from Slack

The `/ysra` command runs Developer sessions from Slack. A session started or
linked from Slack is bound to that **thread**: ordinary replies in the thread
steer the session, and Ysra posts its progress there — edits, commands, checks,
reviews, previews and the final result.

```text
/ysra start owner/repository | describe the work
/ysra link <session link>        bind this thread to an existing session
/ysra status                     where the session stands
/ysra report                     the build report
/ysra diff                       which files changed
/ysra reasoning                  Ysra's recorded rationale
/ysra preview                    start a preview
/ysra deploy                     deploy the verified candidate
/ysra deploy unverified          deploy knowingly, without full verification
```

It's the same session as in the portal — the same budget, repository access,
verification, preview and deployment rules. Nothing is weaker because it was
started from Slack.

- **Only the person who installed the Ysra app** can start paid work, steer,
  preview or deploy from Slack.
- `/ysra diff` lists changed files, not their contents — source files can
  contain secrets, and Slack isn't the place for them. Full evidence is in the
  portal.
- `/ysra reasoning` shows only the rationale Ysra already recorded, never
  internal model reasoning.
- A retried command can't start the same paid work twice.

## Mentions

Type `@` in the Ask composer to insert a Slack person or channel. Ysra keeps the
stable ID behind the name so proposed messages go to the right place.