IT systems · Practical guide

Validating Confluence for GxP: controlling SOP versions, approvals and use

Where staff use Confluence to find the effective GMP SOP, version, approval and availability at the workstation must agree. Distinguish Cloud, Data Center and added apps, including the scope of native approvals. In a small or medium-sized company, check the actual workflow with document owners, QA and IT. Publication alone does not make a page an effective controlled instruction.

Table of contents

At a glance

Can Confluence be used for controlled GMP SOPs?

Confluence can support controlled GMP documents when the configured process demonstrably provides the required controls. Page versions, permissions and native approvals on certain cloud plans can contribute. Check which version is approved and effective, who can change it and how users recognise the current version. Include acknowledgements, retention and any additional apps in scope.

  • Separate published pages, professionally approved editions, and active SOPs.
  • Native cloud releases are tariff- and content-type dependent; they are not a one-size-fits-all signature solution.
  • A page view does not yet prove any documented information or training.
  • Check, in addition to the visible SOPs, release certificates, historical logs, and used apps.

1. Knowledge repository or critical SOP retention?

Start with a clear decision: Is Confluence an informal knowledge repository, a editorial work area, or the binding source for completed GMP activities? A page containing a process description may assume all three roles. The key factor is the intended use and the actual practice within the organization.

For guided SOPs, describe the life cycle from creation and testing to effectiveness, modification and cancellation. Specify where the relevant text is located and which system retains the proof of release. If only controlled documents from another system are displayed, up-to-dateness and clear assignment of this display are part of the scope of inspection.

This article covers GMP for human medicinal products. EU GMP Chapter 4 addresses documentation, and Annex 11 provides guidance on computerised systems in this context. FDA requirements under 21 CFR Part 11 apply where the records or signatures concerned fall within its scope. The Confluence product name alone establishes no blanket validation obligation, and a vendor statement does not grant regulatory approval.

Sources: [9] [8] [10] [11]

2. Document the actually available product combination

The focus is on Confluence Cloud in the documented source state of October 6, 2026. Cloud is to be distinguished from self-operated Confluence Data Center. Document for your environment Tariff or installed version, content types and additional apps. A feature description in the cloud documentation does not prove availability in Data Center.

Atlassian describes native page approvals for Premium and Enterprise editions, covering pages, not Live Docs or blog posts. This means the general statement "approvals are only available via the Marketplace app" is inaccurate. Similarly, treating this feature as a complete, ready-to-use pharmaceutical SOP process without further evaluation would be incorrect.

Product and content limits for SOP planning
ComponentDocumented demarcationTask
Cloud Side Draft and publication with version history Define which stage is professionally significant.
Cloud Live Doc Changes appear without a classical publication step Do not assume the same SOP procedure as for the side.
Native Cloud Release Premium/Enterprise; only pages Testing tenant availability and intended release rules.
Data Center Version- and environment-specific dedicated environment Record installed functions and separate storage.
Marketplace-App Extended functional and data scope Assign manufacturers, licenses, data flows, and traceability evidence.

Sources: [1] [2] [7] [14]

3. Distinguish page version, release and validity

Confluence Cloud maintains version history for each page upon publication. A restored earlier version is automatically designated as the new current version. Individual versions may be deleted; therefore, version history does not equate to an immutable archive. Additional retention guidelines for older versions are specified in the currently accessible data center documentation.

Your SOP requires professional identification: document number, responsible department, approved version, and date of validity. The technical version number may assist but does not replace this assignment. Where multiple SOPs or dynamic content converge on a single page, it must remain clear which components are part of the approved version.

Therefore, also review annexes, linked worksheets, and embedded content. An unaltered page title does not prove that the complete package remains unchanged. Define which changes require a new technical review and how the reviewed combination can be reconstructed thereafter.

Retired containers may remain readable for legitimate historical research purposes. Their misuse as current work instructions must be prevented. Clear labeling and a clear transition to the current document are equally important, as are technical access restrictions.

Sources: [1] [7] [9] [8]

4. Verify native releases consistent with the SOP process

The documented cloud release requires approval rights to request and respond. Previous release cycles are accessible in the associated activity log. Additionally, please note that content status is handled separately in view and edit modes. Therefore, a status dashboard alone does not indicate which version was reviewed.

