Project-Level Role Segmentation in Collaboration Environments

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Existing collaboration environments lack a concise method to organize workflow at the project level, making it difficult to track units of work, user assignments, and user roles within projects.

Innovation Solution

The system assigns users to different project-level roles, which provide specific permissions and privileges, allowing for better project organization and control by enabling or disabling access to features within the collaboration environment.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Adaptability or versatility

If users are assigned multiple roles within units of work, then user functionality and project support are enhanced, but it becomes difficult to keep track of user roles and maintain control of the project

Engineering Contradiction:
Improveuser functionalityVSAvoidproject control
Core Design Contradiction:
Adaptability or versatilityVSDevice complexity

Solution Approach 1:

The patent segments user roles into two distinct levels: project-level roles and unit-of-work roles. Project-level roles provide overarching permissions and visibility for the entire project, while unit-of-work roles provide specific functional permissions for individual tasks. This segmentation allows users to have multiple specialized roles at the unit level without creating complexity at the project level, as the project-level role acts as a unifying framework.

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

The patent introduces a hierarchical dimension to role management by adding project-level roles above the existing unit-of-work roles. This creates a two-dimensional role assignment system where users can be assigned roles at both the project level and unit level simultaneously. The project-level role provides a macro view of user capabilities across the entire project, while unit-level roles provide micro-level functional permissions, resolving the complexity issue by organizing roles across different hierarchical dimensions.

Inventive Principle:
Principle #17Another dimension (Dimensionality change)

2Ease of operation

If project-level roles are implemented, then project organization and control are improved, but the system complexity increases

Engineering Contradiction:
Improveproject organizationVSAvoidsystem structure
Core Design Contradiction:
Ease of operationVSDevice complexity

Solution Approach 1:

The patent implements universal project-level roles that can be applied across multiple units of work within a project. Instead of assigning roles individually to each unit, the project-level role serves as a template that automatically applies to all units, providing consistent organization and control across the entire project. This multi-functionality reduces system complexity by eliminating the need to manage separate role assignments for each unit while maintaining comprehensive project-level organization.

Inventive Principle:
Principle #6Universality (Multi-functionality)

Solution Approach 2:

The patent enables preliminary assignment of project-level roles before users are assigned to specific units of work. By establishing the project-level role framework first, the system pre-defines the organizational structure and permission hierarchy, making subsequent unit assignments more straightforward. This preliminary action simplifies the overall system structure by setting up the organizational framework in advance rather than building it incrementally as units are added.

Inventive Principle:
Principle #10Preliminary action

Data Source

PatentUS20250190947A1Systems and methods to facilitate interaction with a collaboration environment based on assignment of project-level roles
Publication Date: 2025.06.12 ASANA INC
  • US20250190947A1 patent drawing
  • US20250190947A1 patent drawing
  • US20250190947A1 patent drawing

AI summary

Systems and methods to facilitate interaction with a collaboration environment based on assignment of project-level roles are described herein. Exemplary implementations may: manage environment state information maintaining a collaboration environment; obtain role information specifying roles of the users within units of work and projects; update the environment state information based on the role information; effectuate presentation of the collaboration environment based on the environment state information so that access, by the users, to the individual units of work and the individual projects reflects the roles of the users within the units of work and the projects; and/or perform other operations.