Install the BrewMy{Code} app, grant knowledge bases to channels, and approve agent actions from Slack.
app_mentions:read, chat:write, channels:history (only for channels it is invited to), users:read.email (to map Slack users to workspace users) and commands./invite @brewmycode.A channel can only answer from knowledge bases granted to it. Under Knowledge → (knowledge base) → Access → Channels, add the channel. Users still only see documents they personally have access to in the source.
Mention the app anywhere it's invited:
@brewmycode Which suppliers have open August invoices?
Replies arrive in a thread with numbered citations. Follow up in the thread to keep context. In a DM with the app, no mention is needed.
| Command | What it does |
|---|---|
/brewmycode ask <question> | Ask privately; only you see the answer |
/brewmycode sources | In a thread: show everything considered for the last answer |
/brewmycode run <agent> | Start an agent you have access to |
/brewmycode runs | Your recent runs and their status |
/brewmycode stop <run id> | Cancel a run you started |
When an agent needs approval, the approvers group receives a message with the full context (what the agent found, what it wants to do, why the policy triggered) and Approve / Reject buttons. Decisions are recorded in the run trace with the approver's identity.
Separately from the app, you can connect Slack channels as a source so that past threads become searchable knowledge. Channel membership is synced as the permission boundary. See Slack integration.