Slack notifications
Slack is connected once, by a Confluence site administrator, for the entire site. Individual users never connect their own Slack.
That design has consequences, and they are the most important thing on this page.
#Connecting
A Confluence administrator connects Slack from global settings.
Direct messages are matched to people by their Confluence email address.
Channel broadcasts are configured per Confluence space by an administrator.
#The three caveats
An individual cannot turn Slack messages off. The only self-service control is the email switch. If somebody wants Slack messages to stop, an administrator has to disconnect Slack or turn it off site-wide.
Channel broadcasts bypass the per-user page read-permission check. A restricted page's title and link go to everyone in the channel. Administrators must understand this before configuring a channel broadcast on a space with restricted content.
Delivery failures are silent. If the bot was never invited to the channel, or the channel was renamed or archived, messages are dropped with no error anywhere in Confluence.
#Two quieter traps
If somebody's Slack email does not match their Confluence email, their direct messages are silently skipped. They will not know.
Disconnecting Slack is site-wide and destructive rather than personal. An administrator experimenting with their own settings can switch Slack off for the whole company.
#A few things worth knowing
Invite the bot to the channel before configuring a broadcast, or nothing will arrive and nothing will say so.
Check email addresses match if a particular person never receives anything.
Treat channel broadcasts on spaces with restricted pages as a deliberate disclosure decision.
#Related
Site-wide, admin-only, and silent when it fails.
