IT systems · Practical guide

SharePoint SOPs: approval, version control and visibility

A library view can hide drafts while a direct link or another view still exposes them. Check which version readers and editors can open from each entry point using their actual rights.

Table of contents

At a glance

How do you test SOP approval in SharePoint Online?

Check which document version different users can actually see and use. Versioning, content approval and draft visibility are separate SharePoint settings. Test the complete path from draft to effective SOP and withdrawal, including direct links and local copies. A filtered view alone does not prevent access to unsuitable versions.

Scope and Applicability

The article examines a configured SharePoint document library. SharePoint is not considered a qualified eQMS or sufficient electronic signature system in general. Training records and additional release requirements must be addressed separately.

Sources: [1] [2]

Define document routing as a complete workflow.

A version-controlled library is still not a complete SOP process. Describe the steps for creation, review, release, effectiveness, distribution, supersession, and retention. A released SOP may only become effective later, for example, after relevant personnel have been informed or trained. These states must be distinguishable within the intended model.

Capture the library, permissions, metadata, and automations together. Microsoft specifies in versioning settings, among other things, content approval, main versions or main and minor versions, the number of retained versions and drafts, as well as their visibility. Assess the following four questions: Which content requires approval? What versions are generated during editing? Is the required history preserved? Which role is authorized to view drafts? The appropriate settings must align with the other steps of your SOP procedure.

What is the primary record? Is the SOP directed as an editable file, PDF, or in another format? Which version do users, reviewers, and administrators see? A valid status in a list is weak if the link beside it opens a different file version. Review status and actual content jointly.

Sources: [1] [2] [3]

Define states, roles, and visibility settings

Define who is authorized to edit, review, approve, and implement a draft. Consider delegation and administrative capabilities. A role matrix should include specific actions. The name of a SharePoint group does not indicate whether its members are authorized to modify release status or library settings.

Define how regular users can access the currently valid version. Drafts and future versions should not appear ambiguously as a basis for work. Direct links, search functions, and synchronized copies may also be relevant. The appropriate controls depend on the actual access pathways available.

Approval and the effective date may differ. Define visibility, training and the planned date during that interval. For permitted downloads or printouts, define how to confirm at the point of use that the version is current. Include offline or printed use in the access test.

Internal Work Aid: Define states, roles, and visibility settings
StateMeaning in the processOwn Visibility Inspection
Draft Still under review Typical user does not confuse him with a valid SOP
Under review The identified version is assessed Changes and reviewer attribution remain traceable
Released, not yet effective Approved for future use Current valid version remains unequivocal
Effective To be applied to the specified process currently User reaches the correct content
Superseded Historically required, not intended for uncontrolled reuse Labeling and access comply with the retention model

Sources: [1] [2] [3]

Example: previous direct link based on efficacy of a new SOP

SOP-17 Version 3 is now effective. A team continues to use a direct link to Version 2 or a synchronized work copy. The library overview correctly displays Version 3. A review based solely on this overview fails to detect the actual working pathway. The gap arises due to continued use of the direct link or the synchronized work copy; the example does not describe a SharePoint defect and is not a completed product test.

Ask a representative user to open the document through search, the standard link and an allowed alternative route. Compare the visible status, version and file contents. Also test a link to a draft that is not yet effective. Depending on the distribution model, the expected response may be clear labelling, an access restriction or another verified route to the effective version.

Subsequently, test a controlled rollback to a historical version. A duly authorized reviewer must be able to justify a prior decision without requiring the previous SOP to reappear as the current work instruction. Current usage and historical traceability are distinct responsibilities. Both should be demonstrably observable in testing.

When modifying the efficacy status, retain the triggering action and the associated decision. After a relevant change to a workflow or permission, re-evaluate the affected pathways. An unchanged file may become accessible through a new view; a new workflow may assign a different effect to the same status.

Work aid example SOP-17: User access and historical inquiry
Test pathActionExpected finding
Library view Open SOP-17 Current valid version clearly defined
Stored link Use previous link Selected control prevents misinterpretation
Search Search SOP-17 Current status and historical hits distinguishable
Access to the draft As a typical user opens Draft visibility follows the specified rules
Historical Review Search version 2 specifically Previous content and context traceable

Sources: [1] [2] [3]

Separate authorization from electronic signature

A content approval controls a document status. Whether it simultaneously represents the required electronic signature must be evaluated separately. A username and modification date are insufficient by themselves to satisfy every signature requirement. Describe the significance, identity, and linkage to the verified document version.

When automations are implemented, verify who actually writes the status. A workflow may operate under a technical connection, even though a human initiates the decision. The evidence must appropriately attribute the professional judgment to the responsible individual. The document does not assume general signature capability for a SharePoint standard workflow.

Review changes during testing and after release. A critical change must not remain in effect undetected beyond a previous decision. The specific rule may prescribe a new review or other controlled handling. Test the relationship between content, version status, and status using a deliberately modified test file.

