A method and system for matching and adjusting approval authority for group enterprise collaborative office

Abstract

The present application relates to the technical field of authority management, in particular to a kind of group enterprise collaborative office use approval authority matching adjustment method and system, comprising the following steps, extract all function modules and data authority items in group enterprise collaborative office system, identify the interaction and its influence range of each module and item, module and authority are classified and arranged, form module and authority dependence record by comparison and induction.The present application, through graphic visual processing and real-time authority dynamic adjustment, improve the flexibility and response speed of authority management, analyze each module and authority dependence relationship, identify conflict area and reconfigure key node, ensure that authority setting and the operation structure of enterprise keep synchronous, avoid the problem of authority invalidation caused by structure adjustment, the improvement of interdepartmental communication of cross-department negotiation platform, the mechanism of continuous authority monitoring and adjustment, can effectively manage and protect key data resources, while improving the speed and accuracy of decision-making.

Description

Technical Field

[0001] This invention relates to the field of access control technology, and in particular to a method and system for matching and adjusting approval permissions for collaborative office work in a group enterprise. Background Technology

[0002] Access control technology involves creating, maintaining, and using access control policies to ensure secure access to system resources, including identifying and verifying user identities, authorizing users to access specific resources, and monitoring and logging access activities. In a corporate environment, access control also includes configuring permissions across multiple departments and regions, ensuring compliance and data security while optimizing business processes and improving collaborative efficiency. This technology utilizes software systems to implement dynamic permission allocation and adjustment, automatically updating permission settings based on organizational structure changes, changes in employee responsibilities, and collaboration needs.

[0003] Among them, the method of matching and adjusting approval permissions for collaborative office use in group enterprises mainly refers to the matching and adjustment of approval permissions for employees within the group enterprise through technical means. This can ensure the correctness and efficiency of the approval process, especially when it involves multi-level and cross-departmental approvals. It can avoid the problem of excessive concentration or improper allocation of permissions, while strengthening the transparency and traceability of the approval process and improving the speed and quality of decision-making. Its main purpose is to achieve efficient and secure approval process management in the daily operation of the group enterprise.

[0004] Traditional access control technologies often lack the ability to adapt to rapidly changing organizational structures and complex business needs. Static access configuration methods are not only slow to update, but also often fail to accurately reflect current business needs and employee responsibilities, leading to improper resource allocation or overly strict access controls. This lack of flexibility is particularly pronounced in large enterprises with multiple departments and regions, causing delays or misoperations in accessing critical resources, impacting work efficiency and project progress. Furthermore, the monitoring and recording of access approval processes in traditional systems are often not transparent enough, lacking effective tracking and auditing mechanisms, which not only increases compliance risks for enterprises but also reduces the efficiency of internal audits. Summary of the Invention

[0005] The purpose of this invention is to address the shortcomings of existing technologies by proposing a method for matching and adjusting approval permissions for collaborative office work in group enterprises.

[0006] To achieve the above objectives, the present invention adopts the following technical solution: a method for matching and adjusting approval permissions for collaborative office work in a group enterprise, comprising the following steps:

[0007] S1: Extract all functional modules and data permission entries from the group enterprise collaborative office system, identify the interaction and scope of influence of each module and entry, classify and organize the modules and permissions, and form module and permission dependency records through comparison and summarization;

[0008] S2: Based on the module and permission dependency records, extract key data and perform graphical visualization processing, analyze the dependency relationship of each module and permission, check potential conflict areas according to the analysis results, mark each conflict point, identify key connection points between modules, and output a conflict point and key dependency graph.

[0009] S3: Based on the conflict points and key dependency graph, analyze the deficiencies in the current permission settings, reallocate the permission configuration of key connection points, verify the effectiveness of the new permission configuration through simulation tests based on the reallocation results, track changes in the organizational structure in real time, dynamically adjust the permission settings to match the corresponding changes, and output the verified and optimized permission configuration scheme.

[0010] S4: Establish a cross-departmental consultation platform to process and approve permission change requests in the verified and optimized permission configuration scheme, record all change operations and pass the review, and output the group enterprise collaborative office permission change approval record.

[0011] As a further aspect of the present invention, the steps for obtaining the module and permission dependency record are as follows:

[0012] S111: Query the enterprise collaborative office system through the system interface, extract the raw data of all functional modules and data permission items, and generate an initial list of functional modules and data permission items;

[0013] S112: Based on the initial list of functional modules and data permission entries, perform data analysis, evaluate the interrelationships and influences between each module and entry, and generate module and permission interaction analysis records;

[0014] S113: Based on the module and permission interaction analysis records, perform logical grouping of modules and permissions, compare and summarize, and generate module and permission dependency records.

[0015] As a further aspect of the present invention, the analysis steps for the module and permission dependency relationship are as follows:

