Configurable Document Revision History Access Control

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Existing document history mechanisms are cumbersome and inefficient in providing differential access levels to document revisions, requiring separate copies and manual management of revisions and access permissions, which is impractical for most organizations.

Innovation Solution

A facility that records and manages document revisions, allowing authorized users to specify access levels for different groups, determining and enforcing access permissions to ensure that users can only view and interact with document history according to their authorized level, thereby providing configurable access to a document's history.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If separate copies of documents are created for different access levels, then access control is achieved, but device complexity and storage requirements increase significantly

Engineering Contradiction:
Improveaccess controlVSAvoidstorage requirements
Core Design Contradiction:
ReliabilityVSDevice complexity

Solution Approach 1:

The patent segments the document history access by creating different views or representations of the same document history for different user groups. Instead of creating separate document copies, the system segments the access to the unified history through permission layers, reducing storage while maintaining access control.

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

The patent introduces an intermediary access control layer between the document history and the users. This intermediary mechanism (permission system) mediates access to the unified history, allowing different users to access the same history with different levels of visibility without requiring separate document copies.

Inventive Principle:
Principle #24Intermediary (Mediator)

2Reliability

If manual management of revisions and access permissions is performed, then access control is maintained, but productivity and ease of operation deteriorate

Engineering Contradiction:
Improveaccess controlVSAvoidease of operation
Core Design Contradiction:
ReliabilityVSProductivity

Solution Approach 1:

The patent implements self-service mechanisms where users can manage their own access permissions and view their authorized history without requiring manual intervention from administrators. The system automatically enforces access control based on user roles and permissions, improving ease of operation while maintaining reliable access control.

Inventive Principle:
Principle #25Self-service

Solution Approach 2:

The patent uses parameter changes in the form of configurable permission levels and access controls that can be dynamically adjusted. Instead of manual management, the system allows flexible parameter configuration for different user groups, improving productivity while maintaining access control reliability.

Inventive Principle:
Principle #35Parameter changes

3Ease of operation

If full document history is made accessible to all users, then ease of operation is improved, but security and information protection worsen

Engineering Contradiction:
ImproveaccessibilityVSAvoidsecurity risks
Core Design Contradiction:
Ease of operationVSObject-affected harmful factors

Solution Approach 1:

The patent applies local quality by providing different levels of history access to different user groups. Each user group receives customized access permissions tailored to their role, allowing ease of operation for authorized users while maintaining security through differentiated access controls that prevent unauthorized viewing.

Inventive Principle:
Principle #3Local quality

Data Source

PatentUS10642940B2Configurable access to a document's revision history
Publication Date: 2020.05.05 MICROSOFT TECHNOLOGY LICENSING LLC
  • US10642940B2 patent drawing
  • US10642940B2 patent drawing
  • US10642940B2 patent drawing

AI summary

A facility for providing configurable access to a document's history is described. The facility receives input specifying one or more revisions to a document. The facility causes to be stored a representation of at least a portion of the revisions. When the facility receives a request to materialize the document for a particular entity, the facility materializes the document in a manner that includes any of the represented revisions only if the entity is among an authorized class of entities.