The requirement for approval prior to publication explicitly references new pages in the open documentation. This does not imply a documented restriction preventing any revision of an already published SOP. Review this scenario within your own tenant: modify the text, reject the release, re-edit, and attempt an unauthorized publication.

Establish acceptance criteria for content changes during a review. Is a new authorization required following such changes? Which version does the reviewer refer to—whichever the reviewer or the standard reader? Are appendices or external content included in the review? These questions define the necessary process, without assuming an unproven product function.

Do you require an electronic signature? Assess its significance, identity, and permanent linkage separately. A native approval or app bearing an appropriate designation does not fulfill all requirements of the applicable regulatory framework merely by its name.

Sources: [2] [8] [10]

5. Separate authors, reviewers, and readers effectively

Confluence Cloud controls access at space and content level. Child content inherits viewing restrictions from its parent. Editing restrictions do not automatically pass to child content. The Free plan does not support the same content restrictions. Base the permission design on both the plan and the actual content structure.

Test with realistic user roles: SOP Author, Technical Reviewer, QA, regular reader, and Administrator. Can a reader view or modify a draft? Can an author bypass review? Is the valid SOP remain accessible at the intended work location? Verify permissions after document movement, copying, or creation based on actual workflow usage.

Administrators may have advanced capabilities beyond those of regular users. Treat changes to access and release rules as controlled interventions. An additional control procedure may be required when a desired separation cannot be fully implemented technically. Document the remaining boundary, rather than describing the configuration as fully complete.

Public releases and external accounts fall within this evaluation, provided they are used. A regulated SOP must not become an uncontrolled copy via an overlooked distribution route.

Sources: [3] [4] [8]

6. Page refresh, awareness and training separation

Confluence Analytics provides information about content use. The comprehensive analytics feature described here belongs to the Premium and Enterprise plans. A page view alone does not establish that an employee read the correct SOP version, understood it and practised the task.

Determine the required level of involvement for each change: simple information provision, documented awareness, or training accompanied by an appropriate assessment of understanding. Clearly define the target group, document version, deadline, and responsibility. This ensures that minor corrections do not trigger disproportionate effort or that critical process changes are merely communicated without proper validation.

When an app or learning system conducts knowledge confirmation, verify its assignment to the correct individual and the exact version of the SOP. What occurs after a subsequent text amendment, role change, or delayed confirmation? A report stating "all tasks completed" must specify a defined target group. Absent personnel should not be eliminated through an inappropriate filter.

This validation plan does not claim a general native read-verification capability for Confluence. It outlines the documentation required to support your selected workflow and specifies any additional requirements that may be necessary.

Sources: [6] [9] [8]

Further reading:

7. Assess existing documentation related to a SOP amendment driven by a CAPA action

Supplier documentation can actually address relevant requirements. To verify this, assess the scope, product version, and statement of the respective document. Security controls, documented standard functions, and custom configured workflows address different questions. Validatable evidence does not need to be generated without justification.

Confluence Cloud keeps page history separate from the administrative audit log. The audit log records events such as permission changes and excludes content edits. Approval histories and relevant app records can provide further evidence. Identify the sequence of events your process requires across those records.

The following internal work matrix leverages a SOP update resulting from a CAPA initiative. Confluence is not assumed to function as a complete CAPA system. The original deviation and effectiveness assessment may reside in a separate leading system.

Assign documentation for a SOP amendment following CAPA
Process stepUsable evidenceRemaining internal inspection
Change request from CAPA Reference and professionally evaluated measure Is the correct SOP and relevant process assigned?
Create a new version Page version and associated documents Has the complete content been verified against the instruction?
Professional Approval Native or App Release Documentation Identity, authority and exact status?
SOP effective implementation Validity statement and distribution/training certification Target group reached and old work copies addressed?
Assess efficacy Evidence within the established quality system Does the action address the technical objective, not just the status of the side?

Sources: [12] [4] [2] [8]

8. Plan complete export records, histories, and storage requirements

When a documented cloud export of a page is performed, the published version status of that page is displayed. PDF exports do not include comments. The scope and content of additional export formats depend on the selected export path and user permissions. Therefore, carefully verify whether the required documents, release certificates, and app data are included or otherwise preserved.