[0016] S211: Based on the module and permission dependency records, extract the module identifier and associated permission attributes to form a module attribute list and generate an initial dataset;

[0017] S212: Using the initial dataset, reveal the dependencies between modules through data correlation analysis, employing formulas...

[0018]

[0019] Calculate the dependency score matrix R between modules, construct and output the dependency graph, where A represents the module attribute matrix, D represents the permission data matrix, and D... T The transpose of the permission data matrix, |A·D T | represents matrix A·D T The absolute value is used to handle negative scores and balance the impact of dependencies;

[0020] S213: Perform in-depth analysis on the dependency graph to identify key dependencies and potentially complex permission areas, map permission dependencies between modules, and generate inter-module dependency analysis results.

[0021] As a further aspect of the present invention, the steps for obtaining the conflict point and the critical dependency graph are as follows:

[0022] S221: Using the inter-module dependency analysis results, check the permission settings of all modules, identify potential conflict areas between permission configurations, and generate preliminary conflict check records;

[0023] S222: Based on the preliminary conflict check records, analyze each record item, mark all potential conflict points and key dependencies between modules, and use a formula...

[0024]

[0025] Calculate the total probability of conflict C, and generate conflict and dependency labeled records, where p i q represents the permission level of module i. i This represents the permission level of the dependent modules, and n represents the total number of modules.

[0026] S223: Integrate the conflict and dependency marker records, use data visualization technology to visually display key conflict points and key dependencies, and output a conflict point and key dependency graph.

[0027] As a further aspect of the present invention, the step of reallocating the key connection point permission configuration is as follows:

[0028] S311: By analyzing the conflict points and key dependency graph, identify specific conflict points in the permission configuration, including connection points of excessive permissions and missing permissions, and generate specific conflict point identification results;

[0029] S312: Based on the specific identification results of the conflict points, reconfigure the permissions of key connection points using a formula.

[0030]

[0031] Calculate the new permission value NP jOptimize the permission settings for each key node and generate a permission reconfiguration scheme, in which OP j TP represents the current permission value of connection point j, and TP represents the total permission value of all connection points in the system.

[0032] S313: Apply the permission reconfiguration scheme to test the response and processing efficiency of the new configuration, confirm that each critical connection point is running effectively according to the new configuration, and output the permission reconfiguration results of the critical connection points.

[0033] As a further aspect of the present invention, the step of obtaining the optimized permission configuration scheme is as follows:

[0034] S321: Based on the reconfiguration results of the permissions at the key connection points, a comprehensive simulation test is conducted by creating test scenarios with different user behaviors and system loads to reflect the target operating conditions and potential security risks, analyze whether the new permission settings meet the expected operating and security requirements, and generate simulation test results;

[0035] S322: Based on the simulation test results, monitor the real-time changes in the group enterprise's organizational structure, automatically capture and respond to organizational change data, update permission configuration in real time, and generate dynamically adjusted permission configuration results;

[0036] S323: Based on the dynamically adjusted permission configuration results, repeat simulation tests to verify the adjustment effect, collect operation data and security logs to analyze the long-term effectiveness and potential security risks of the configuration, and output the verified and optimized permission configuration scheme.

[0037] As a further aspect of the present invention, the steps for obtaining the approval records for changes in collaborative office permissions within the group enterprise are as follows:

[0038] S411: Integrate the permission change requirements collected by the group's enterprise departments, combine them with the verified and optimized permission configuration scheme, conduct multi-department collaboration, and output a cross-departmental negotiation platform architecture.

[0039] S412: Based on the cross-departmental negotiation platform architecture, process permission change requests, receive permission change requests submitted by departments, classify, analyze and preliminarily approve the requests, and generate a preliminary processed permission change record;

[0040] S413: Based on the preliminary processed permission change records, conduct a final review and record of all permission change operations, verify that each permission change matches the group company's policies and security standards, and generate the group company's collaborative office permission change approval record.

[0041] A collaborative office approval permission matching and adjustment system for group enterprises includes:

[0042] The raw data analysis module extracts the raw data of all functional modules and data permission items of the group enterprise, evaluates the interrelationships and impacts between each module and item, performs logical grouping of modules and permissions, compares and summarizes, and generates module and permission dependency records.

[0043] The dependency identification module extracts module identifiers and associated permission attributes based on the module and permission dependency records, reveals the dependencies between modules through data correlation analysis, identifies key dependencies and potentially complex permission areas, and generates inter-module dependency analysis results.

[0044] The conflict point visualization module uses the inter-module dependency analysis results to identify potential conflict areas between permission configurations, mark all potential conflict points and key dependencies between modules, and output a conflict point and key dependency graph using data visualization technology.

[0045] The permission adjustment analysis module analyzes the conflict points and key dependency graphs to identify specific conflict points in the permission configuration, reconfigures the permissions of key connection points in a targeted manner, tests the response and processing efficiency of the new configuration, and outputs the permission reconfiguration results of key connection points.

