By Atlassian

Confluence

What it does

Confluence Cloud is Atlassian’s shared knowledge workspace. A team creates a space for a project or knowledge base, builds pages or live docs inside it, and lets others find the resulting information through the content tree and search. This profile covers the Cloud service; check Data Center separately.

Its strongest distinction is the choice between a page that can be drafted and published, and a live doc where collaborators see changes as they happen. Whiteboards and databases provide other ways to plan and organize material in the same workspace.

Last updated
Oct 21, 2026
Confluence · Editorial illustration
Conceptual paper-and-clay illustration of loose knowledge pages organized into folders and found through search.

Work at Confluence?

Help customers find accurate information about your software.

Manage this listing →

Find your fit

Who it is for

A team maintaining policies, onboarding notes or technical knowledge can organize its material in a dedicated space. Pages suit reviewable information that should be published and revised over time; the version history helps trace later changes.

A project team taking meeting notes or shaping a plan together may prefer live docs and whiteboards. Live docs show edits without a separate publish step, so agree on an editing and review convention before treating one as an approved policy.

Teams with structured lists alongside narrative documents can consider databases. They live in the content tree and use fields and entries, but access follows space permissions rather than a separate database permission model.

Back to sections

The work it supports

Core capabilities

Start by creating a space for a team, initiative or knowledge base. Confluence offers collaboration, knowledge-base and custom space purposes. The selected purpose shapes the starting setup; available access schemes depend on plan and administrator rights.

Write a page when you need a draft, deliberate publication and later version comparisons. Write a live doc when immediate collaboration is more useful. Pages and blog posts can hold unpublished drafts; live docs cannot. This distinction matters for policy or customer-facing material that needs review before others see it.

Space administrators can make reusable templates with variables and placeholder instructions. That can keep meeting notes, decision records or recurring documents consistent while still allowing the author to fill in the actual content.

Readers can use quick search or advanced search, then narrow results by space, content type, contributor, modification date and labels. A useful trial is to check whether people can locate a specific published page from the terms they naturally use.

Whiteboards add visual planning inside Confluence Cloud, while databases provide structured fields and entries for material that does not fit a prose page. Whiteboard limits and controls vary by tier, and Atlassian excludes both whiteboards and databases from Government environments.

If Confluence is connected to Jira, a page or live doc can display Jira work items. That can put project status beside written context; confirm the connection and viewer permissions before relying on a linked page as a shared status view.

Back to sections

Understand the offer

Pricing and getting started

Atlassian lists Free, Standard, Premium and Enterprise for Confluence Cloud. Standard adds configurable space and page permissions that the Free plan lacks. Choose a tier by the access controls the team needs, especially if a space must contain material with different audiences.

Premium advertises more administrative controls, page and space insights, and automation. Verify the exact entitlement, limits and site configuration before budgeting around these advanced functions.

The billing documentation covers plan changes and monthly or annual subscription choices. This profile does not state a numeric price because the public pricing page was not reliably retained; check the current quote for user count, billing term and any add-ons.

Back to sections

Look a little closer

Before you choose

Map one real knowledge workflow before rollout: choose a space purpose, create a draft page, review it, publish it, then have a second reader find it. Confirm who can create spaces and who can see the published page under the intended plan.

Decide which material needs draft and publish control and which can evolve openly as a live doc. Restore or compare a sample page version to understand what the history preserves before using it for controlled documentation.

If visual planning, databases or Jira-linked views are central, test those specific paths with the intended plan and environment. Check whiteboard limits, database access and the connected Jira permissions rather than assuming every reader has the same view.

Evaluate Confluence Cloud separately from a Data Center deployment. Confirm current plan features and AI availability for the intended account; this profile makes no promise about AI credits, regional rights or a numeric subscription price.

Back to sections

11 distinct sources behind this profile. Research observed Oct 21, 2026. Features and offers can change.
View sources and research →

Help keep this profile useful

Spotted an outdated detail? Send the correction with a supporting source. A verified account is needed to submit.

Suggest a correction ↗