> For the complete documentation index, see [llms.txt](https://docs.bito.ai/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.bito.ai/ai-architect/integrating-ai-architect-with-your-tools/integrating-with-confluence.md). # Integrating with Confluence Your team's documentation lives in Confluence — design decisions, RFCs, runbooks, acceptance criteria, architecture notes. [**Bito's AI Architect**](/ai-architect/overview.md) reads that documentation and uses it as context whenever it analyzes Jira tickets, answers questions in Slack, or generates implementation plans. And it can write back to Confluence too — creating pages, updating content, adding labels, leaving comments, and managing attachments — all from inside Jira or Slack, without ever switching tabs. Once you connect Confluence, AI Architect treats it as a first-class context source alongside your code, Jira tickets, and team conversations in Slack. ## What AI Architect does with Confluence ### Pulls Confluence into analysis as context * **Automatic context on Jira plans** — When AI Architect generates an implementation plan for a Jira Epic or Story, any Confluence pages linked to that ticket are pulled in automatically. Recommendations, risk assessments, and effort estimates reflect what's already documented. * **Reads page attachments** — Attachments on Confluence pages are read along with the page content, so design specs, requirement docs, and reference data attached to a page all factor into the plan. * **Surfaces information in Slack** — When you paste a Confluence link into a Slack thread, the [Bito AI Assistant for Slack](/ai-architect/integrating-ai-architect-with-your-tools/integrating-with-slack.md) reads the linked page and uses it to answer questions, summarize, or compare against the discussion. ### Lets you manage Confluence from Jira and Slack You can ask AI Architect — through Jira comments or Slack — to create and maintain Confluence content for you. **Supported operations:** | Operation | What you can ask | | --------------------- | ------------------------------------------------------- | | **Create page** | Create a new Confluence page in a given space | | **Update page** | Edit the body or title of an existing page | | **Add labels** | Add labels to a page for findability and categorization | | **Read comments** | Read both footer and inline comments on a page | | **Add comment** | Add a footer comment to any page | | **Upload attachment** | Attach a file (design mock, spec, CSV, etc.) to a page | | **Delete page** | Delete a page programmatically | No browser tab required — the same Jira ticket or Slack thread where you're already working can drive your wiki. #### Supported attachment formats When AI Architect reads attachments from Confluence pages (whether for context or when you ask about a specific file), the following formats are supported: * `.pdf` * `.docx` * `.xlsx` * `.csv` * `.json` * `.yaml` * `.zip` …and other common document formats. ## Setup {% stepper %} {% step %} ### Enable AI Architect for your workspace AI Architect can be set up using one of the following deployment options: #### Bito-hosted AI Architect is managed and maintained by Bito. * Follow the [Bito-hosted installation guide](/ai-architect/installation/install-ai-architect-bito-hosted.md) to get started. * If AI Architect isn't already active for your workspace, contact the Bito team at to enable it. #### Self-hosted AI Architect is deployed and managed within your own infrastructure. * Follow the [self-hosted installation guide](/ai-architect/installation/install-ai-architect-self-hosted.md) to set up and configure AI Architect for your workspace. {% endstep %} {% step %} ### Connect Bito with Confluence 1. In your Bito dashboard, go to the [**Manage integrations**](https://alpha.bito.ai/home/cra-integrations) page. 2. Under **Available integrations**, find **Confluence** and click **Connect**.
3. Click **Authorize with your Confluence account**. You will be redirected to Atlassian's site to grant Bito access to your Confluence workspace. This uses OAuth to securely link your Confluence content.
4. Review the requested permissions and click **Accept**.
5. After successful authorization, Bito will display a list of spaces from your Confluence site that Bito has access to.
{% endstep %} {% endstepper %} {% hint style="info" %} **One Confluence connection covers all workflows.** Once Confluence is connected to your Bito workspace, AI Architect will use it everywhere — in Jira ticket analysis, in Slack threads, and when you ask it to write back to Confluence. {% endhint %} ## How to use AI Architect with Confluence #### Get richer Jira plans automatically If you've already linked a Confluence page to a Jira ticket — for example, an RFC, design doc, or product brief — there's nothing more to do. When AI Architect generates a plan for that ticket, it reads the linked Confluence pages (and their attachments) and folds them into the analysis. **Example:** A Story links to a Confluence page that documents the team's preferred retry strategy. AI Architect's plan will reference that strategy directly, instead of suggesting a generic approach. [**Learn more about Jira integration**](/ai-architect/integrating-ai-architect-with-your-tools/integrating-with-jira.md) #### Reference Confluence pages in Slack Paste a Confluence URL into a Slack thread and ask AI Architect about it. **Examples:** ``` @Bito summarize this Confluence page and tell me what's missing [Confluence link] @Bito does the approach in this design doc conflict with PROJ-456? [Confluence link] ``` The Bito AI Assistant reads the page, factors it into the thread context, and responds with answers grounded in your documentation. [**Learn more about Slack integration**](/ai-architect/integrating-ai-architect-with-your-tools/integrating-with-slack.md) #### Create and update Confluence pages from Jira Ask AI Architect to write to Confluence directly from a Jira ticket comment. **Examples:** ``` @bito create a Confluence page in the "Engineering" space summarizing the implementation plan above @bito update the linked Confluence page with the decisions made on this ticket @bito add the label "post-mortem" to the linked Confluence page ``` #### Create, update, and manage Confluence pages from Slack The same operations work from Slack threads. **Examples:** ``` @Bito create a Confluence page in the "Platform" space documenting the conclusions from this thread @Bito leave a comment on this Confluence page noting that the API contract changed: [Confluence link] @Bito attach this file to the linked Confluence page @Bito delete the stale Confluence page at [Confluence link] ``` ## What AI Architect knows about your team Once Confluence is connected, it becomes one of several context sources AI Architect uses: * **Your codebase** — All your repositories, services, API endpoints, modules, and design patterns are indexed into a knowledge graph. * **Your Jira/Linear history** — Recurring patterns from past tickets: race conditions, fragile services, security gaps, error-handling issues. * **Your Confluence documentation** — RFCs, design docs, runbooks, acceptance criteria, and any attached specifications. * **Other context sources** — Slack threads, observability data, and custom instructions you provide. [**Learn how Bito builds the knowledge graph**](/ai-architect/knowledge-graph.md) ## Permissions required for Confluence integration When you connect Confluence, Bito requests access to your Atlassian account via OAuth. The integration requests **read**, **write**, and **delete** permissions across Confluence content so AI Architect can both pull pages into analysis and act on them when you ask it to. #### Summary of access: | Capability | Scope | | ---------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | | **Delete** | Comments, Custom content, Page, Content attachments, Blogposts, Database, Smart Link, Folder, Whiteboard | | **View** | Comments, Custom content, Page, App Properties, Content attachments, Blogpost, Content metadata, Content Property, email-address, Smart Link, Groups, Contents, Inline tasks, Labels, Task, Space permissions, Space properties, Space settings, Space details, Task, Content templates, User properties, User details, Content watchers, Whiteboard, Database, Folder, Content restrictions | | **Update** | Comments, Custom content, Page, App Properties, Content attachments, Labels, Space details, Content templates, Content watchers, Blogpost, Content Property, Content restrictions, Database, Smart Link, Folder, Inline tasks, Whiteboard | #### Full list of permissions requested: **Delete** * Delete comments on content. * Delete custom content. * Delete pages. * Delete attachments. * Delete blogposts. * Delete databases. * Delete Smart Links. * Delete folders. * Delete whiteboards. **View** * View comments on pages or blogposts. * View custom content. * View page content. * Read connect app properties data * View and download attachments of a page or blogpost that you have access to. * View blogpost content. * View information about the content. Note that this does not provide access to the content itself. * View properties associated with a content. * View email addresses of all users regardless of the user's profile visibility settings. * View Smart Link data, such as its content id and title * View details about groups including its members. * View children or descendants for hierarchical content, including pages, whiteboards, databases, folders and smart links * Search and view inline tasks. * View labels associated with the content or space. * View content restrictions and space permissions. Note that is only used for V2 APIs * View space permissions. * View properties associated with the space. * View space settings and themes. * View space details * View Confluence tasks. Note that is only used for V2 APIs * View content templates. * View properties associated with the user. * View user details. * View the watchers associated with the contents, spaces or labels. * View whiteboard data, such as its content id and title * View database data, such as its content id and title * View folder data, such as its content id and title * View the restrictions on the content. **Update** * Create and update comments on content. * Create and update custom content. * Create and update pages. * create, modify and delete app properties data * Create and update attachments. * Add and remove labels associated with the content or space. * Create and update spaces. * Create, update and delete content templates. * Add and remove the watchers associated with content, spaces, or labels. * Create and update blogposts. * Create, update and delete properties associated with a content. * Update the restrictions on the content. * Create and update databases. * Create and update Smart Links. * Create and update folders. * Mark inline tasks as complete or incomplete. * Create and update whiteboards. {% hint style="info" %} AI Architect only acts on Confluence content when you ask it to (via Jira or Slack) or when a page is linked to a ticket it's analyzing. It doesn't make changes on its own. {% endhint %} ## Troubleshooting #### AI Architect's Jira plan doesn't reflect my Confluence docs **Check:** 1. Is Confluence connected in [**Manage integrations**](https://alpha.bito.ai/home/cra-integrations)? 2. Is the Confluence page actually linked to the Jira ticket — either via a link in the ticket description/comments, or via the *Jira Issue* macro on the Confluence page? 3. Does the OAuth user used to connect Confluence have access to the page in question? Bito sees only what that user can see. #### AI Architect can't read an attachment **Check:** 1. Is the attachment in a supported format (`.pdf`, `.docx`, `.xlsx`, `.csv`, `.json`, `.yaml`, `.zip`, or similar)? 2. Is the attachment under your Confluence instance's size limits? #### Authorization errors If Bito reports that it can't access Confluence: 1. Go to [**Manage integrations**](https://alpha.bito.ai/home/cra-integrations) and reconnect Confluence. 2. Confirm the Atlassian account used has access to the spaces and pages you expect AI Architect to read or write to. #### My Confluence instance is self-hosted (Data Center) Confluence Data Center is **not yet supported**. Support for self-hosted Confluence is coming soon for both Bito-hosted and Self-hosted AI Architect. In the meantime, contact to be notified when it's available. ## Frequently Asked Questions #### Does AI Architect read every page in our Confluence? No. AI Architect reads Confluence pages on demand: * Pages **linked to a Jira ticket** it's analyzing * Pages **referenced by URL** in a Slack thread where it's mentioned * Pages you explicitly ask it to read, create, update, or delete It does not crawl or index your full Confluence instance. #### Can I limit which spaces AI Architect can access? Yes — at the Atlassian/Confluence level. The OAuth user used to connect Confluence to Bito determines what AI Architect can see. Restrict that user's space access in Confluence to control what's reachable. #### Does AI Architect modify Confluence pages without asking? No. Write and delete operations happen only when you explicitly request them through a Jira comment or Slack message. ## Next steps 1. **Connect Confluence** to your Bito workspace via [**Manage integrations**](https://alpha.bito.ai/home/cra-integrations). 2. **Link your design docs and RFCs** to the Jira tickets that reference them — AI Architect will pick them up automatically when you ask it to generate implementation plan. 3. **Try writing back from Slack or Jira** — ask AI Architect to create a Confluence page summarizing a thread or ticket, and see how it reads. 4. **Combine with** [**Jira**](/ai-architect/integrating-ai-architect-with-your-tools/integrating-with-jira.md) **and** [**Slack**](/ai-architect/integrating-ai-architect-with-your-tools/integrating-with-slack.md) **integrations** for the full workflow: plan in Jira, discuss in Slack, document in Confluence — all driven by AI Architect. --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter: ``` GET https://docs.bito.ai/ai-architect/integrating-ai-architect-with-your-tools/integrating-with-confluence.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.