Project-wise Lists for Cross-Platform Permission Management
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Current access permissions management systems are inefficient in managing project-wise permissions across network objects stored on disparate computers operating different operating systems, especially when these objects are inter-related and cannot be managed together via a hierarchical folder structure.
Innovation Solution
A project-wise lists management subsystem that generates and maintains project-wise lists of network objects, maps access permissions, and merges permissions from multiple lists, allowing owners to make project-wise changes without individually modifying each object, utilizing a user interface that operates within a hierarchical access permissions environment.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Ease of operation
If hierarchical folder structure is used to manage access permissions, then individual object management is simplified, but project-wise permission management becomes inefficient when objects are stored on disparate computers with different operating systems
Solution Approach 1:
The patent introduces a project-wise list as an intermediary layer between the hierarchical folder structure and the actual network objects. This list aggregates multiple network objects from disparate computers and operating systems, allowing permission changes to be applied to all objects in the list simultaneously through a single interface, thus resolving the inefficiency of managing permissions across distributed systems
Solution Approach 2:
The project-wise list serves multiple functions: it acts as a collection container for network objects, a permission management interface, and a cross-platform abstraction layer. By making the list multi-functional, the system can handle both individual object management and project-wise permission changes without requiring separate mechanisms for each task
2Productivity
If project-wise permission changes are made without individual modification, then operational efficiency improves, but system complexity increases due to the need for list management infrastructure
Solution Approach 1:
The patent segments the permission management system into two distinct layers: the project-wise list layer for bulk operations and the individual network object layer for specific object management. This segmentation allows the system to handle large-scale permission changes efficiently through the list while maintaining the ability to manage individual objects when needed, without requiring a complete redesign of the underlying infrastructure
3Adaptability or versatility
If network objects are managed across disparate computers with different operating systems, then system versatility improves, but permission management consistency deteriorates
Solution Approach 1:
The project-wise list acts as a mediating abstraction layer that uniformizes permission management across different operating systems and computers. By routing all permission changes through this standardized list interface, the system ensures consistent permission application regardless of the underlying platform differences, maintaining reliability while supporting versatility
Data Source
AI summary
In a hierarchical access permissions environment, a method for enabling efficient management of project-wise permissions including maintaining project-wise lists of network objects, access permissions to which cannot be managed together via a hierarchical folder structure and employing the project-wise lists of network objects to make project-wise changes in access permissions to the network objects without the need to individually modify access permissions to individual ones of the network objects.