Skip to main content

Slack and Teams channels

Connecting Slack or Microsoft Teams (see Connecting an app) only authorizes the workspace account. To actually get agents posting somewhere, a project needs a channel link. The two providers handle that differently, so this page covers each in turn.

Slack: one channel per project​

A project can link exactly one Slack channel. You will see the same small control in two places:

  • On the project itself: the project detail page shows a compact Slack control next to the issue count. If Slack is not connected for the project yet, it renders as a disabled "Link Slack" with a tooltip to configure the integration first. If it is connected but no channel is linked, it is an active "Link Slack" button. Click it to type a channel ID (for example C1234567890, found by right-clicking the channel in Slack → View channel details) or a #channel-name, then Link.
  • Inside the account and project modal on this page: see Managing accounts and project assignments for the same action from the Communication side.

Once linked, the control shows the channel name with a small health dot: green if the channel is currently deliverable, red (with a tooltip naming the reason code) if not, for example when the bot was removed from the channel. Click the linked channel name to edit it, or the trash icon to unlink. Unlinking or relinking immediately invalidates any cached "who can I notify" data used elsewhere (like the remote-control targets used by chat and agent actions).

Conflicts: each Slack channel can only be linked to one project at a time, workspace-wide. Trying to link a channel that is already claimed by another project does not silently fail; it opens a "Channel already linked" dialog with the backend's own message, which names the conflicting workspace and project if you have access to see them, or stays generic if you do not.

Without org:integrations:manage (see the permissions), this control is read-only: you will see the linked channel and its health, but no way to change it.

Microsoft Teams: many channels per project, plus its own bot​

Teams works differently in two ways: a project can have multiple Teams channels linked (not just one), and there is a separate, org-level ACE bot connection needed before the bot can actually reply in a channel.

Configuration lives in a slide-out panel, Teams Configuration, opened from the gear icon on the Microsoft Teams card (the same slot Slack would use for its account modal, but Teams gets this dedicated panel instead).

The ACE Teams bot​

At the top of the panel, a status card shows whether the ACE bot (the hidden microsoft-teams-bot provider; see Connecting an app) is connected:

  • Not connected: "Connect the ACE bot" with copy explaining an admin connects it once, org-wide, so the bot can reply in your Teams channels. Connect starts the same OAuth-popup flow as any other provider.
  • Connected, not yet published: a "Publish to org" button appears, to publish ACE into the tenant's Microsoft 365 app catalog (a one-time step). Publishing can land in one of two states: submitted for review (an admin must approve it in the Teams Admin Center before channels can actually be linked) or published outright (channels can be linked right away).

Linking a project to a channel​

Below the bot card, pick a Project, then a Team, then a Channel (each a searchable combobox; channel choices are scoped to the selected team, and already-linked channels for the currently selected project are excluded so you do not double-link). Link adds the channel to that project's list; it does not replace any existing link, since a project can have several.

If Teams is not connected at all, the form explains that and links back to Integrations. If it is connected but you have no channels, it tells you to make sure your account has joined at least one Team.

Right after linking, if the ACE bot has not been added to that specific Microsoft Team yet, you will see one of two notices:

  • Pending: Add the ACE bot to <team> with an "Add ACE to Teams" deep link that opens Teams directly to the install screen.
  • Unavailable: the channel link is saved, but nothing will actually post there until an admin connects the Microsoft Teams Bot integration at all (that is, the bot has not been connected org-wide yet).

The panel's Project channels list shows every current project → channel link, with the team name (if known) and channel name. Each row has a shortcut to re-open the "Add ACE to Teams" deep link (if the bot is connected) and a trash icon to unlink that one channel from that one project.

How this feeds notifications​

A project's linked Slack channel (Teams is not part of this yet) is one of the delivery rows in the personal Notification delivery modal; see Notification delivery. It is read-only from that modal on purpose: the channel is the project's shared surface, not a personal per-user switch, so it is configured here, on Communication or Teams config, not there.

On this page