[0046] The simulation test verification module performs a comprehensive simulation test based on the reconfiguration results of the key connection point permissions, analyzes whether the new permission settings meet the expected operation and security requirements, automatically captures and responds to organizational change data, updates the permission configuration in real time, repeats the simulation test to verify the adjustment effect, and outputs the verified and optimized permission configuration scheme.

[0047] The permission change approval module integrates permission change requests collected by departments of the group enterprise, combines the verified and optimized permission configuration scheme, conducts multi-department collaboration, processes permission change requests, reviews, verifies and records all permission change operations, and generates group enterprise collaborative office permission change approval records.

[0048] Compared with the prior art, the advantages and positive effects of the present invention are as follows:

[0049] In this invention, the flexibility and responsiveness of permission management are improved through graphical visualization and real-time dynamic adjustment of permissions. The system analyzes the dependencies between each module and permission, identifies conflict areas, and reconfigures key nodes to ensure that permission settings are synchronized with the company's operational structure. This avoids permission failures caused by structural adjustments. The cross-departmental negotiation platform enhances communication between departments, and the continuous permission monitoring and adjustment mechanism effectively manages and protects critical data resources while improving the speed and accuracy of decision-making. Attached Figure Description

[0050] Figure 1 This is a flowchart of the main steps of the present invention;

[0051] Figure 2 This is a flowchart illustrating the process of obtaining the module and permission dependency record of this invention.

[0052] Figure 3 This is a flowchart illustrating the analysis of module and permission dependencies in this invention.

[0053] Figure 4 This is a flowchart illustrating the process of obtaining the conflict points and key dependency graphs of this invention.

[0054] Figure 5 A flowchart illustrating the reallocation of permissions for key connection points in this invention;

[0055] Figure 6 The flowchart for obtaining the optimized permission configuration scheme is provided to verify the present invention.

[0056] Figure 7 This is a flowchart illustrating the process of obtaining approval records for changes in collaborative office permissions within a group enterprise. Detailed Implementation

[0057] To make the objectives, technical solutions, and advantages of this invention clearer, the invention will be further described in detail below with reference to the accompanying drawings and embodiments. It should be understood that the specific embodiments described herein are merely illustrative and not intended to limit the invention.

[0058] In the description of this invention, it should be understood that the terms "length," "width," "upper," "lower," "front," "rear," "left," "right," "vertical," "horizontal," "top," "bottom," "inner," and "outer," etc., indicating orientation or positional relationships, are based on the orientation or positional relationships shown in the accompanying drawings and are only for the convenience of describing the invention and simplifying the description, and do not indicate or imply that the device or element referred to must have a specific orientation, or be constructed and operated in a specific orientation, and therefore should not be construed as a limitation of the invention. Furthermore, in the description of this invention, "a plurality of" means two or more, unless otherwise explicitly specified.

[0059] Please see Figure 1 A method for matching and adjusting approval permissions for collaborative office use in a group enterprise includes the following steps:

[0060] S1: Extract all functional modules and data permission entries from the group enterprise collaborative office system, identify the interaction and scope of influence of each module and entry, classify and organize the modules and permissions, and form module and permission dependency records through comparison and summarization;

[0061] S2: Based on module and permission dependency records, extract key data and perform graphical visualization processing, analyze the dependency relationship of each module and permission, check potential conflict areas according to the analysis results, mark each conflict point, identify key connection points between modules, and output conflict point and key dependency graph;

[0062] S3: Based on conflict points and key dependency graphs, analyze the deficiencies in the current permission settings, reallocate the permission configuration of key connection points, verify the effectiveness of the new permission configuration through simulation tests based on the reallocation results, track changes in the organizational structure in real time, dynamically adjust the permission settings to match the corresponding changes, and output the verified and optimized permission configuration scheme.

[0063] S4: Establish a cross-departmental consultation platform to process and approve permission change requests in the optimized permission configuration scheme, record all change operations and pass the review, and output the group enterprise collaborative office permission change approval record.

[0064] Module and permission dependency records include module classification, permission classification, and interaction records. Conflict points and key dependency graphs include dependency relationship graphs, conflict area identification results, and key connection point records. Verification and optimization of permission configuration schemes include permission reconfiguration records, simulation test results, and dynamic permission adjustment records. Group enterprise collaborative office permission change approval records include change request records, operation records, and review status.

[0065] Please see Figure 2 The steps to obtain module and permission dependency records are as follows:

[0066] S111: Query the enterprise collaborative office system through the system interface, extract the raw data of all functional modules and data permission items, and generate an initial list of functional modules and data permission items;

