Slack
Connecting a Slack workspace, what becomes a ticket there, and where your replies land.
Slack is a two-way channel. Messages raise tickets here, and your reply lands back in the same Slack thread. Everything Slack needs is on one page, Channels, Slack: the credential at the top, the behaviour underneath.
One page, not two
/integrations/slack redirects to /channels/slack. Slack briefly took two
pages, with the credential in Integrations and the routing under Channels;
that split was reversed, because an operator sets both up in one sitting and
clicking Manage on the Channels list should not land somewhere that tells you
to go elsewhere.
Connecting
Connect runs an OAuth consent at Slack and returns you to this page with the outcome stated plainly: connected, denied, expired, or refused. A consent attempt is short-lived and single-use, so expired is the most likely thing you will see if you opened the link and came back later. Every refusal keeps a live Connect button rather than sending you off to find this screen again.
Once connected, the page names the Slack workspace on the other end and offers Disconnect.
If the runtime cannot be reached the page says it cannot tell whether Slack is connected. That is not the same as reporting it disconnected, and the page does not pretend otherwise.
What becomes a ticket
Two things, and it is worth being exact, because the answer is narrower than it looks:
- anything written in a Slack channel Aura has been added to, public or private. A whole thread becomes one ticket.
- anything someone asks Aura to raise, in a direct message or by mentioning it.
An @mention in an ordinary channel, or a direct message, is treated as an instruction to Aura and not as ticket-filing traffic. The activity-feed channel is the exception in the other direction: what people write there is never turned into a ticket at all.
You change what is in scope by adding Aura to a Slack channel or taking it out again. There is nothing to configure for it on this page.
Behaviour on the same page
Below the credential sit the acting bot, the activity-feed destination and which events are posted to it, intake from people who are not workspace members, and the staff authority list, which grants authority to act rather than configuring the integration.