Sources: [1] [2] [3]

Versioning, restoration, and retention verification

A version history may make previous contents available, but it has predefined limitations. Review which records are retained, who is authorized to delete or restore them, and how required documentation is protected over the long term. Versioning is not automatically a complete archiving or backup solution.

A restored previous version may generate a new current state or have other process implications. Verify the actual behavior of your configuration. Restoration should not silently re-establish a historical SOP as the current work basis. Technical restoration must align with subject-matter approval.

For storage and audit readiness, the required context includes: document, version, decision, effectiveness, and where applicable, associated information. The specific platform functions or supplementary procedures that address this task must be evaluated. A export of only the latest PDFs may not adequately address historical concerns.

Sources: [1] [2] [3]

A feasible operations and change management model to be provided

Name the responsible parties for content, library configuration, permissions, and automations. A document owner may assess technical changes, while a platform change requires technical support. The interface between the two should be clearly defined. Otherwise, a modified release rule may be implemented merely as an administrative task.

Retain a small set of critical tests for later changes. Include access to the effective version, visibility of drafts, critical content changes, permissions and historical retrieval. A cosmetic change to a view may need less testing than new approval automation. Justify the selection from its actual impact.

The internal team should be able to trace an SOP from user access to the release decision. A short practical handover with a current and a historical process shows whether this will succeed. Thus, the document management will be usable in everyday life and depends less on the original creator of the library.

Sources: [1] [2] [3]

Next steps

  • Define document statuses and efficacy conditions.
  • Configure versioning, approval, and rights jointly.
  • Test direct links, alternative views, and copies.
  • Software version changes, training, and decommissioning in operation transfer.
Further reading:

Project experience and collaboration

Find the current SOP through the channels staff actually use

With an eventual reader and document owner, we open a prepared SOP through the library, search and a saved direct link. We compare the displayed version against the version authorised for use at that time. Library settings may suffice. Additional effective-date or training conditions require a suitable process rule. We include any permitted printout or download, then test access to historical versions with an authorised role. Historical access is distinct from use of the SOP currently in force.

Frequently asked questions about SOP approval in SharePoint

Is a main version automatically a valid SOP?

Only if the defined process specifically provides for this intent and all required conditions are met. Training or future efficacy may require additional steps.

Sources: [1] [2]

Does a version history replace an audit trail?

Not blanket. Verify which events, content, and metadata are actually captured and retained, and determine whether this is sufficient for the intended process.

Sources: [1] [2]

Must SharePoint be fully validated itself?

The scope aligns with the specific intended use, relevant functions, and dependencies. The solution configured for your document process remains at the core.

Sources: [1] [2]

Is SharePoint with versioning enabled automatically considered a validated Document Management System (DMS)?

No. Assess the specifically implemented document process, its risks, and the controls in place. Versioning is a component. Roles, release, validity, distribution, changes, and retention require appropriate documentation. A general statement about the platform does not substitute for an evaluation of the actual configuration and usage.

Must previous versions of SOPs remain accessible to all users?

Historical availability and routine usage must be distinguished. Authorized personnel require prior versions for traceable investigations. Routine users should clearly identify which version is currently in effect. Visibility is determined by the specific procedure and the selected technical and organizational controls.

Is a restored previous version automatically valid again?

A technical restoration does not automatically make the previous version a professionally valid SOP. Microsoft states that during restoration, a new version is created. The described dialog prompts whether this version should become the currently approved document. Check in your library the subsequent status, the actually opened content, and the required release workflow. This ensures that a restoration does not result in an unintended version change during operation.

Sources: [3] [2]

How can we test document control from the user's perspective?

Grant representative roles access via the actually authorized pathways for current, future, and historical packaging. Compare status and content. Monitor search activities and stored links. A correct administrator view alone does not confirm unambiguous distribution in day-to-day work.

Sources and review date

The sources provide the technical foundation. Tables, checklists, and examples are derived methodological tools, not verbatim regulatory requirements. Manufacturer information must be referenced to the specific version and configuration in use.

  1. European Commission: EU GMP Annex 11, Computerised Systems (2011)Current version as per EudraLex inventory as of 14.10.2026. Application, risks, operation, and data lifecycle; specific testing proposals are derived independently.
  2. European Commission: EU GMP Chapter 4, Documentation (2011)Document routing and records. Electronic documents, their control, and the required retention must be considered in conjunction.
  3. Microsoft: Versioning for a SharePoint list or librarySupplier source for product functionalities. Availability and behavior depend on version, edition, license, and configuration; no general compliance certification.

Sources checked: .

Daniel Herrmann, Daniel Herrmann Consulting

Daniel Herrmann Consulting

Review the SOP workflow from release to use

With your document managers, we take an SOP through the libraries, releases and access routes used. In doing so, open rules on effectiveness, required training and access to replaced versions become concrete. We derive the appropriate additions from the existing evidence with your team.

  • 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 →