The administrative Cloud Audit Log features a configurable retention period of one to twelve months; for extended availability, Atlassian describes the CSV export option. This product limit does not constitute a GMP retention period. Separate determination must be made regarding the required retention periods for document versions and events, as well as the timeliness of an appropriate transfer.

A storage test should extend beyond simply opening a PDF. Can document number, version, original release date, and associated attachments be clearly linked after transfer? Are comments—particularly those involving material decisions—traceable? Are different versions clearly distinguishable?

Define additionally the required restart period following system failure. Backup, readable retention, and restoration of an operational system serve distinct objectives. The scope and evaluation shall be aligned with this need; a blanket requirement to restore all data after any change would not be justified.

Sources: [5] [4] [9] [8]

Further reading:

9. Test example: SOP revision without premature use

A pharmaceutical SME modifies the cleaning procedure for a packaging line following a deviation. Version 4 is valid; Version 5 is being developed as a draft. The following scenario is a standalone review proposal and does not describe results from an already conducted product testing.

Prepare the previous version, the new instruction, and an amended annex. A typical reader opens the intended workbench link; the expected outcome is the valid version 4. The reviewer examines version 5 and requests a correction. Now, the author attempts to make the rejected revision available as a binding instruction. The established process must prevent this in accordance with the previously defined criteria or clearly control it.

After the correction, check which text and which installation are covered by the documented approval. Test another modification after approval: The process must not be published as approved by any technical or unaudited version. Because the manufacturer's description of the native publication block lists new pages, this revision case is deliberately examined separately.

At the specified effective date, the reader refers to Version 5. The required awareness is directed to this version; Version 4 remains identifiable as obsolete for legitimate inquiries. Finally, verify export and retrievability of both versions together with the necessary decision justification. Document deviations together with their professional implications, not merely with a technical error message.

Sources: [1] [2] [5] [9] [8]

10. Project participation and ongoing changes management

The SOP Owner defines content and validity; QA defines the technical acceptance criteria, IT defines the technical implementation. For apps, the suppliers are additionally included. Effort arises particularly due to scattered legacy data, inconsistent document numbering, embedded content, multiple release pathways, and lack of association between training data and specific documents.

Start with a representative SOP lifecycle. Identify gaps based on this approach prior to taking over the entire inventory. When evaluating future changes, assess functions, rights, templates, apps, and exports that may impact this workflow. Regular reviews should also include incidents, open actions, and ongoing supplier support.

For the affected data center products, including Confluence, Atlassian has announced the end of life on 28 March 2029. Review contractual special provisions. A cloud migration requires a planned content alignment, historical states, permission mapping, and additional feature assessment.

  • Purpose of document, designated storage location, and responsible party are defined.
  • Product, tariff, content type, and apps match the validated combination.
  • Release and validity refer to a single, definitive document version.
  • Rights prevent unauthorized editing and premature use.
  • Awareness or training is assigned to the correct version.
  • Historical versions remain retrievable and clearly organized.
  • Export, storage, and required restoration were reviewed.
  • Changes and migrations have defined evaluation and responsibility.

Sources: [8] [13] [9]

Project experience and collaboration

Show which approved SOP version readers can access

Will Confluence hold reference knowledge or provide the effective SOPs that staff must follow? We settle that with QA and users before reviewing approvals and apps. Using an SOP change, we check which version authors can edit and which readers should use. If the existing setup can control the defined document process, we plan the remaining evidence. Fundamental gaps in effective status, history or retention warrant considering a different document storage approach.

Frequent Questions about Confluence as an SOP Repository

Is Confluence a ready-made GMP document management system?

From the described functions, this does not follow. What is decisive is whether the established process actually meets the required documentation control. Define document identity, release, validity, distribution, and retention, and verify the implementation thereof. Appropriate supplier records may support parts of this. A collection of pages with uniform layout is insufficient as evidence for this process.

Sources: [9] [8] [12]

Do we need a Marketplace app for every Confluence release?

No. The current cloud documentation describes native page releases for Premium and Enterprise. However, this does not necessarily imply that your complete SOP workflow is covered. Identify the remaining requirements, particularly for revisions, efficacy, and potentially signatures. Only after this assessment can it be justified whether additional functionalities or an alternative leading system are required.

Sources: [2]

Does the native release function also apply to Live Docs and Data Center?