[0067] By querying the system interface, the database of the enterprise collaborative office system is accessed one by one to obtain the raw data of functional modules and data permission items. The process involves strict data screening, mainly using standard SQL query statements to search for specific database fields such as module name, permission level, and user access count. Data screening operations remove items that do not meet the query conditions, such as incorrect user access data or expired module information, to ensure that the extracted data accurately reflects the current actual usage of the system. The accuracy of the data is guaranteed by repeatedly checking and verifying the query results, ensuring that the final generated data is an initial list of functional modules and data permission items containing all necessary information.

[0068] S112: Based on the initial list of functional modules and data permission items, perform data analysis, evaluate the interrelationships and impacts between each module and item, and generate module and permission interaction analysis records;

[0069] Based on the initial list of functional modules and data permission entries, a detailed analysis of the interrelationships and impact of each entry is conducted. This process primarily employs a data-by-item comparison method, verifying the data of each module and permission entry according to its function. Direct connections between each module and permission entry are identified and recorded, such as which users can access specific modules and which data is controlled by specific permissions. Furthermore, the consistency and integrity of the data are verified by manually checking module configuration files and permission setting logs. This manual checking helps confirm the logical relationships between data, resulting in more accurate interactive analysis records of modules and permissions, reflecting how modules and permissions depend on and influence each other in actual operation.

[0070] S113: Based on the module and permission interaction analysis records, perform logical grouping of modules and permissions, compare and summarize, and generate module and permission dependency records;

[0071] Based on the generated interaction analysis records of modules and permissions, the modules and permissions are categorized and organized, primarily through manual review. This includes reviewing the functional descriptions of each module and permission, grouping modules and permissions with similar functions together, and ensuring that each category is divided according to actual business needs and data processing flows. Subsequently, by comparing and analyzing the dependencies within and between groups, a clear dependency record between modules and permissions is formed, detailing how different modules and permissions interact. This supports subsequent system optimization and permission adjustment strategy formulation, ensuring that the generated dependency records are both detailed and easy to understand, providing accurate reference information.

[0072] Please see Figure 3 The steps for analyzing module and permission dependencies are as follows:

[0073] S211: Based on the module and permission dependency records, extract the module identifier and associated permission attributes, form a module attribute list, and generate the initial dataset;

[0074] Module identifiers and related permission attributes are extracted from module and permission dependency records to form a module attribute list. The list details the identifier of each module, its permission level, and its dependencies on other modules. By precisely defining SQL queries, all entries related to permission management are retrieved from the system database, including module access permissions, management levels, and detailed information on dependent modules. This ensures that the extracted data accurately reflects the current state and configuration of the modules. The retrieved data is cleaned and formatted to remove any redundant or outdated records, ensuring that the generated initial dataset has a high degree of consistency and completeness. This dataset will provide the foundational data support for constructing an accurate module dependency graph.

[0075] S212: Using the initial dataset, reveal the dependencies between modules through data association analysis, employing formulas...

[0076]

[0077] Calculate the dependency score matrix R between modules, construct and output the dependency graph, where A represents the module attribute matrix, D represents the permission data matrix, and D... T The transpose of the permission data matrix, |A·D T | represents matrix A·D T The absolute value is used to handle negative scores and balance the impact of dependencies;

[0078] The attribute matrix A of the collected modules is shown below:

[0079]

[0080] The permission data matrix D is as follows:

[0081]

[0082] Then A·D T The calculation is as follows:

[0083]

[0084] Take the absolute value and calculate the dependency score matrix R:

[0085]

[0086] The results show that when there is a direct permission dependency (i.e., 1), the score is 1, while the absence of a dependency (i.e., 0 converted to infinity) indicates that such a dependency is not allowed. This means that the permission dependencies between modules are intuitively displayed in the dependency graph. The results of the further derivation steps will be used for permission conflict detection and critical dependency analysis.

[0087] S213: Perform in-depth analysis of the dependency graph to identify key dependencies and potentially complex areas of permissions, map the permission dependencies between modules, and generate inter-module dependency analysis results;

[0088] A thorough analysis of the graphical dependency representation is conducted to identify direct and indirect dependencies between modules. The analysis meticulously examines the connection strength between each module and other modules, as well as the compatibility of each module's permission requests with the permission settings of other modules. For modules with high dependencies, the potential impact on system stability is further analyzed. By comparing module permission configurations with dependencies, inconsistencies or conflicts in permission configurations are clearly identified. Each potential conflict area is marked, and every critical connection point identified during the analysis is meticulously recorded. The analysis results will be used to guide system optimization configurations to enhance overall system security and stability, ensuring that operations between modules do not lead to system instability or security vulnerabilities due to incorrect permissions or improper configurations.

[0089] Please see Figure 4 The steps to obtain the conflict points and key dependency graph are as follows:

[0090] S221: Using the results of inter-module dependency analysis, check the permission settings of all modules, identify potential conflict areas between permission configurations, and generate preliminary conflict check records;

