Communication
Integrations → Communication is where a workspace connects the tools its team already works in: Slack, Microsoft Teams, Linear, and Jira today. Connect an account once and agents can post updates, read issues, and stay in sync, with no one re-authenticating per project.
This is one of three surfaces under the Integrations section. The others are Clouds (AWS, GCP, and Azure, read-only, for infrastructure discovery) and Repositories (GitHub and GitLab). All three share the same underlying connect and disconnect machinery. This guide covers what is specific to communication tools: chat channels, issue trackers, and the ACE Teams bot.
In this section
- Connecting an app: the provider catalog, the OAuth connect flow, reconnecting, disconnecting, and the read-only mode a workspace can be limited to.
- Managing accounts and project assignments: when you have connected more than one account of the same provider, choosing which account serves which project, and the "one account per project" rule.
- Slack and Teams channels: linking a Slack channel or Microsoft Teams channel to a project so agents can post there, channel conflicts, channel health, and the separate ACE Teams bot connection.
Where to find it
Left sidebar → Integrations → Communication, or go straight to /integrations/communication. Connections are workspace-scoped, so the page is gated on having a workspace selected (the switcher is in the top-left).
Permissions
| Grant | Controls |
|---|---|
org:integrations:read | Seeing this page and the status of every connection |
org:integrations:manage | Connecting, reconnecting, disconnecting an account, opening account and project management, and configuring Teams channels |
Without org:integrations:manage, the page shows a banner ("This workspace grants integration visibility only. Connection, credential, and project-assignment controls are read-only.") and every action control is hidden.
How this connects to the rest of the platform
- Inbox: a project's linked Slack channel is one of the four delivery rows in Notification delivery; Inbox always fires, and Slack mirrors "Needs you" items to the project's channel if one is linked. That modal links back here (Set up / Change channel) when nothing is connected yet.
- Projects: the project detail page shows a live Slack-link control next to the issue count. See Slack and Teams channels.
- Agents and issue tracking: connecting Linear or Jira here is what lets agents read and create issues in that tracker instead of (or alongside) the built-in Development board.