Centralized Domain Access Profiles Across Application Instances

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Existing application management systems face inefficiencies in centrally managing user access permissions for multiple application instances, leading to increased computational load, user frustration, and potential data security vulnerabilities due to unfettered access across instances.

Innovation Solution

A centralized access permissions management system that allows admin users to configure role-based domain access permissions through a unified interface, enabling efficient management of access across multiple application instances by associating domains with specific product roles, reducing the need for individual instance-level permissioning.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Measurement precision

If individual instance-level permissioning is implemented across multiple application instances, then access control precision is improved, but device complexity and computational load increase significantly

Engineering Contradiction:
Improveaccess control precisionVSAvoidpermission management complexity
Core Design Contradiction:
Measurement precisionVSDevice complexity

Solution Approach 1:

The patent merges permission management across multiple application instances by introducing a centralized permission service that consolidates authentication and authorization logic. Instead of implementing separate permission systems at each instance level, the patent combines these functions into a unified service that manages permissions centrally, reducing overall system complexity while maintaining precise access control.

Inventive Principle:
Principle #5Merging (Combining)

Solution Approach 2:

The patent creates a universal permission service that handles multiple application instances through a single interface. This permission service is designed to be multi-functional, supporting various types of applications and instances while providing consistent permission management. The service can authenticate users, manage roles, and enforce access policies across diverse application instances without requiring instance-specific customization.

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

2Productivity

If centralized access permissions management is implemented across multiple application instances, then productivity is improved, but device complexity increases

Engineering Contradiction:
Improvepermission management efficiencyVSAvoidsystem architecture complexity
Core Design Contradiction:
ProductivityVSDevice complexity

Solution Approach 1:

The patent segments the permission management system into distinct functional modules: an authentication service handles user verification, while a separate authorization service manages permission enforcement. This segmentation allows each module to specialize in specific tasks, improving overall efficiency. The authentication service focuses on verifying user identities, while the authorization service concentrates on managing roles and permissions across multiple instances, reducing the complexity burden on any single component.

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

The patent introduces an intermediary permission service that acts as a mediator between users and application instances. This service receives authentication requests, manages user sessions, and coordinates authorization decisions across multiple instances. By positioning this intermediary layer, the patent simplifies the interaction model - users interact with a single permission service rather than multiple instance-specific systems - while the service itself handles the complexity of coordinating across instances.

Inventive Principle:
Principle #24Intermediary (Mediator)

3Ease of operation

If domain-wide access permissions are implemented, then ease of operation is improved, but manufacturing precision of access control is reduced

Engineering Contradiction:
Improvepermission configuration easeVSAvoidaccess permission precision
Core Design Contradiction:
Ease of operationVSManufacturing precision

Solution Approach 1:

The patent implements local quality by allowing different precision levels of access control within the same domain. While domain-wide permissions provide broad access for ease of operation, the system also enables instance-specific permission overrides that allow administrators to apply more precise access control where needed. This means that most users experience simple domain-based access, while specific sensitive instances can enforce stricter permission rules without affecting the overall ease of operation for the domain.

Inventive Principle:
Principle #3Local quality

Solution Approach 2:

The patent makes the permission system dynamic by allowing permission precision to adapt based on the context. The system can switch between domain-wide permission modes (providing ease of operation) and instance-specific permission modes (providing precision) depending on the requirements of each application instance. This dynamic approach allows the system to optimize for ease of operation in general while maintaining the capability to enforce precision when specific security or access control requirements demand it.

Inventive Principle:
Principle #15Dynamics

Data Source

PatentUS12519794B2Apparatuses, methods, and computer program products for centralized access permissions management of a plurality of application instances
Publication Date: 2026.01.06 ATLASSIAN PTY LTD
  • US12519794B2 patent drawing
  • US12519794B2 patent drawing
  • US12519794B2 patent drawing

AI summary

Various embodiments of the present disclosure provide for centralized access permission management of a plurality of application instances. An example embodiment is configured to receive a manage access permissions request, cause rendering of a centralized access user interface, receive a domain access configuration request associated with a first domain, retrieve instance data associated with a plurality of application instances, cause rendering of a domain access configuration user interface associated with the first domain, receive a first product role selection request, generate a first domain permissions profile, the first domain permissions profile comprising at least a first product role associated with the first application instance, the first product role defining the role-based domain access permission of the first domain for accessing the first application instance, and store the first domain permissions profile in a permissions repository in association with the first domain and the first application instance.