Connect a Confluence Source so Dosu can index your existing spaces and pages and use that documentation to answer questions and keep knowledge current. This page covers what connecting Confluence gives you, what you need, how to connect, and what Dosu does with the content.
What connecting Confluence gives you#
Confluence is where many engineering organizations keep architecture notes, runbooks, onboarding guides, and decisions. Connecting it as a Source pulls that knowledge into a Library so it shows up in Dosu answers (in Chat, GitHub, and Slack) and in the context served to coding agents over the MCP Server and CLI.
Confluence also works as a destination. Dosu can sync a Document to Confluence and update existing pages directly when code ships, so your wiki reflects the codebase as it is today, not six months ago. Page structure, formatting, and organization are preserved.
Availability and prerequisites#
- Beta. The Confluence Source is in Beta. Behavior and limits may change.
- Teams plan. Confluence requires the Teams plan. See pricing or contact Dosu about plans.
- A Library to hold it. Sources live inside a Library. Open or create one at Libraries.
- Confluence access. You authorize with an Atlassian account, and the spaces Dosu can read are determined by that account's permissions. To control exactly what gets indexed, create a dedicated Confluence service account with access only to the spaces you want Dosu to see, then authorize with that account.
How to connect#
- Open or create a Library, or start a new one at create a Library.
- Add a new Source and choose Confluence.
- Choose an authentication method. Dosu supports three:
- OAuth (Recommended). Sign in with your Atlassian account and grant Dosu read access. This works best for most Confluence users.
- Email + API Token. Connect with your Atlassian email and an API token. Useful when OAuth is not available.
- Scoped API Token. A token with fine-grained scopes for tighter access control. Dosu shows the exact read scopes to select (and the write scopes needed for sync-back) when you choose this method.
- After you authorize, select which Confluence spaces to index.
Any member of your organization can view and select spaces from a connected Confluence workspace.
What Dosu does with it#
- Indexes pages. Dosu indexes current, published pages from global, collaboration, and knowledge base spaces.
- Keeps the index fresh. Dosu checks your Confluence content for changes about every five minutes. New and updated pages are indexed automatically, and deleted pages are removed.
- Serves the knowledge. Indexed pages become answerable in Dosu and available to coding agents alongside your other Sources.
- Updates pages when code changes. When a change ships, Dosu can update the affected Confluence pages directly. You control this with the Auto-Accept Review setting on the Library. You can leave it off, and updates go through Review first, or turn it on to apply updates automatically.
Notes and limits#
- Not indexed. Attachments, archived pages, draft pages, and trashed pages are not synced. Personal and system spaces are excluded.
- Access is org-wide once connected. After a Confluence workspace is connected, every member of your Dosu organization can query data from the connected spaces, regardless of their individual Confluence permissions. This is why a scoped service account is the safer choice for authorization.
- Reauthorization. If your Atlassian authorization expires, Dosu stops syncing and notifies the organization's owners and admins via email. You will also see a prompt to reconnect. Reauthorize promptly so your documentation stays current.
- Public Libraries. Sources connected to a Library set to public visibility become queryable by anyone. Only connect Confluence to a public Library if that content is meant to be public.