Integrations · 10

Slack

Govern what your agents may read and post in selected public channels. The workspace connection is held by your organization, never by the agent.

What can be governed#

Your organization connects Slack and selects which public channels are governable. Policies then govern the supported action families: channel history, threads, messages, and reactions. Where applicable, modification and deletion can be restricted to messages owned by the connected application. An agent can be allowed to clean up after itself without being allowed to touch anyone else's messages.

policy fragment · slack branch

actions:
  - allow: slack.read_history, slack.read_thread
    where: channel in [#deploys, #support-queue]
  - require_approval: slack.post_message
    where: channel in [#customer-announcements]
  - allow: slack.add_reaction
default: reject

slack.read_history { channel: #deploys }

channel enrolled · action supported · policy permits

ALLOW

slack.post_message { channel: #general }

channel not enrolled · outside the governed boundary

REJECT

Boundaries#

Verified behavior

Governance covers selected public channels and supported action families. A connected workspace does not imply every Slack operation is governable. The agent never receives the workspace credential; allowed operations run through the organization's connected access.

PoliciesBranches, conditions, and the default decision.Console & operationsWhere channels are selected and the connection is observed.