Slack
Reviews stall because the request sits in an inbox nobody is reading. Connect Slack and the request arrives where your team is already talking, with Approve and Reject buttons on it, so answering takes one click and no context switch.
It is the single biggest thing you can do to speed up a slow review cycle.
#What your team gets
Feature | Who sets it up |
|---|---|
Direct messages when you are asked to approve, and when something you raised is decided | Automatic once Slack is connected |
Approve, Reject and Comment buttons on the message itself | A Confluence administrator turns it on |
Channel notifications so a whole team can watch a space | A Confluence administrator, per space |
#Connecting it
As a Confluence administrator, open Capable, Approval, Notifications and turn on Slack. You will be asked to authorise the Capable app in Slack. Direct messages start working straight away.
Go to Global settings, Features and turn on Slack approval actions. This is the switch that puts the buttons on messages, and it is off until you flip it. See Site settings.
To broadcast a space into a channel, invite the Capable bot to that channel first, then add the space in the global Slack settings. Pick which events the channel should hear about.
One Slack workspace per Confluence site, connected once by an administrator. Connecting a new workspace replaces the old one, and disconnecting turns Slack off for everybody.
#Answering from Slack
A Confluence administrator needs to enable this feature before it is available.
Request messages carry Approve, Reject and Comment. Approve and Reject take an optional note, Comment needs text. Your answer lands on the approval exactly as if you had used the page, and shows up in the history the same way.
Once the request is resolved, Capable goes back and rewrites the message in Slack so the buttons disappear and it shows the outcome. Nobody clicks a stale button on a request that closed last week.
#When Slack refuses your answer
The buttons act on the page as it was when the message was sent, so occasionally you get a reply instead of a confirmation.
Message | What happened |
|---|---|
This page changed since the request was sent | The page was edited, so the review restarted on the new version. Open the page and answer there. See How approvals work. |
You can no longer respond to this request | You were removed from the approver list, or lost access to the page. |
This page was deleted, no approval is required | Exactly that. |
Slack buttons are not offered for spaces that require an authentication code to approve. A signature needs the code, and a Slack button cannot collect one, so in those spaces everyone answers in Confluence. See Sign approvals with a code.
#Channel notifications
Pick the spaces a channel should follow and it gets approval activity for them: requests, approvals, rejections, comments, status changes and expirations, each switchable. Useful for a compliance channel watching a controlled space, or a team channel watching its own.
#A few things that catch people out
Slack finds you by matching your Confluence email to your Slack account. If the two addresses differ, no Slack message is sent, and nothing tells you. If a colleague never gets Slack notifications, check their addresses match.
There is no per-person switch for Slack. You can turn emails off yourself, but Slack is on or off for the whole site.
Buttons appear on requests only, never on the message telling you something was approved or rejected.
Comments are included in full in the Slack message, so anyone in a notified channel reads them.
#Related
Notifications
Everything Capable sends, and when.
Respond to a request
The other ways to answer a request.
Sign approvals with a code
Why codes and Slack buttons do not mix.
Site settings
Connecting Slack and choosing channels.
View approval history
Where a Slack answer ends up.
How approvals work
Why the buttons sometimes refuse.
Requests where people already are, answered in one click.