[0091] Data is extracted from the inter-module dependency analysis results. Potential conflict areas between permissions are identified by examining the permission configuration of each module. The implementation of this process relies on a detailed review of the system configuration files and data mining. By parsing the contents of the configuration files, the permission settings of each module are identified and compared with the dependencies of other modules, including the extraction of permission levels and the mapping of inter-module dependencies. This helps to determine the key areas that may cause permission conflicts. The generated preliminary conflict check records provide the necessary basic data for subsequent steps.

[0092] S222: Based on the initial conflict check records, analyze each record item, mark all potential conflict points and key dependencies between modules, and use formulas...

[0093]

[0094] Calculate the total probability of conflict C, and generate conflict and dependency labeled records, where p i q represents the permission level of module i. i This represents the permission level of the dependent modules, and n represents the total number of modules.

[0095] Define three modules with permission levels p = [2, 4, 5] and dependent modules with permission levels q = [1, 2, 5] (permission levels range from 1 to 5, with 5 being the highest and 1 being the lowest). The total number of modules is n = 3.

[0096] Calculate the ratio of each term and sum them:

[0097]

[0098] The square root of the absolute ratio of the averages:

[0099]

[0100] Calculate the total probability of conflict:

[0101]

[0102] The results show that the conflict probability is approximately 0.745 in the existing module and dependency settings, representing the average conflict risk in the system. This helps to further analyze and optimize the permission configuration between modules to reduce the conflict risk.

[0103] S223: Integrate conflict and dependency tagging records, use data visualization technology to visually display key conflict points and key dependencies, and output a conflict point and key dependency graph;

[0104] By leveraging tagged conflict and dependency records, a comprehensive conflict point and dependency graph is constructed using data visualization techniques. This graph graphically displays the direct and indirect dependencies between modules. This step involves transforming complex data relationships into visual graphics, including node representations of modules and edge connections of dependencies. Each node in the graph is determined by specific module data, including module identifiers and permission levels. The thickness and color variations of dependency edges reflect the severity of conflicts and the importance of dependencies. This provides intuitive analytical tools to help quickly identify key problem areas and take targeted measures.

[0105] Please see Figure 5 The steps for reallocating permissions for critical connection points are as follows:

[0106] S311: By analyzing conflict points and key dependency graphs, identify specific conflict points in permission configuration, including connection points of excessive permissions and missing permissions, and generate specific conflict point identification results;

[0107] During the identification process of permission configuration, permission data for each connection point is first collected, then sorted and compared, with particular attention paid to connection points with abnormally high or low permission settings. This comparison identifies which connection points have excessive or insufficient permissions. Further detailed review is then conducted on these identified conflict points, including examining their position and role in the critical dependency graph, and how their permission configurations affect the overall system's security and efficiency. Finally, a detailed conflict point report is compiled based on the analysis. This report will guide subsequent permission reconfiguration, ensuring that the permission settings for each connection point meet the overall system requirements and security standards.

[0108] S312: Based on the specific identification results of conflict points, reconfigure permissions for key connection points using a formula.

[0109]

[0110] Calculate the new permission value NP j Optimize the permission settings for each key node and generate a permission reconfiguration scheme, in which OP j TP represents the current permission value of connection point j, and TP represents the total permission value of all connection points in the system.

[0111] Identify 10 connection points, and the current permission value (OP) for each connection point. j Given {10, 20, 30, 40, 50, 60, 70, 80, 90, 100}, the total permissions (TP) of all connection points is 550.

[0112] For the permission reconfiguration of connection point j=1, substitute OP1=10 into the formula, and the calculation process is as follows:

[0113]

[0114] This indicates that in the permission reconfiguration scheme, the new permission value of the first connection point is approximately 0.00575. The result shows that the original permission value was successfully converted into a relative permission ratio within the system through adjustment, and this ratio will be implemented in the system's permission management policy.

[0115] S313: Application permission reconfiguration scheme, test the response and processing efficiency of the new configuration, confirm that each critical connection point runs effectively according to the new configuration, and output the reconfiguration results of critical connection point permissions;

[0116] After implementing the permission reconfiguration scheme, a comprehensive test of the new permission configuration is conducted. Simulated scenarios are set up to test the response and processing efficiency of the new configuration, including simulating high load, permission conflicts, and abnormal data access, to verify the stability and responsiveness of the new configuration. Furthermore, the permission execution status of each connection point is monitored and evaluated to ensure that permissions at all connection points are correctly implemented according to the new scheme. Feedback and system logs after the permission configuration implementation are tracked to analyze the specific impact of the permission change, such as improved system performance and reduced security risks. This data supports our evaluation of the effectiveness of the new configuration, ultimately leading to a conclusion and an implementation results report. This report details the actual performance of the new permission configuration and any areas requiring adjustment.

