Seller field guide · 3 min read
Can your company license its Confluence knowledge base?
A company-owned Confluence collection can be assessed when it documents real procedures and the company has rights to the included content. Define a set of spaces and documents around a business process. Export format matters because readable pages and the discussion around them are not always preserved together.
Check comments and permissions in the selected format
Atlassian documents several Confluence export formats. Its guide states that PDF exports omit comments and that HTML exports do not currently include page comments; it also describes permission-dependent differences in space exports.
Inspect an allowed page whose discussion changes how the procedure should be interpreted. A visually complete PDF may still omit a correction or exception recorded in comments. Keep the source’s revision context and distinguish missing discussion from a document that never had it.
Source notes: Atlassian: export a Confluence space
Connect policy with evidence of its use
A procedure explains what a team should do. A related incident or project record may explain what the team actually did. For evaluation, identify that connection explicitly instead of presenting a collection of policy pages as proof of operational execution.
Separate company-authored guidance from copied vendor manuals, client specifications and licensed training material. A page can mix these sources in a single section. Record the source and ownership of each component rather than making a blanket claim based on the space owner.
Choose a defensible evaluation scope
This is our suggested scoping framework, not a statement that a buyer accepts every record below. Review contractual rights and the intended use before preparing a sample. Technical access to a record does not establish permission to license it.
| Record or context | What to evaluate | Boundary to keep |
|---|---|---|
| Internal runbook | Steps, exceptions and decision criteria | Remove environment secrets and copied restricted material |
| Decision or postmortem page | Reasoning, outcome and lessons | Exclude confidential customer incidents and security detail |
| Page comments or linked tickets | Corrections and application context | Verify availability and rights separately from the page body |
Make the document collection interpretable
Prepare an index showing each document’s purpose, owner and applicable period. Mark superseded guidance and broken links. A buyer should be able to tell which policy was in effect for a worked example, rather than guessing from the latest edit date.
Ask whether the buyer needs clean prose, page hierarchy, versions or links to operational records. Export only the allowed elements that support that purpose. Retain a record of excluded spaces so a later update does not accidentally broaden the dataset.
Illustrative scenario · fictional company
Confluence: a fictional scoping example
A fictional IT operator selects its internal Confluence runbooks and a small set of permitted postmortems. Customer diagrams, access details and vendor manuals are excluded. The team finds that a PDF export omits comments containing a correction, so it labels the missing context and supplies a separately reviewed correction note from the source. It keeps superseded procedures visibly marked and does not represent the current page as the policy used years earlier.
When to pause or narrow the scope
Client work and customer files are excluded from this starting scope. Assess company-owned internal records separately from personnel, health, privileged or NDA-restricted material.
- The space is mainly copied or client-owned documentation.
- Secrets and sensitive incident details cannot be separated from the useful explanation.
- Missing comments or versions would make the procedure misleading.
Your preparation checklist
- Define an allowlist of firm-owned spaces and pages.
- Inventory copied material and confidential references.
- Test export formats against a page with comments.
- Mark superseded procedures and version gaps.
- Provide a document index and scoped evaluation terms.
Start with a description of the records. The quote form does not ask you to upload a dataset.
Discuss your dataSources and further reading
- Atlassian: export a Confluence space · Checked October 26, 2026
This is general information, not legal advice or confirmation that a buyer will accept your records. Published buyer ranges describe their programs, not an offer for your dataset. Buyers may pay QuoteMyData when a deal closes; see how we are paid.
