Collaborative File Access Across User-Specific App Instances

Resolve Bottlenecks,
Find Innovative SolutionsGenerate Solutions

Solution Overview

Problem

Existing web-based collaboration platforms do not enable multiple users to collaboratively edit the same content shared during virtual meetings, leading to unnecessary content proliferation and disparate impressions due to users editing different instances of the content.

Innovation Solution

A system that updates user-specific instances of an application for individual users in response to a data file being associated with a collaboration object, providing direct access to the data file through a collaboration platform, allowing seamless editing across user-specific instances based on object permissions.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Ease of operation

If users share data files via email or separate instances before virtual meetings, then each user can view and edit content independently, but this leads to unnecessary content proliferation and disparate impressions of discussed content

Engineering Contradiction:

ImproveIndependent content access and editingVSAvoidNumber of content copies

Core Design Contradiction:

Ease of operationVSQuantity of substance

Solution Approach 1:

The patent merges multiple separate content instances into a single shared data file accessible by all users through the collaboration object. Instead of each user having their own copy edited independently, all users access and edit the same file through the virtual meeting interface, consolidating content into one unified instance while maintaining individual editing capabilities.

Inventive Principle:

Principle #5Merging (Combining)

Solution Approach 2:

The shared data file serves multiple functions simultaneously: it acts as both the collaboration object content and the editable document for all users. The system enables the data file to be accessed and edited through multiple interfaces (virtual meeting interface and direct file access), providing universal access without requiring separate content instances for different purposes.

Inventive Principle:

Principle #6Universality (Multi-functionality)

2Adaptability or versatility

If users edit different instances of the same content, then each user has their own customized version, but this creates alignment issues and loses the ability to track collaborative changes

Engineering Contradiction:

ImproveUser-specific content customizationVSAvoidCollaborative context and alignment

Core Design Contradiction:

Adaptability or versatilityVSLoss of information

Solution Approach 1:

The system implements feedback mechanisms that allow users to see real-time or near-real-time changes made by other users to the shared data file. Through the collaboration object interface, users can observe modifications, comments, and editing activity, maintaining awareness of collaborative context while still allowing individual editing freedom.

Inventive Principle:

Principle #23Feedback

Solution Approach 2:

The collaboration object serves as an intermediary layer between users and the shared data file. This intermediary provides a unified access point that maintains the single source of truth while enabling individual editing capabilities, acting as a mediator that reconciles the need for both collaboration and individual customization.

Inventive Principle:

Principle #24Intermediary (Mediator)

3Reliability

If a single data file is shared through the collaboration object, then all users access the same content, but users need direct access to their user-specific application instances for seamless editing

Engineering Contradiction:

ImproveContent consistency across usersVSAvoidDirect file access from application instance

Core Design Contradiction:

ReliabilityVSEase of operation

Solution Approach 1:

The system implements a nested structure where the shared data file is accessed through multiple levels: the collaboration object provides the primary access layer, while the user-specific application instances provide direct access layers. The application instances are essentially nested within or connected to the collaboration object framework, allowing users to access the same data file through their familiar application interfaces while maintaining content consistency through the underlying single-file architecture.

Inventive Principle:

Principle #7Nested doll (Nesting)

Data Source

PatentUS20260006084A1Updating user-specific application instances based on collaborative object activity

Publication Date: 2026.01.01 MICROSOFT TECHNOLOGY LICENSING LLC

AI summary

Updating user-specific instances of a second application for individual users of a group based on a data file for the second application being shared via a collaboration object that corresponds to the group within a first application. The instances of the second application present each individual user with their own custom user experience that is configured to provide access to specific content based on object permissions data. An application extension is executable, by the first application, to extend content editing functionalities of the second application into the collaboration object. Responsive to specific content being associated with the collaboration object via the application extension, each of the instances of the second application may be automatically updated to provide direct access to the specific content. Thus, each user within the group defined for collaboration object can access the data file via the collaboration object and their own instance of the second application.