Confluence AI search across your company documentation
Runbooks, project decisions and internal guidance already live in Confluence. ChatDocument connects that knowledge to the rest of your company sources, so employees can ask a practical question and get a cited answer. Pages stay in Confluence, new and edited documents are picked up automatically, and source permissions determine what each person can see.
Turn the wiki into answers people can check
"What do we do when a customer reports a failed export?" may require the support runbook and a product decision recorded elsewhere. ChatDocument answers from the relevant company passages and links each sentence to its source.
| Department | Question from a colleague | Useful Confluence knowledge |
|---|---|---|
| Support | "What should I check before escalating this issue?" | Troubleshooting and escalation runbooks |
| IT | "How is temporary access approved?" | Access guidance and operating procedures |
| Operations | "Who owns the handoff after a project closes?" | Handoff process and ownership documents |
"Who needs to review a change to our access process?" should lead to the documented procedure. Employees ask in ordinary language, without reconstructing a page hierarchy or knowing who wrote the original guidance.
Keep your wiki as the place people write
Connect your Confluence knowledge and organize it into department spaces with owners. Support can maintain runbooks while IT keeps access guidance and Operations owns internal procedures. Employees ask within their department or across the spaces they can access.
- Google Drive1,248 files
- SharePoint and OneDrive862 files
- Confluence410 pages
- Notion196 pages
- Dropbox233 files
- Slack12 channels
- PDF, Word, Excel and PowerPoint uploads73 files
- Websites and help centers2 sites
The original documentation stays in Confluence. New and edited pages are picked up on their own, so authors keep updating the source. There is no separate assistant copy for a department to rewrite whenever a procedure changes.
Connect the other applications behind your processes too. A Confluence runbook can sit alongside a Drive handbook, SharePoint policies, Notion pages, Dropbox documents, Slack knowledge and a published help center in the same company workspace.
Keep the original passage beside the answer
Every sentence in a ChatDocument answer links to the document, section and space. Click a citation to open the passage and check its wording before following a procedure or sharing guidance with a colleague.
If the documents do not cover the question, ChatDocument says "not in your documents" and shows the closest passages it checked. An undocumented workaround remains a question for the owner instead of becoming an invented instruction. Answers follow the language of the question.
Trips over 500 dollars need written approval from your manager before booking.Travel Policy 2026, 1.2
Exceptions go to Finance with the trip details.Approval Guide, section 4
Keep restricted guidance inside its existing access rules
Source permissions are inherited from Confluence. Employees get answers only from documentation they can already open. A connected wiki does not make restricted pages available to everyone in the company workspace.
Private department spaces add a home for sensitive knowledge, with owners and members. The workspace uses admin, space owner, member and reader roles. Review permissions when organizing Confluence material alongside other company sources.
Use repeated questions to improve the wiki
Save useful answers for colleagues and verify recurring guidance with an owner, review date and version history. The source remains available when someone needs to check whether an instruction still matches the underlying documentation.
Business and Scale add knowledge gap detection. Unanswered questions are grouped for the right owner, and conflicting or outdated documents are flagged. Owners can use those signals to decide which runbooks need attention rather than relying only on informal requests.
The Slack and Microsoft Teams bot on Business and Scale brings answers from accessible Confluence knowledge into direct messages and channels. It links to sources and hands off to a person when the documents do not answer.
FAQ
Can we ask across Confluence and other sources?
Yes. ChatDocument connects company knowledge across sources while following existing permissions. Browse all integrations to see drives, wikis, Slack, document uploads, websites and help centers together.
Which plans include source connections?
Team includes 5 connected sources and 10 spaces. Business and Scale include all connectors with unlimited sources and spaces. Question and new page allowances apply to every plan. See pricing for the limits.
Does connecting our wiki allow model training?
No. Your documents are never used to train models. AI model providers are bound by contract not to train on your content. Read security for encryption and deletion controls.
Make maintained guidance easier for the whole team to use
Connect Confluence to your company workspace and let employees move from a question to the passage behind the answer.