The open manufacturer's description applies to cloud pages and excludes live docs as well as blog posts. It does not occupy a corresponding data center function. Therefore, check product, version and apps separately during an existing installation. An identical looking status or a similarly named button is not sufficient evidence of identical behavior.

Sources: [2] [7]

Does the publication lock prevent any unreviewed SOP revision?

For already published SOPs, you require separate evidence of the change and release process. The reviewed documentation describes the publication lock for new pages and thereby does not adequately demonstrate control over every subsequent revision. Also assess changes during an ongoing review and after formal approval. Any remaining deviation from the intended process must be resolved or appropriately controlled prior to use.

Sources: [2] [8]

Is a approval in Confluence considered an electronic signature?

Not automatically in the sense of all applicable requirements. Assess the meaning in the process of the action and its continued alignment with a specific individual and the exact document version. For the relevant FDA context, the requirements of Part 11 must be evaluated separately. Even in the case of a signature app, its actual configuration and integration are decisive.

Sources: [8] [10] [11]

Can employees still read old SOP versions?

A blanket restriction on access to all historical versions is not required. Authorized users may need to retrieve specific versions. However, ensure that an outdated version is not used as the current work instruction. Verify labeling, search and access pathways, as well as controlled printouts. The standard workplace retrieval should unambiguously lead to the intended current version.

Sources: [9] [8]

Prove that all personnel are trained using Confluence-Analytics?

No. Usage information initially describe activity. For documented awareness, a defined target group and assignment to the correct document version are required; additional training may necessitate further evidence. Determine what is required depending on the change. Review the selected app or learning system, including open and delayed confirmations.

Sources: [6] [9] [8]

Why is the version history insufficient for all tests?

It supports the comparison of content strengths. Changes to rights, release decisions, and internal activities within an app may be documented elsewhere. Therefore, compile the relevant events for your specific SOP process. Subsequently, assess their protection, availability, and required analysis. The scope and rationale for the review arise from context and risk, not from a routine daily comprehensive audit.

Sources: [1] [4] [8]

Is an exported PDF sufficient for retention?

A PDF can provide a clear and readable version. However, it is not automatically a complete package comprising documents, appendices, and decision trails. Verify the required information against a required inventory. Also consider app data and its availability after license expiration. Crucially, it must be possible to trace the relevant version and its usage throughout the required duration.

Sources: [5] [9] [8]

What should we prepare prior to a Confluence validation project?

Bring together the document inventory, intended life cycle, roles, product and application inventory and representative historical versions. Identify contacts in QA, document ownership and IT. Trace an example from first draft to withdrawal to find evidence gaps and plan migration, configuration and testing. This work provides a basis for estimating cost and duration.

Sources: [8] [9]

Sources and review date

Source: October 6, 2026. Cloud functions are to be confirmed according to tariff and actual tenant availability; Data Center and additional apps are to be evaluated separately. Test scenario and verification matrix are professional work aids.

  1. Atlassian: Create, edit, and publish a page – Confluence Cloud
  2. Atlassian: Request and manage approvals in Confluence Cloud
  3. Atlassian: Change who can find content and what they can do with it
  4. Atlassian: View the audit log – Confluence Cloud
  5. Atlassian: Export a space's content as Word, PDF, or data files
  6. Atlassian: View Confluence analytics
  7. Atlassian: Page History and Page Comparison Views – Data Center 10.2
  8. European Commission: EU GMP Annex 11, January 2011 revision
  9. European Commission: EU GMP Chapter 4 – Documentation
  10. eCFR: 21 CFR Part 11 – Electronic Records; Electronic Signatures
  11. FDA: Part 11 – Scope and Application
  12. Atlassian: GxP – Compliance Resources
  13. Atlassian: Ascend to the cloud – announced end of life for Data Center
  14. Atlassian: Understand Marketplace and custom app access

Sources checked: .

Daniel Herrmann, Daniel Herrmann Consulting

Daniel Herrmann Consulting

Verify the Confluence SOP process is traceable

We help you assess your document workflows and supplier evidence, identify gaps and select suitable tests for your intended use of Confluence.

  • Computer system validation →

    Bring your GxP systems into validated operation, from laboratory software, MES and eQMS to ERP. We define the scope, plan risk-based tests using GAMP 5 and hand the evidence to QA for release.

Send a project enquiry Customer testimonials →