Embedded Workbook Access Segmentation for Team-Level Data Control

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Modern businesses face challenges in efficiently managing team access to workbooks embedded in client domains, as composing and issuing database queries for complex data manipulation often exceeds the abilities of most users.

Innovation Solution

A workbook manager system that hosts workbooks accessible by multiple teams, creates team administrator accounts with specific authorization, and manages access to different underlying data sets, allowing teams to administer their data without affecting others, while offloading administrative duties.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Adaptability or versatility

If a workbook is made accessible to multiple third-party user accounts divided into teams, then the system's adaptability and collaboration capability are improved, but the complexity of managing access permissions and data security increases

Engineering Contradiction:
Improvecollaboration capabilityVSAvoidaccess permission management complexity
Core Design Contradiction:
Adaptability or versatilityVSDevice complexity

Solution Approach 1:

The system segments user access permissions by organizing third-party users into distinct teams, where each team is granted access to specific workbooks and underlying data sets. This segmentation allows the workbook manager to control access at the team level rather than individually managing permissions for each user, thereby reducing management complexity while maintaining collaborative capabilities across multiple teams.

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

The workbook manager acts as an intermediary component between the workbook, multiple third-party teams, and the underlying data warehouse. It mediates access requests by authenticating users, determining their team affiliations, and enforcing appropriate permission levels. This intermediary layer simplifies access management by centralizing permission control logic and isolating the complexity from both users and the underlying data system.

Inventive Principle:
Principle #24Intermediary (Mediator)

2Ease of operation

If team administrator accounts are created with authorization to manage workbooks for specific teams, then the ease of operation for team self-management is improved, but the system's security requirements and authorization management complexity increase

Engineering Contradiction:
Improveteam self-management capabilityVSAvoidauthorization security
Core Design Contradiction:
Ease of operationVSReliability

Solution Approach 1:

The system implements local quality by granting team administrator accounts with differentiated authorization levels specific to their respective teams. Each team administrator receives permissions tailored to their team's needs - sufficient to manage their team's workbook access and data operations - but restricted from accessing or managing other teams' resources. This localized permission assignment simplifies operation for each team while maintaining security through precise authorization boundaries.

Inventive Principle:
Principle #3Local quality

Solution Approach 2:

The system applies partial action by giving team administrators only the specific permissions necessary for their role, rather than full administrative access to all workbooks and data. Team administrators can perform actions relevant to their team (such as managing team member access, viewing team data) but are deliberately restricted from performing actions outside their team's scope. This partial authorization approach enables effective team self-management while preventing excessive access that would compromise security.

Inventive Principle:
Principle #16Partial or excessive action

3Measurement precision

If complex database queries are required to manipulate data in cloud-based data warehouses, then the measurement precision and data manipulation capability are improved, but the ease of operation for most users deteriorates

Engineering Contradiction:
Improvedata manipulation capabilityVSAvoiduser accessibility
Core Design Contradiction:
Measurement precisionVSEase of operation

Solution Approach 1:

The workbook manager serves as an intermediary that shields users from the complexity of direct database query construction. It provides a simplified interface where users can interact with data through workbooks without needing to write or understand complex SQL queries. The workbook manager handles query generation, optimization, and execution behind the scenes, translating user-friendly operations into the precise database statements needed for efficient data manipulation in the cloud-based data warehouse.

Inventive Principle:
Principle #24Intermediary (Mediator)

Solution Approach 2:

The system creates workbook copies or views of the underlying data warehouse content, allowing users to work with simplified data representations rather than directly querying the complex database structure. These workbooks act as copied, user-friendly interfaces to the raw data, pre-configured with appropriate queries and data models. Users can manipulate data through these workbook copies without needing to understand or construct the complex database queries that power them.

Inventive Principle:
Principle #26Copying

Data Source

PatentUS12585824B2Managing team access to workbooks embedded in client domains
Publication Date: 2026.03.24 SIGMA COMPUTING INC
  • US12585824B2 patent drawing
  • US12585824B2 patent drawing
  • US12585824B2 patent drawing

AI summary

Managing team access to workbooks embedded in client domains including hosting, by a workbook manager, a workbook embedded in a client domain accessible by a plurality of third-party user accounts divided into a plurality of teams, wherein each of the plurality of teams accesses a different underlying data set through the workbook; receiving, by the workbook manager from a client computing system, a request to create a team administrator account for a first team of the plurality of teams; and creating, by the workbook manager, the team administrator account with authorization to manage the workbook for the first team and without authorization to manage the workbook for third-party user accounts outside the first team.