[0117] Please see Figure 6 The steps to verify and obtain the optimized permission configuration scheme are as follows:

[0118] S321: Based on the reconfiguration results of permissions at key connection points, comprehensive simulation tests are conducted by creating test scenarios with different user behaviors and system loads to reflect the target operating conditions and potential security risks, analyze whether the new permission settings meet the expected operating and security requirements, and generate simulation test results;

[0119] In creating test scenarios with different user behaviors and system loads, various scenario simulations were planned in detail, such as daily operation simulation, high-pressure load simulation, and security vulnerability testing. The tests aimed to verify the response and security of the new permission configuration under different operating conditions. For each test scenario, the system's reaction time, permission processing efficiency, and potential security vulnerabilities were recorded. The data was compared with the expected goals to evaluate whether the performance of the permission settings in each scenario met the company's security standards and operational requirements, thereby confirming the effectiveness of the new configuration. Detailed simulation test results were collected, which will serve as the basis for evaluating the success of the new permission configuration.

[0120] S322: Based on simulation test results, monitor real-time changes in the organizational structure of the group enterprise, automatically capture and respond to organizational change data, update permission configuration in real time, and generate dynamic adjustment results of permission configuration.

[0121] By monitoring real-time changes in the organizational structure, the system adjusts permission configurations in real time to adapt to departmental restructuring or role changes. During this process, the system continuously tracks any structural changes in the organization, including the creation or removal of positions, the merging or splitting of departments, etc. It automatically updates the permission settings in the system according to the changes, ensuring a rapid response to each organizational change. By comparing the permission configuration data before and after the change, the system evaluates the accuracy and timeliness of the adjustment and generates dynamically adjusted permission configuration results, helping management to quickly understand the immediate effects of the adjustment and areas that may need further optimization.

[0122] S323: Based on the results of dynamically adjusting the permission configuration, repeatedly conduct simulation tests to verify the adjustment effect, collect operation data and security logs to analyze the long-term effectiveness and potential security risks of the configuration, and output the verified and optimized permission configuration scheme;

[0123] After adjusting the permission configuration, repeated simulation tests were conducted to confirm the actual effect of the adjustment. Long-term actual operation monitoring of the configuration was also carried out. By collecting data and security logs during the operation, the performance of the new permission configuration in daily use was analyzed in detail, such as the processing time of permission requests and approvals, and the frequency of permission conflicts. At the same time, the data can also help assess the security of the configuration, such as whether unauthorized access has occurred. Finally, by sorting out the information, a comprehensive evaluation report was formed. The report details the efficiency and security of the permission configuration and provides suggestions for possible future improvements to ensure the continuous adaptability and protection capabilities of the permission system.

[0124] Please see Figure 7 The steps to obtain the approval record for changes in collaborative office permissions within a group enterprise are as follows:

[0125] S411: Integrate permission change requests collected by the group's enterprise departments, combine them with the verified and optimized permission configuration scheme, conduct multi-department collaboration, and output a cross-departmental negotiation platform architecture.

[0126] When designing the architecture of the cross-departmental negotiation platform, the basic requirements of each department for access control are first collected, such as processing speed, security requirements, and the operation permissions of various users. This establishes the platform's basic functions and security standards. Then, based on the requirements, suitable architectural patterns and database design methods are selected. For example, modular design is used to increase the system's flexibility and maintainability, and layered security measures are used to ensure data security. During the analysis process, tools such as data flow diagrams and use case diagrams are used to clarify the data flow and functional interfaces between modules. Through the analysis and design process, a negotiation platform architecture that meets the needs of cross-departmental collaboration is constructed, ensuring that the platform can efficiently handle various permission change requests while ensuring the security of data processing.

[0127] S412: Based on the cross-departmental consultation platform architecture, it processes permission change requests, receives permission change requests submitted by departments, classifies, analyzes, and preliminarily approves the requests, and generates a preliminary permission change record.

[0128] Based on the established cross-departmental negotiation platform architecture, when developing the permission change request processing module, detailed planning is done on how the module receives and categorizes permission requests from different departments. For example, requests are divided into ordinary modifications, urgent modifications, etc. Each type of request is processed according to a preset process. For instance, urgent modification requests will be processed first, while ordinary requests will be queued in order of submission time. In addition, the module also needs to perform preliminary data validation to exclude illegal or incorrectly formatted requests, ensuring that all requests entering the processing flow are valid and compliant. The implementation of this process relies on predefined data validation rules and processing protocols, such as using regular expressions for format validation and using preset conditions for data legality checks. Through these specific operations, permission change records that have undergone preliminary processing and are ready for final review are generated.

[0129] S413: Based on the preliminary processing of permission change records, conduct a final review and record of all permission change operations, verify that each permission change matches the group enterprise's policies and security standards, and generate the group enterprise's collaborative office permission change approval record;

