Slack
Slack integration
CommunicationAvailable
BRAIAN connects to Slack through Slack app, bot token with scoped permissions. Agents can approval requests, escalation notifications and carol conversational access. Every action is scoped by the permissions granted to the integration and executed under a versioned policy. Each one is recorded in the audit log with the agent, timestamp and record touched.
What can BRAIAN do?
A scoped Slack app posts approval requests and escalations in the channels a process uses, and gives Carol a conversational entry point. Only the channels the app is invited to are reachable.
| Capability | Agent | Read or write |
|---|---|---|
| Approval requests | All agents | Write |
| Escalation notifications | All agents | Write |
| Carol conversational access | Carol | Read and write |
How does it connect?
- Connection method
- Slack app, bot token with scoped permissions
- Credential
- A Slack bot token issued to the workspace app and held in the secrets store.
Credentials are held in an encrypted secrets store. BRAIAN never stores end-user passwords.
Which permissions are required?
- chat:writePosting messages in the channels the app has been invited to.
- users:readMatching an approver to their Slack account.
Permissions are requested at the minimum scope the configured processes require. Unused scopes are not granted.
Which processes use it?
Processes that run on this connection, and the domains they belong to.
Policy compliance
SLA
Access certification
Used across every business domain.
How do you revoke access?
Access is revoked in Slack itself — by disabling the credential or removing the granted scopes — or in BRAIAN by disconnecting the integration. Processes already running stop at their next call to Slack and are held for review rather than completed with partial data; the interruption and the state of each process are recorded in the audit log.
FAQ
Does BRAIAN store data from Slack?
BRAIAN reads what a process needs, when it needs it. Records retrieved from Slack are held only for the duration of the process and in the audit trail of the actions taken; Slack remains the system of record.
What happens if the connection fails mid-process?
The process stops at the failed step and is held for review. Nothing is written twice: completed writes stay recorded in the audit log and the remaining steps resume only once the connection is restored.
Can permissions be scoped per agent?
Yes. Scopes are defined per agent, not per system, so one agent can read while another cannot, on the same connection to Slack.
