Knowledge workspace / PRODUCT DOSSIER

Confluence Cloud

Team documentation organized into spaces, published pages and live documents.

Investigation: Where should a small team keep shared knowledge? →

Official website ↗Explore in graph →9 cited claims ↓

Confluence Cloud with the space features enabled; excludes Data Center and Marketplace apps. · Not established · Atlassian Customer Agreement for cloud products; no open-source platform license established.Revision 2026-09-15.1 · unreviewedNeeds recheck · recheck 2026-10-150 attestations · checked 2026-09-15

What we do not know yet · 3 open gaps

Which client versions, plan and administrator policies apply to the team?
What survives a representative export: links, attachments, comments, permissions and history?
How do simultaneous edits, temporary disconnection and member departure behave on the chosen setup?

Applies to: Living documentation accessed 2026-09-15; pin plan, client, deployment and tenant policies before use. · Confluence Cloud with the space features enabled; excludes Data Center and Marketplace apps.

Applicability, 2 recheck triggers & verification plan

Applicability

Living documentation accessed 2026-09-15; pin plan, client, deployment and tenant policies before use.

Confluence Cloud with the space features enabled; excludes Data Center and Marketplace apps.

Excludes: Executed collaboration, recovery or migration tests; Unlisted third-party plugins and integrations; AI quality, security certification and performance rankings; Unlisted editions and plan entitlements

Recheck when

Changes to app versions, plan entitlements, sharing policies or license terms.
Changes to offline caching, synchronization, recovery retention or export formats.

Needs recheck · due 2026-10-15

Verification plan

Use the small-team-knowledge investigation to specify the required collaboration and access boundaries.
With explicit authorization, create an isolated synthetic workspace and named test accounts; do not invite real colleagues or upload private knowledge.
Test editing, viewer restrictions, recovery and export with pinned clients and plan; retain sanitized artifacts before drawing conclusions.

Provenance & review

Testedknowhow collaboration research

Commissioned by a Nimbalyst maintainer. Public-source synthesis; no independent review or product execution.

Revision 2026-09-15.1 · unreviewed · checked 2026-09-15

0 attestations · Content: Unlicensed prototype; redistribution decision pending

Capability claims · 9 / 17 sourced

Standing condition: these are documentation claims at the source capture date, with outcome “claimed”; no runtime execution is recorded. Dossier applicability and limitations apply throughout. Expand a row for its statement, specific scope and contradictions. Numbered citations resolve to the source locator and capture date below. Missing evidence means Unknown, not No. Sources are unpinned unless marked “Pinned”; this marks source stability, not stronger support or runtime verification. Reuse counts refer to claims in the full dossier; repeated citations do not represent independent sources.

Yes Documented within scope Partial Limited form of the feature No Explicit evidence of absence Unknown No evidence recorded. These are support assessments, not quality scores or runtime verification.

Collaboration

Document authoringYes

Explore Document authoring →

Authors pages, live docs and blog posts.

Scope: Content type changes draft and publication behavior.

[1]

Live co-editingYes

Explore Live co-editing →

Supports simultaneous edits to live docs.

Scope: Live docs must be enabled in the space; documented limit is 40 editors.

[2]

Shared knowledge spaceYes

Explore Shared knowledge space →

Organizes shared written content in spaces.

Scope: Cloud space access applies.

[1]

Comments or discussionsYes

Explore Comments or discussions →

Supports inline comments on written content.

Scope: Draft comments are visible within the editing session; unresolved comments become visible on publication.

[1]

Access control

Distinct collaborator rolesYes

Explore Distinct collaborator roles →

Configures member permissions at space level.

Scope: Plan, groups and administrator configuration apply.

[4]

Per-document accessYes

Explore Per-document access →

Can restrict access to individual pages.

Scope: Space permissions and page restrictions combine.

[3]

External collaboratorsYes

Explore External collaborators →

Provides guests access to one assigned space.

Scope: Guests have feature restrictions; anonymous spaces can broaden accessible content.

[3]

Continuity & portability

Version recoveryYes

Explore Version recovery →

Stores and restores earlier live-doc versions.

Scope: Snapshots finalize after an editing session; no recovery run recorded.

[2]

Portable contentYes

Explore Portable content →

Exports content as Word, PDF or supported data formats.

Scope: Format, content type and export permissions determine coverage.

[5]

Unknown · 8 capabilities without evidence

Interface images & local attachments

Screenshots & attachments

Image index

Official project screenshots and your own reference images. Images illustrate a UI; they do not verify feature behavior. Uploads stay in this browser.

No screenshots gathered yet.