[0130] During the final review process, the permission change records that have undergone preliminary processing are subject to a final review. This includes a detailed review of the change records, such as verifying the necessity and rationality of the changes, checking whether the changed permission settings meet security standards, and whether there are sufficient logs and audit trails to support the change operations. This ensures that each change has undergone rigorous review, and the approval process is also recorded to generate a detailed approval report. Through this series of specific review and recording steps, a compliant group enterprise collaborative office permission change approval record is finally generated, ensuring the compliance and transparency of the entire change process.

[0131] A collaborative office approval permission matching and adjustment system for group enterprises includes:

[0132] The raw data analysis module extracts the raw data of all functional modules and data permission items of the group enterprise, evaluates the interrelationships and impacts between each module and item, performs logical grouping of modules and permissions, compares and summarizes, and generates module and permission dependency records.

[0133] The dependency identification module extracts module identifiers and associated permission attributes based on module and permission dependency records, reveals the dependencies between modules through data correlation analysis, identifies key dependencies and potentially complex permission areas, and generates inter-module dependency analysis results.

[0134] The conflict point visualization module uses the results of inter-module dependency analysis to identify potential conflict areas between permission configurations, marks all potential conflict points and key dependencies between modules, and outputs a conflict point and key dependency graph using data visualization techniques.

[0135] The permission adjustment analysis module identifies specific conflict points in the permission configuration by analyzing conflict points and key dependency graphs, performs targeted permission reconfiguration on key connection points, tests the response and processing efficiency of the new configuration, and outputs the permission reconfiguration results of key connection points.

[0136] The simulation test verification module performs comprehensive simulation tests based on the reconfiguration results of permissions at key connection points, analyzes whether the new permission settings meet the expected operational and security requirements, automatically captures and responds to organizational change data, updates permission configurations in real time, repeatedly performs simulation tests to verify the adjustment effect, and outputs the verified and optimized permission configuration scheme.

[0137] The permission change approval module integrates permission change requests collected from various departments within the group, combines them with a validated and optimized permission configuration scheme, facilitates multi-department collaboration, processes permission change requests, reviews, verifies, and records all permission change operations, and generates group-wide collaborative office permission change approval records.

[0138] The above are merely preferred embodiments of the present invention and are not intended to limit the present invention in any other way. Any person skilled in the art may make changes or modifications to the above-disclosed technical content to create equivalent embodiments that can be applied to other fields. However, any simple modifications, equivalent changes, and modifications made to the above embodiments based on the technical essence of the present invention without departing from the scope of the present invention shall still fall within the protection scope of the present invention.

Claims

1. A method for matching and adjusting approval permissions for collaborative office work in a group enterprise, characterized in that, Includes the following steps: Extract all functional modules and data permission entries from the group's collaborative office system, identify the interaction and scope of influence of each module and entry, classify and organize the modules and permissions, and form a module and permission dependency record through comparison and summarization; Based on the module and permission dependency records, key data is extracted and graphically visualized. The dependency relationship between each module and permission is analyzed. Potential conflict areas are checked according to the analysis results. Each conflict point is marked and key connection points between modules are identified. A conflict point and key dependency graph are output. Based on the conflict points and key dependency graph, analyze the deficiencies in the current permission settings, reallocate the permission configuration of key connection points, verify the effectiveness of the new permission configuration through simulation tests based on the reallocation results, track changes in the organizational structure in real time, dynamically adjust the permission settings to match the corresponding changes, and output the verified and optimized permission configuration scheme. Establish a cross-departmental consultation platform to process and approve permission change requests in the verified and optimized permission configuration scheme, record all change operations and pass the review, and output the group enterprise collaborative office permission change approval record; The steps for analyzing the module and permission dependencies are as follows: Based on the module and permission dependency records, extract the module identifier and associated permission attributes to form a module attribute list and generate the initial dataset; Using the initial dataset, data correlation analysis reveals the dependencies between modules, employing formulas. Calculate the dependency score matrix between modules Construct and output a dependency graph, where, Represents the module attribute matrix. Represents the permission data matrix. The transpose of the permission data matrix. Representation matrix The absolute value is used to handle negative scores and balance the impact of dependencies; The dependency graph is subjected to in-depth analysis to identify key dependencies and potentially complex permission areas, map the permission dependencies between modules, and generate inter-module dependency analysis results. The steps for obtaining the conflict points and key dependency graph are as follows: Using the inter-module dependency analysis results, check the permission settings of all modules, identify potential conflict areas between permission configurations, and generate preliminary conflict check records; Based on the preliminary conflict check records, each record item is analyzed to mark all potential conflict points and key dependencies between modules, using a formula... Calculate the total probability of conflict Generate conflict and dependency tag records, where, Representative module permission levels, This represents the permission level of the dependent modules. Represents the total number of modules; Integrate the conflict and dependency marker records, use data visualization technology to visually display key conflict points and key dependencies, and output a conflict point and key dependency graph; The steps for reallocating the permissions configuration of the critical connection points are as follows: By analyzing the conflict points and key dependency graph, specific conflict points in the permission configuration are identified, including connection points of excessive permissions and missing permissions, and specific conflict point identification results are generated. Based on the specific identification results of the conflict points, targeted permission reconfiguration is performed on key connection points using a formula. Calculate new permission values Optimize the permission settings for each key node and generate a permission reconfiguration scheme, in which... Representing connection point The current permission value, Represents the total permissions of all connection points in the system; Apply the aforementioned permission reconfiguration scheme to test the response and processing efficiency of the new configuration, confirm that each critical connection point is operating effectively according to the new configuration, and output the permission reconfiguration results of the critical connection points.

