Decision Log for Confluence: documentation
Decision Log records team decisions on Confluence pages as structured records (context, options, decision, owner, date, status) and makes them findable later. It runs on Atlassian Forge. It makes no network calls outside Atlassian.
1. Install
- A Confluence site admin installs the app from its installation link or from the Atlassian Marketplace listing.
- Approve the four permissions listed under Permissions.
- Open Apps in the Confluence sidebar and choose Decision Register.
2. First run
The register starts empty. Choose Add sample decisions to load five invented decisions, each marked "Sample", so you can try search, the draft check and the agent before recording anything real. Remove sample decisions deletes them again. Samples never count towards the free tier.
3. Record a decision on a page
- Edit any Confluence page, type
/decisionand insert the Decision Record macro. Publish the page. - Pick a format: Architecture Decision Record, DACI, RFC or Blank.
- Fill in the title, status, owner, context, options considered (one per line) and the decision with its rationale. Save.
Statuses are Draft, Proposed, Decided and Superseded. Every status change is kept in the record's history with the person and date. Choosing an earlier decision in the Supersedes field marks that earlier decision as superseded when you save.
4. Decision Register
The register lists every decision on a page you have permission to open. You can search, filter by status, format, owner, space and decided date, sort, and export the filtered rows as CSV. Details opens the full record: whether it still stands, options with the chosen one marked, rationale, related decisions and history. A banner lists decisions that have been open for more than 14 days.
5. Check a draft or a page against past decisions
- In the register: choose Check a draft, paste a proposal and choose Check.
- On any page: choose Decision check under the page title. It lists the decisions filed on that page and checks the page text against the rest of the log.
Findings are grouped as: possible conflict (a decided record covers this and the text names an option that record rejected, or uses change wording such as "instead of" in the same sentence as what was chosen), relies on a superseded decision, still being decided, and already decided. Each finding shows its reasons and links to the record. Findings come from matching words against recorded decisions. They are leads to verify, not verdicts, and "no overlap found" is not proof that there is no conflict.
6. Decision Keeper, the Rovo agent
If Rovo is enabled on your site, open Rovo chat and choose the Decision Keeper agent, or use the Ask Decision Keeper buttons in the app. It can:
- find decisions about a topic, person or Jira issue key
- explain why a decision was made, with the options that were rejected and a link to the source page
- check the page you are viewing, or text you paste, against past decisions
- list decisions that have been waiting too long
- log a new decision from a discussion or from notes on the page you are viewing, after you confirm it
- change a decision's status
The agent answers only from recorded decisions and only shows decisions on pages you can open. The search, explain and check steps are ordinary app functions over stored records; the agent words the result.
7. Tools for your own agents (Rovo MCP)
The same seven actions are exposed as tools through the app's Rovo MCP module, named Decision Log: find-decisions, explain-decision, check-against-decisions, review-open-decisions, read-page, log-decision and set-decision-status. In Rovo Studio, create or edit an agent, choose Add tools, then Connected apps, then Decision Log. To use the tools from an external MCP client, an organisation admin must first turn them on in Atlassian Administration under Apps, Sites, your site, Connected apps. External access is off by default.
8. Permissions
| Scope | Why |
|---|---|
storage:app | Holds the decision records and each person's list of unread status changes, in Forge storage. |
read:page:confluence | Reads page titles, links and page text as the signed-in user: to show where a decision lives, to check the reader may see that page, and to read a page that the reader asks to have checked. |
read:space:confluence | Reads space names and keys for the Space column and filter. |
read:user:confluence | Backs the people pickers and shows the names of people named on a decision. |
The app has no write access to Confluence content. All Confluence reads are made as the signed-in user, so nobody sees a decision on a page they cannot open.
9. Free tier
The Marketplace edition is free for up to 10 live decisions (anything not superseded). Superseded and sample records do not count.
10. Support
Email kyle@skillmerc.com. Include your site address and what you were doing.