Confluence
Also known as: Atlassian Confluence, team wiki
Confluence is a collaborative documentation and wiki tool from Atlassian, designed for teams to create, organize, and search internal knowledge.
Pages are organized in Spaces (usually per team or project), with parent-child page hierarchies. Confluence integrates natively with Jira, making it the standard documentation layer in Atlassian-ecosystem engineering organizations. Business teams also use it for policies, handbooks, and process documentation.
Confluence, explained at three levels
At home
Confluence is like a shared website that your company builds and maintains internally. Instead of emailing policy documents or storing procedures in a file drive, teams write them as Confluence pages. Anyone at the company can search for and find the information they need -- like a Wikipedia just for your organization.
At work
In companies that use Jira for project tracking, Confluence is usually the companion tool where the documentation lives. A sprint's technical design decisions get written in a Confluence page. The company's onboarding guide is a Confluence page. Meeting notes from last week's planning session are in Confluence. It's the place for written information that doesn't belong in a ticket.
At home
Confluence pages live in Spaces (like sections of a website), and each Space has a tree of pages and child pages. You can @mention colleagues in a page comment, link to Jira tickets, and embed macros that display dynamic content like ticket status or roadmap progress. The page editor supports text, tables, code blocks, images, and embedded Jira issues.
At work
Confluence's Jira integration is its strongest feature for engineering teams: you can embed a live Jira issue list in a Confluence page, so the status of linked tickets updates automatically. This allows a project charter page that always shows current sprint status. Page restrictions let teams control who can view or edit sensitive pages. Templates give new pages a starting structure for formats like meeting notes, project specs, and retrospectives.
At home
Advanced Confluence users use labels to cross-tag pages across different Spaces and build content reports using the Content Report Table macro. Page watching sends email notifications whenever a followed page is updated. The Confluence REST API allows programmatic page creation -- for example, automatically generating a Confluence project charter when a new Jira project is created.
At work
Enterprise Confluence deployments manage permissions through Space-level and page-level restrictions, group memberships synced via SCIM, and audit logs for compliance. Confluence Data Center provides horizontal scaling for large organizations. Atlassian Intelligence features allow summarizing long pages, generating first drafts from a prompt, and identifying related pages. Content governance requires regular archiving of stale spaces, a clear Space governance policy, and search optimization -- page titles and labels matter more than content for Confluence search.
Real-world examples
At home
Thomas joined a new company and used Confluence to onboard himself. The HR space had an onboarding checklist page, the Engineering space had architecture diagrams and runbooks, and the Product space had the roadmap and feature specs. He found answers to most of his first-week questions without asking anyone.
At work
Aisha's engineering team used Confluence for all their technical documentation. Every feature had a design doc page linked to its Jira Epic. Before the sprint, the tech lead wrote the technical spec in Confluence, developers commented on it to ask clarifying questions, and the final design was approved before a single line of code was written.
Common confusions
- Teams assume Confluence is suitable for regulated document control — Confluence is a wiki -- great for living documentation that evolves over time, but not a document control system. It does not enforce formal approval workflows, does not maintain a tamper-evident audit trail, and is not compliant with ISO 9001 or FDA 21 CFR Part 11 document control requirements. For regulated industries, use a proper document management system (Veeva, Qualio, SharePoint with document control configurations) instead.
- Many expect Confluence search to work like Google — Confluence search prioritizes page titles, labels, and headings over body text. A page with the exact phrase buried in the middle of a long document will rank below a page whose title matches the search term. Good Confluence information architecture requires descriptive page titles and consistent labelling -- a badly named page is effectively invisible in search.
- People think Confluence pages update automatically when processes change — Confluence pages reflect what someone wrote at a point in time. They become stale quickly without a page owner and a review schedule. Many Confluence spaces accumulate pages that are years out of date but still appear in search results. Building a page ownership and review process into team norms is the only way to keep a Confluence space accurate.
For analysts
When assessing a client's Confluence instance, look for three common failure modes: spaces that haven't been updated in over a year (stale knowledge), spaces with no clear owner (governance gap), and a home page that doesn't help anyone navigate the space (poor information architecture). These three issues account for most 'Confluence doesn't work for us' complaints.
History & origin
Atlassian launched Confluence in 2004 as an enterprise wiki. It grew as companies adopted it alongside Jira, becoming the default place to write documentation explaining the work tracked in Jira. Confluence competed with Microsoft SharePoint and later with tools like Notion and Coda. Atlassian migrated Confluence from on-premises servers to Confluence Cloud during the 2020s. Atlassian Intelligence (AI) was added to Confluence in 2023 for page summarization and content generation. Confluence remains the dominant enterprise wiki for organizations running Jira.