2. The method for matching and adjusting approval permissions for collaborative office work in group enterprises according to claim 1, characterized in that, The steps for obtaining the module and permission dependency records are as follows: By querying the enterprise collaborative office system through the system interface, the original data of all functional modules and data permission items are extracted, and an initial list of functional modules and data permission items is generated. Based on the initial list of functional modules and data permission entries, data analysis is performed to evaluate the interrelationships and impacts between each module and entry, and to generate module and permission interaction analysis records. Based on the module and permission interaction analysis records, the modules and permissions are logically grouped, compared and summarized, and module and permission dependency records are generated.

3. The method for matching and adjusting approval permissions for collaborative office work in group enterprises according to claim 1, characterized in that, The steps for obtaining the optimized permission configuration scheme are as follows: Based on the reconfiguration results of the key connection point permissions, comprehensive simulation tests are conducted by creating test scenarios with different user behaviors and system loads to reflect the target operating conditions and potential security risks, analyze whether the new permission settings meet the expected operation and security requirements, and generate simulation test results. Based on the simulation test results, monitor real-time changes in the group's organizational structure, automatically capture and respond to organizational change data, update permission configurations in real time, and generate dynamically adjusted permission configuration results. Based on the dynamically adjusted permission configuration results, repeated simulation tests are conducted to verify the adjustment effect. Operation data and security logs are collected to analyze the long-term effectiveness and potential security risks of the configuration, and the optimized permission configuration scheme is output.

4. The method for matching and adjusting approval permissions for collaborative office work in group enterprises according to claim 3, characterized in that, The steps for obtaining the approval record of changes to the collaborative office permissions of the group enterprise are as follows. By integrating permission change requests collected from various departments within the group, and combining them with the verified and optimized permission configuration scheme, multi-department collaboration is conducted to output a cross-departmental negotiation platform architecture. Based on the aforementioned cross-departmental consultation platform architecture, permission change requests are processed. Permission change requests submitted by departments are received, the requests are classified, analyzed, and preliminarily approved, and a preliminary permission change record is generated. Based on the preliminary processed permission change records, all permission change operations are subject to final review and recording to verify that each permission change matches the group company's policies and security standards, and to generate the group company's collaborative office permission change approval record.

5. A collaborative office approval permission matching and adjustment system for group enterprises, characterized in that, The system is used to execute the group enterprise collaborative office approval permission matching and adjustment method according to any one of claims 1-4, including: The raw data analysis module extracts the raw data of all functional modules and data permission items of the group enterprise, evaluates the interrelationships and impacts between each module and item, performs logical grouping of modules and permissions, compares and summarizes, and generates module and permission dependency records. The dependency identification module extracts module identifiers and associated permission attributes based on the module and permission dependency records, reveals the dependencies between modules through data correlation analysis, identifies key dependencies and potentially complex permission areas, and generates inter-module dependency analysis results. The conflict point visualization module uses the inter-module dependency analysis results to identify potential conflict areas between permission configurations, marks all potential conflict points and key dependencies between modules, and outputs a conflict point and key dependency graph using data visualization technology. The permission adjustment analysis module analyzes the conflict points and key dependency graphs to identify specific conflict points in the permission configuration, reconfigures the permissions of key connection points in a targeted manner, tests the response and processing efficiency of the new configuration, and outputs the permission reconfiguration results of key connection points. The simulation test verification module performs a comprehensive simulation test based on the reconfiguration results of the key connection point permissions, analyzes whether the new permission settings meet the expected operation and security requirements, automatically captures and responds to organizational change data, updates the permission configuration in real time, repeats the simulation test to verify the adjustment effect, and outputs the verified and optimized permission configuration scheme. The permission change approval module integrates permission change requests collected by departments of the group enterprise, combines the verified and optimized permission configuration scheme, conducts multi-department collaboration, processes permission change requests, reviews, verifies and records all permission change operations, and generates group enterprise collaborative office permission change approval records.

Images