Security and permissions

AnswerLoop – AI Q&A for Confluence · DevBuddy · Last updated November 12, 2026

The question every admin should ask about an AI app: could it show someone an answer built from a page they aren't allowed to see? This page explains how AnswerLoop is designed to prevent that, what it stores, and the limits you should know about.

Summary

How an AI answer is made

  1. A person asks a question.
  2. AnswerLoop searches Confluence and reads pages as that person. Pages they can't open are never found, so they never reach the AI.
  3. The question and excerpts of the pages found are sent to a Claude model through Atlassian's Forge LLMs, hosted by Atlassian. The answer comes back with citations.
  4. Every page given to the AI counts toward who may see the answer, not only the pages it cites.

AnswerLoop also uses a smaller Claude model, through the same Forge LLMs service, to spot duplicate questions: it receives a question's title and the start of its details, plus the titles and short snippets (from their answers or details) of similar questions the asker can open. This runs when a question is posted and in a background pass as the asker. The background pass uses the question's stored title and details without re-checking that the asker can still open the question; it returns only a duplicate/not-duplicate verdict, and what anyone sees is still checked per viewer.

Who else can see an AI answer

What the app stores

Details: Privacy Policy.

Permissions the app requests

AnswerLoop asks for Confluence read and write access to pages, folders, comments, labels and page properties (to create and update question pages); search (to find sources as the asker); user, group and space-permission lookups (to show names and apply space roles); read access to Confluence custom content (used only to read Questions for Confluence data for the import); Confluence's broad read-all-content and write-content scopes, which Forge requires for search results and page events; space details; app storage; personal-data reporting (for account closures); and Forge LLMs. Its scopes let it act as a user.

Most actions run as the person using the app. Background work runs as the person it concerns only after they have allowed access (for example, a reminder is written as the asker, and waits until the asker has opened AnswerLoop once, and background duplicate checks run as the question's asker). Building an expert draft checks each source as every person being asked. Some work runs with the app's own access: keeping question pages up to date, rebuilding the search index from question pages, reading page restrictions to apply the save rules, looking up user names, the title of the page a question is about for questions asked before version 3.36.0 (stored only when that page is in the question's space with no restrictions), and the Questions import (site admins only; it reads Questions content as the app, then as the admin who started it, creates the imported pages as the app with the space's permissions, and never changes Questions data). The app's own access is never used to give the AI content the asker can't open.

Other places your notifications can go

Expert alerts are normal Confluence @mentions. If your site uses Atlassian's Confluence apps for Slack or Microsoft Teams, Confluence delivers them there too, under those apps' terms. The alert is a comment on the question page with a link to answer; it never contains the AI answer.

Limits you should know about

How we check it

Report a security issue

Email support@devbuddy.ai with "Security" in the subject. We reply to security reports within 24 hours.

How DevBuddy manages vulnerabilities and incidents is described in our Partner Security Policy.