Confluence

At a glance

Confluence Cloud is a team wiki for turning meeting notes, decisions and instructions into organized, linked pages with version history. It is worth considering when shared documents need a maintained home, especially beside Jira work. Spaces group related material and page trees give it structure. Free supports a small team, but cannot restrict access to individual content; plan choice matters before confidential documents arrive.

Good fit

Teams willing to maintain a shared knowledge base rather than leave answers scattered across chats and files. A page has a draft and publishing step; a live doc makes edits visible immediately. That choice suits different work: a reviewed operating procedure benefits from deliberate publication, while a working note may not. Agents can use the REST API or official Atlassian MCP Server to read and update permitted content. This does not grant access beyond the authorized user’s permissions.

Consider something else when

You want a local notebook, a plain-file repository or free access controls for separate confidential groups. The content-permissions documentation explicitly excludes restrictions on Free; open access within a space does not mean automatic public internet access. Self-managed Confluence Data Center is a separate product with new-customer sales ended and a scheduled March 2029 end of life, so it is not a durable new self-hosting route.

Start here

Before adding team material, have an administrator review sharing and data-contribution settings. With an authorized account, create a space for one real task, then choose Create and Page for a document that needs review before publication. Use a template or write a short procedure, check location and access, then publish. Success is a page your intended readers can find in the tree and search, not a large empty space. Create Space and Add content permissions are prerequisites. This workflow is documented; no page was created during the review.

Cost and requirements

On 31 October 2026, the public calculator at ten users showed Standard at $7.15 per user per month, or $720 per year for the annual one-to-ten-user tier. These are different billing bases. Monthly billing uses the highest seat count during the cycle; removing users mid-cycle does not reduce that bill. Free lists ten users and 2 GB file storage. Guard SSO/provisioning may add a separate subscription outside Enterprise. Some MCP queries consume Rovo credits; model-client costs and organizational allowances are separate from a wiki seat.

Limits to know

The trial changed the public pricing calculator, not a working wiki. Before uploading team material, review Security, Data contribution in organization administration: the highest active plan sets defaults. Free/Standard organizations default in-app content contribution on, with an opt-out; metadata contribution cannot be disabled outside Enterprise where these settings apply. Compliance-specific defaults can differ. Export is documented in Word/PDF and space data formats, but permissions or admin policy can block it and formats omit some content. Test a representative export before relying on it; editing, search quality, API/MCP access and export fidelity were not exercised.

Related work

• Atlassian MCP Server: agent access to permitted wiki content (complement)
• Jira: work tracking that can sit alongside the wiki (complement)