Stanki Guild

Guide · Confluence

Policy acknowledgement nudges in Slack and Microsoft Teams with Confluence Automation

Attestation Flow for Confluence 3.1.0 is the production version (30 October 2026). Last updated 29 October 2026. On the Atlassian Marketplace.

By Bartosz Stankiewicz, founder, Stanki Guild.

A policy acknowledgement is only worth something if the person confirmed it themselves. Slack and Microsoft Teams are where people notice things, so they are a good place for the reminder, and a poor place for the confirmation: a message can be forwarded or read by someone else. The recipes below post the nudge to a channel with Confluence Automation; each message links to the page, where the reader confirms signed in to Atlassian.

The confirmation step uses our app, Attestation Flow. It calls neither Slack nor Teams: your own Confluence Automation rule sends the message with the webhook your admin set up.

What is available in Confluence

#

Atlassian offers Forge Automation actions for Jira only, so there is no "Get acknowledgement status" action in Confluence Automation. Two things replace it:

  • Reminder comments: with reminders turned on in a requirement (a paid setting), Attestation Flow posts a page comment that mentions everyone who has not acknowledged the current version, at most once per chosen interval. A comment is something Confluence Automation can react to.
  • The Rovo agent: Confluence Automation's "Use Rovo agent" action can ask the Attestation Flow assistant who has not acknowledged a page. The answer is text, not structured values.

Recipe A: when the app posts a reminder, nudge the channel

#
  1. In the policy space, open Automation and create a rule with the trigger Page commented.
  2. Add a condition on the comment's text: it contains Automatic reminder from the Attestation Flow app. The trigger fires on every comment, so this condition keeps only the app's reminders. Check the exact smart value for the comment body in the rule builder.
  3. Action: Send Slack message or Send Microsoft Teams message to a channel such as #policy-acknowledgements. Text, for example: "Reminder:" with the page title, "still needs acknowledgements. Open it, sign in and click I have read and understood:" with the page link.
  4. Turn the rule on, then press Send reminder now in the Attestation Flow box of a test page to see one message arrive.

Recipe B: a weekly status to Teams

#
  1. Trigger: Scheduled, Mondays at 09:00.
  2. Action: look up the pages with your policy label (for example policy).
  3. Action: Use Rovo agent, agent "Attestation Flow assistant", with a prompt such as "For each of these pages, who has not acknowledged it and is it overdue?" followed by the looked-up pages.
  4. Action: Send Microsoft Teams message (or Slack) with the agent's answer and a link to the Attestation Flow compliance dashboard.

This recipe needs Rovo on your site and a check that the Attestation Flow assistant can be chosen in Use Rovo agent. The answer is written by Rovo from what the app returns; for audit evidence, use the app's compliance report, not the chat message.

Requiring acknowledgement for new pages

#

The other half of automation is asking the right people in the first place. With a paid licence, a space default can carry a label rule: every hour, the app finds pages of that space with the label that have no requirement yet. With the rule's switch Apply automatically to new labelled pages on (the default for a new rule), the app gives each such page the default itself, owned by the person who set the space default and due a set number of days later, but only where Confluence confirms that person can view the page; other pages wait, and that person sees "N new page(s) match the label rule" on the space page and gives them the default with Apply now. A Confluence Automation rule that adds the label when a page is published then puts every new policy page in that list within the hour.

On a phone

#

People will tap the link on their phone. Atlassian states that Forge apps are not supported in its mobile apps today (Atlassian's issue FRGE-538; FRGE-1492, the request to render Forge modules on mobile, is open), so the Attestation Flow box may not show in the Confluence mobile app. Open the page in the phone's browser, signed in: the confirm button is full width there. The app's reminder comments say the same.

What this does not do

#
  • No confirmation from inside a chat. The message links to the page; the receipt is recorded only when the signed-in reader confirms there.
  • Rules use your Automation allowance. Each run counts toward your plan's monthly Automation usage.
  • The reminder comment is the trigger. Without reminders on in the requirement, Recipe A never fires; use Recipe B or the app's Send reminder now instead.

How our app helps

#

Attestation Flow is our app: named readers confirm each version of a Confluence page, with due dates, reminder comments, escalation and a compliance report, and every receipt in a tamper-evident log. Pricing: free for up to 10 users with every feature, then from USD 0.75 per user per month for the first 100 users. See the documentation.

Common questions

#

Can someone acknowledge a policy from Slack or Teams?

No. The message links to the Confluence page, and the acknowledgement is recorded only when the signed-in reader confirms the current version there.

Does Attestation Flow send anything to Slack or Teams?

No. The app makes no calls outside Atlassian. Your own Confluence Automation rule posts the message with Atlassian's integration.

Can the message list who has not acknowledged?

Recipe B can, through the Rovo agent's answer. The reminder comment itself mentions the outstanding readers on the page, and Confluence notifies them directly.

#