Security and permissions
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
- Runs on Atlassian. AnswerLoop is a Forge app with no calls to servers outside Atlassian. Your content, the search index and the AI all stay inside Atlassian Cloud. We (DevBuddy) do not receive your Confluence content.
- The AI only reads what the asker can read. Search and page reads for an AI answer run as the person asking, with their own Confluence permissions.
- Answers are checked per viewer. Other people see an AI answer only if they can open every page it used, or if it was saved to the question page under the save rules below.
- Reading follows Confluence. Questions are ordinary Confluence pages in your spaces, protected by your existing space and page permissions.
- Writing follows AnswerLoop's roles. Who can ask, answer, comment and vote is set by AnswerLoop's space roles (default: anyone who can view the space; asking also needs Confluence permission to create pages). The app writes answers, comments and votes onto the question page itself, so Confluence edit restrictions on a question page don't limit them, and page history shows the app as the editor.
How an AI answer is made
- A person asks a question.
- AnswerLoop searches Confluence and reads pages as that person. Pages they can't open are never found, so they never reach the AI.
- 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.
- 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
- Source titles follow the same rule. On the question page, in its page property and in exports, a source is named only if it is in the question's space with no read restrictions; other sources are shown as a count. In the app, each reader sees the titles of the sources they can open.
- The asker sees the answer they were given while they can still open every page it used. If they lose access to one, the answer is hidden from them too; they see the titles of the sources they can still open and a count of the rest. (Text saved on the question page follows that page's permissions, as below.)
- Saved to the question page. The AI text is written into the Confluence question page only when every page it used is in the question's space and none of them (or their parent pages) has read restrictions. Then anyone who can open the question page can read it, just like any other text on that page.
- When a source is restricted or in another space, AnswerLoop may try once to rewrite the answer from allowed pages only. If that isn't possible or safe, it warns the asker and saves the question without the AI text. If a site admin has turned on "include anyway" (it's off by default), the asker (or an expert posting a draft) can choose to include the text anyway; that choice is recorded and the text then follows the question page's permissions. An expert's answer that still mostly reuses such a draft follows the same rule, even after editing it. (A person can always type or paste what they already know into an answer; that is ordinary text, not an AI answer.)
- Not saved to the page. Inside AnswerLoop, other people see the AI text only if they can currently open every page it used. Otherwise they see the question and people's answers, without the AI text, plus the titles of the sources they can open and a count of the rest. The same check applies to search results, "already asked" suggestions and the question list. The FAQ macro is stricter: it shows AI text only when it may be shown to everyone who can open the question.
- Expert drafts. An expert sees a private AI draft only if they can currently open all its sources. The @mention that alerts an expert says a draft exists, never what it says.
- Duplicates. A moderator can merge two questions only within one space, and an asker can close their own question into an answered one in the same space. Merges only happen between question pages with the same read restrictions (their own and inherited from parent pages); otherwise AnswerLoop refuses and says why. The merged question's answers and comments move to the kept question page. Across spaces AnswerLoop only shows a link, and only to people who can open the other question; content never moves between spaces. (An asker can still close their own question in favour of an answered one in another space; their page becomes a pointer and nothing moves.)
- Exports are for space and site admins. They cover the questions the admin can open, and include account IDs and display names (JSON also includes the titles and links of AI sources that are in the question's space with no restrictions, and a count of the others; CSV doesn't), but AI text only where it may be shared with everyone who can open the question.
- Page metadata. Each question page carries an AnswerLoop page property with account IDs, comment text, source page IDs, and the titles and links of sources that are in the question's space with no restrictions, readable by anyone who can view the page. AI text in it is blanked when it can't be shared. From version 3.31.0 the property is signed: if anyone else edits it (or it hasn't been re-signed yet), a restore brings the question back without AI text, account IDs, the linked page, import records, the accepted answer, votes or comments, the asker becomes the page's creator, and "include anyway" consent is never taken from it.
- Who counts as a site admin. AnswerLoop asks Confluence, as the user, whether they have the global Confluence "administer" permission. Group names are never trusted. Site admins can change site and space settings, see stats, export, and ask, answer and moderate in every space they can view. Every request from AnswerLoop's own admin page (settings, stats, import, search index rebuild) is also checked on the server: AnswerLoop asks Confluence whether the caller has that permission and refuses the request if not, wherever it comes from.
- Space settings. Asking people, expert drafts and reminders re-check that the asker still has the ask role (or is a moderator), that AnswerLoop is on in the space and that the page hasn't moved. Turning AnswerLoop off in a space hides its questions and stops app actions there; it doesn't exclude that space's ordinary pages from AI answers for people who can view them.
- Imports. Imported pages get the space's permissions; page-level restrictions on the original questions are not copied.
- Rovo. AnswerLoop's Rovo agent runs every action as the person chatting, with the same checks. What it returns (people's answers and AI text that may be shared) goes to Rovo, Atlassian's AI, inside Atlassian.
- Stats. Site admins see counts, topics and top-helper names only for spaces they can open, plus a single total for questions in spaces they can't view. No question titles or text. Counts can include restricted question pages in spaces the admin can open. The import dry run is limited the same way, but may show one example title from a space the admin can open.
What the app stores
- Questions and answers, as Confluence pages and page properties in your site.
- In Forge's built-in storage for your installation: a copy of question, answer, comment and AI answer text (including the asker's original before any rewrite) for search and per-viewer checks, private expert drafts, a search index, duplicate-check results, import status, settings and usage counters.
- Atlassian account IDs of people who ask, answer, comment, vote, are asked or listed as experts, edit question pages directly, merge, close or dismiss duplicates, include AI text, run an import, have reminders waiting for them to open the app, or request AI answers (in usage counters, drafts and the last space they used, which expires after 180 days unused), plus the display names shown on question pages. No email addresses.
- Unsaved AI drafts for about 1–2 hours. Private expert drafts until the asked experts post or dismiss them, and at most 30 days after preparation or refresh. Usage counters for up to 40 days.
- When a question page is trashed, the app hides it and keeps its stored copy so it can be restored. From version 3.26.0, when the page is permanently deleted (purged from the trash), the app deletes everything it stored for it: the question, AI text, answers, comments, votes, expert routing, search index entries, duplicate-check results and drafts. Only an import record of page IDs is kept, so a re-import doesn't bring it back. A genuine deleted-page event is recorded before purging, and the hourly job retries failed cleanup. Access denied or a missing-page response by itself is not proof of deletion. If the event is missed, or a whole space is deleted without per-page events, stored copies are retained pending confirmed deletion rather than guessed to be gone. Spaces unreadable for 61 days are flagged in operational counts for review; loss of app access never by itself authorizes deletion.
- An AI usage log with timings and token counts, kept for 90 days. (Versions before October 30, 2026 also logged question titles and account IDs there; those fields were cleared from all existing rows on November 3, 2026.)
- The app is designed to log counts and page IDs only — not question text, page content or personal data.
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
- Saved copies don't update themselves yet. If AI text was saved into a question page and a source page is restricted or moved later, the saved text stays on the question page until it is edited or republished. AnswerLoop's own views re-check access each time, but the Confluence page itself is a copy, and like any Confluence page it keeps its history. We are working on automatic re-checks; until then, we don't promise instant removal.
- Titles in older page versions. Since version 3.36.0 (November 12, 2026), a source's title and link, and the title of the page a question is about, appear on the question page only when that page is in the question's space with no read restrictions; other sources are shown as a count, and AnswerLoop shows each reader the sources they can open. Question pages written before that version keep the earlier titles in their Confluence page history.
- Text people write or include. A person's own answer, or AI text an asker chose to include (when the admin allows it), is written onto the question page and readable by everyone who can open it.
- Exports and copies. Content already read, exported or copied elsewhere can't be recalled by a permission change.
- AI limits under load. Usage is checked before each AI call and counted after it, so requests at exactly the same moment can go slightly over a limit.
- Interrupted imports. If an import is interrupted, an item can be left partly imported; review failures before running it again.
How we check it
- An automated test suite (more than 170 tests) covers permission checks, including restricted sources, cross-space questions, admins and the asker.
- We use automated tests and targeted development checks with test users who have different access. Verification coverage and any incomplete live checks are recorded for each release.
- AnswerLoop has completed Atlassian's Marketplace privacy and security questionnaire.
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.