Enterprise project management system and method oriented to multi-project collaboration

Abstract

The invention provides an enterprise project management system and method for multi-project collaboration, and relates to the technical field of project management, and the method comprises the steps: obtaining a multi-project collaboration sharing platform; when a first sharing user accesses the multi-project collaborative sharing platform, obtaining a user type of the first sharing user; when the first sharing user belongs to the first type of users, performing permission verification according to the first verification channel, and performing partial access on the multi-project collaborative sharing platform according to the access permission level; and when the first sharing user belongs to the second type of users, performing permission verification according to the second verification channel, and performing partial access on the multi-project collaborative sharing platform according to the access permission level. According to the method and the device, the technical problem that the security and confidentiality of enterprise data are affected due to the fact that different requirements of internal personnel and external customers of an enterprise cannot be effectively distinguished in the prior art can be solved, and the technical effects of effectively improving the data security, reducing the information leakage risk and improving the working efficiency are achieved.

Description

Technical Field

[0001] The present application relates to the field of project management technology, and in particular to an enterprise project management system and method for multi-project collaboration. Background Art

[0002] With the rapid development of information technology, enterprise project management systems have gradually become an indispensable tool for modern enterprises in their daily operations. However, existing enterprise project management systems still have some shortcomings in meeting the needs of different types of users, ensuring information security, and supporting multi-project collaboration.

[0003] At present, most existing permission management systems are based on fixed role allocation models and fail to dynamically adjust according to users' actual behavior and changes in project requirements. For example, in many project management systems, once user permissions are set, it is difficult to flexibly adjust them according to project progress, task changes, or changes in user requirements. Therefore, some users may obtain too many permissions during project implementation, causing them to access information that is not related to their responsibilities, and may even leak sensitive corporate data.

[0004] In summary, there are technical problems in the prior art that the enterprise project management system cannot effectively distinguish the different needs of internal enterprise personnel and external customers, resulting in excessive sharing or improper access to information, thereby affecting the security and confidentiality of enterprise data. Summary of the invention

[0005] The purpose of this application is to provide an enterprise project management system and method for multi-project collaboration, so as to solve the technical problem in the prior art that the enterprise project management system cannot effectively distinguish the different needs of internal enterprise personnel and external customers, resulting in excessive sharing or improper access of information, thereby affecting the security and confidentiality of enterprise data.

[0006] In view of the above problems, the present application provides an enterprise project management system and method for multi-project collaboration.

[0007] In a first aspect, the present application provides an enterprise project management system for multi-project collaboration, including: a shared platform acquisition module, the shared platform acquisition module is used to acquire a multi-project collaborative sharing platform, the multi-project collaborative sharing platform includes a dual-channel verification module; a user type acquisition module, the user type acquisition module is used to acquire the user type of the first shared user when the first shared user accesses the multi-project collaborative sharing platform, wherein the user type includes a first type of user and a second type of user, wherein the first type of user is an internal employee of the enterprise, and the second type of user is a customer-connecting employee of the enterprise; a first type of user access module, the first type of user access module is used to perform permission verification on the identity information of the first shared user according to the first verification channel of the dual-channel verification module when the first shared user belongs to the first type of user, match the access permission level, and partially access the multi-project collaborative sharing platform according to the access permission level; a second type of user access module, the second type of user access module is used to perform permission verification on the identity information of the first shared user according to the second verification channel of the dual-channel verification module when the first shared user belongs to the second type of user, match the access permission level, and partially access the multi-project collaborative sharing platform according to the access permission level.

[0008] In the second aspect, the present application also provides an enterprise project management method for multi-project collaboration, including: obtaining a multi-project collaborative sharing platform, the multi-project collaborative sharing platform including a dual-channel verification module; when a first shared user accesses the multi-project collaborative sharing platform, obtaining the user type of the first shared user, wherein the user type includes a first type of user and a second type of user, wherein the first type of user is internal personnel of the enterprise, and the second type of user is the enterprise's customer liaison personnel; when the first shared user belongs to the first type of user, performing authority verification on the identity information of the first shared user according to the first verification channel of the dual-channel verification module, matching the access permission level, and partially accessing the multi-project collaborative sharing platform according to the access permission level; when the first shared user belongs to the second type of user, performing authority verification on the identity information of the first shared user according to the second verification channel of the dual-channel verification module, matching the access permission level, and partially accessing the multi-project collaborative sharing platform according to the access permission level.

[0009] The technical solution provided in the present application has at least the following technical effects or advantages: by acquiring a multi-project collaborative sharing platform, the multi-project collaborative sharing platform includes a dual-channel verification module; when a first shared user accesses the multi-project collaborative sharing platform, the user type of the first shared user is acquired, wherein the user type includes a first type of user and a second type of user, wherein the first type of user is an internal employee of the enterprise, and the second type of user is a customer contact person of the enterprise; when the first shared user belongs to the first type of user, the identity information of the first shared user is authenticated according to the first verification channel of the dual-channel verification module, the access permission level is matched, and partial access to the multi-project collaborative sharing platform is performed according to the access permission level; when the first shared user belongs to the second type of user, the identity information of the first shared user is authenticated according to the second verification channel of the dual-channel verification module, the access permission level is matched, and partial access to the multi-project collaborative sharing platform is performed according to the access permission level. That is to say, by realizing the technical goal of a refined permission management system that dynamically adjusts permissions based on user roles and behaviors, the technical effect of effectively improving data security, reducing the risk of information leakage and improving work efficiency is achieved.

[0010] The above description is only an overview of the technical solution of the present application. In order to more clearly understand the technical means of the present application, it can be implemented according to the contents of the specification, and in order to make the above and other purposes, features and advantages of the present application more obvious and easy to understand, the specific implementation methods of the present application are specifically cited below. It should be understood that the content described in this section is not intended to identify the key or important features of the embodiments of the present application, nor is it intended to limit the scope of the present application. Other features of the present application will become easy to understand through the following description. BRIEF DESCRIPTION OF THE DRAWINGS

[0011] In order to more clearly illustrate the technical solutions in the present application or the prior art, the drawings required for use in the embodiments or the description of the prior art will be briefly introduced below. Obviously, the drawings in the following description are only exemplary, and for ordinary technicians in this field, other drawings can be obtained based on the provided drawings without paying any creative work.

[0012] Figure 1 This is a schematic diagram of the structure of the enterprise project management system for multi-project collaboration in this application; Figure 2 This is a flowchart of the enterprise project management method for multi-project collaboration in this application.

[0013] Description of reference numerals: A sharing platform acquisition module 11, a user type acquisition module 12, a first type of user access module 13, and a second type of user access module 14. DETAILED DESCRIPTION

[0014] This application solves the technical problem in the prior art that the enterprise project management system cannot effectively distinguish the different needs of internal enterprise personnel and external customers, resulting in excessive sharing or improper access of information, thereby affecting the security and confidentiality of enterprise data by providing an enterprise project management system and method for multi-project collaboration. The application achieves the technical goal of a refined permission management system that dynamically adjusts permissions based on user roles and behaviors, achieving the technical effect of effectively improving data security, reducing the risk of information leakage, and improving work efficiency.

[0015] Below, the technical solutions in the present application will be clearly and completely described with reference to the accompanying drawings. Obviously, the described embodiments are only part of the embodiments of the present application, rather than all of the embodiments of the present application. It should be understood that the present application is not limited to the example embodiments described herein. Based on the embodiments of the present application, all other embodiments obtained by ordinary technicians in this field without creative work are within the scope of protection of the present application. It should also be noted that, for the convenience of description, only the parts related to the present application are shown in the accompanying drawings, rather than all of them.

[0016] For example, please refer to the attached Figure 1 , this application provides an enterprise project management system for multi-project collaboration, specifically including: The sharing platform acquisition module 11 is used to acquire a multi-project collaborative sharing platform, and the multi-project collaborative sharing platform includes a dual-channel verification module.

[0017] Specifically, the multi-project collaborative sharing platform is a system platform that supports collaboration and information sharing among multiple projects. The multi-project collaborative sharing platform includes a dual-channel verification module. For internal personnel of the enterprise, the multi-project collaborative sharing platform provides a partial access function with permissions, such as enterprise employees can access project data related to them according to their roles and responsibilities. The partial access permissions for customer personnel can access information related to their projects, such as progress reports or deliverables, through the multi-project collaborative sharing platform. The dual-channel verification module effectively protects the confidential information of the enterprise, while ensuring that customers can keep abreast of the progress and relevant data of the project, increasing the security of the enterprise project management system.

[0018] A user type acquisition module 12 is used to obtain the user type of the first shared user when the first shared user accesses the multi-project collaborative sharing platform, wherein the user type includes a first type of user and a second type of user, wherein the first type of user is an internal employee of the enterprise, and the second type of user is a person who connects the enterprise with customers.

[0019] Specifically, the first shared user is the user to be accessed. When the first shared user accesses the multi-project collaborative sharing platform, the multi-project collaborative sharing platform will first obtain the user type of the user. User type refers to the classification of users according to their identities and roles, so as to achieve different permissions and access control. Among them, user types include first-class users and second-class users. The first-class users are internal personnel of the enterprise, and the second-class users are customer personnel connected to the enterprise. They are used to provide different levels of information access rights according to user needs and permissions.

[0020] The first category user access module 13 is used for, when the first shared user belongs to the first category of users, to verify the identity information of the first shared user according to the first verification channel of the dual-channel verification module, match the access permission level, and partially access the multi-project collaborative sharing platform according to the access permission level.

[0021] Specifically, when the first shared user belongs to the first category of users, the multi-project collaborative sharing platform will verify the user's identity information according to the first verification channel of the dual-channel verification module. For example, the first verification channel may include the step of entering a password or further confirming the user's identity through SMS verification codes or fingerprint recognition, effectively preventing unauthorized users from accessing the system, thereby protecting the security of the multi-project collaborative sharing platform.

[0022] After identity authentication, the enterprise project management system for multi-project collaboration will match the corresponding access permission level based on the identity information and verification results of the first shared user. Access permission levels refer to the different permission levels set by the multi-project collaborative sharing platform based on user roles, responsibilities, and the scope of data that needs to be accessed. For example, the access permissions of the first category of users can view and operate data of multiple projects. According to the matched access permission level, the multi-project collaborative sharing platform will partially access the first shared user, access the functions and information related to his / her responsibilities in the multi-project collaborative sharing platform, and cannot view or operate other content that is not within his / her scope of responsibilities, ensuring that users of different roles can work effectively within their authority, while also ensuring the security and privacy of information.

[0023] The second category user access module 14 is used for, when the first shared user belongs to the second category of users, to perform authority verification on the identity information of the first shared user according to the second verification channel of the dual-channel verification module, match the access permission level, and perform partial access to the multi-project collaborative sharing platform according to the access permission level.

[0024] Specifically, when the first shared user belongs to the second category of users, the multi-project collaborative sharing platform will verify the user's identity information according to the second verification channel of the dual-channel verification module. The second verification channel may include further confirmation of the user's identity through email verification code, SMS verification code or other means. The second category of users are customers or external partners of the enterprise, so their access rights may be relatively limited, ensuring that external personnel can only access information related to them without affecting sensitive data within the enterprise. The multi-project collaborative sharing platform will match the access rights level of the second category of users according to their identity information. The access rights level is a different level set by the platform according to the user's role and responsibilities, which controls the scope of data and operation permissions that users can access. For example, enterprise customers may only be able to view the project's progress report, deliverables or key node information, but cannot modify the core content of the project such as the plan and budget. The multi-project collaborative sharing platform will partially access the second category of users according to the access rights level, allowing access to project data related to themselves, ensuring the customer's right to know, and also ensuring the security and privacy of enterprise data.

[0025] The enterprise project management system for multi-project collaboration can achieve the technical goal of a refined permission management system that dynamically adjusts permissions based on user roles and behaviors, thereby achieving the technical effects of effectively improving data security, reducing information leakage risks, and improving work efficiency.

[0026] Furthermore, the present application also includes: dividing enterprise functions for the first user group and obtaining multiple layers of enterprise user tags; based on the multiple layers of enterprise user tags, establishing sensitivity coefficients of each layer of user tags for various types of information in the project and obtaining a first set of sensitivity coefficients; based on the first set of sensitivity coefficients, generating access rights levels for each piece of information; based on the access rights levels for each piece of information, configuring accessible information items corresponding to each layer of enterprise user tags, and establishing a first mapping relationship based on the accessible information items corresponding to each layer of enterprise user tags; and constructing the first verification channel according to the first mapping relationship.

[0027] Specifically, the first category of user groups is classified according to different functions and responsibilities within the enterprise, and each user group is given different labels according to its role in the enterprise, obtaining multiple layers of enterprise user labels. For example, project managers are labeled as "project management" and technicians are labeled as "technical support" based on employees' positions, functions or scope of responsibilities, which helps to provide corresponding access rights and functions to different users more accurately.

[0028] Based on the multi-layer enterprise user tags, establish the sensitivity coefficient of each layer of user tags for various types of information in the project. The sensitivity coefficient is used to evaluate the confidentiality of each type of information and obtain the first sensitivity coefficient set. For example, financial data has a low sensitivity coefficient for "financial personnel", but has a high sensitivity coefficient for "technical support layer", so as to better set access rights.

[0029] Different information is assigned different access rights levels through the first sensitivity coefficient set. The access right level refers to the scope and depth of information that the platform allows different users to access. For example, the progress report of a project is of low sensitivity to the "project manager", so the access level of the progress report of the project is higher and more detailed data can be viewed.

[0030] According to the access rights level of each piece of information, the accessible information items corresponding to each layer of enterprise user tags are configured, and the first mapping relationship is established according to the accessible information items corresponding to each layer of enterprise user tags. According to the access rights level of the information, different enterprise user tags are matched with the specific information that can be accessed. For example, the "project manager" can access the detailed budget, progress, resource allocation and other information of the project, while the "technical support layer" can only view the resource allocation and other information of the project.

[0031] According to the first mapping relationship, a corresponding first verification channel is constructed. The first verification channel refers to a channel for performing identity authentication and determining access rights based on the identity and access rights of the user. The identity of the first category of user groups is confirmed by double verification and other methods. Based on the verification results and the mapping relationship, the information that the user can access is ultimately determined to ensure that each user can only access the data for which he is authorized.

[0032] User groups are labeled by functional division, and the confidentiality level of each type of information is set according to the sensitivity coefficient. The accessibility of information is determined according to the access permission level, and a mapping relationship is established to correspond each layer of user labels to the corresponding information items. Finally, access control is performed through the verification channel to ensure that each user can only access information related to his or her responsibilities and roles, ensuring data security and privacy protection.

[0033] Furthermore, the present application also includes: identifying the participating projects of the first sharing user; identifying the project collaboration indicators of the participating projects of the first sharing user and other projects, and outputting a project collaboration indicator set; generating a first sensitive weight coefficient based on the project collaboration indicator set; weighting the sensitivity coefficients of various types of information in different projects according to the first sensitive weight coefficient, and outputting an updated first sensitive coefficient set.

[0034] Specifically, confirm the specific project that the first sharing user is involved in. Through user information and project data, it is possible to identify the projects that the user is associated with. For example, a "project manager" may be involved in multiple projects, while an "ordinary employee" may only be involved in a specific project. By clarifying the user's work scope, necessary data support is provided for subsequent operations.

[0035] Next, analyze the projects in which the first sharing user participates and compare them with the collaboration data of other projects to identify the synergy indicators between projects. Project synergy indicators refer to data on the relevance, resource sharing, and progress synchronization between different projects. For example, if two projects share resources or have interdependent phased results, the synergy indicators between the two are higher. Organize the project synergy indicators into a project synergy indicator set to facilitate subsequent analysis.

[0036] Based on the project collaboration indicator set, the first sensitive weight coefficient is generated to reflect the impact of the collaboration degree between different projects on the sensitivity of information. For example, projects with high collaboration become more sensitive because information involves multiple parties sharing, so the sensitivity coefficient is higher. The first sensitive weight coefficient helps to further refine the protection measures for information and ensure that data security in projects with high collaboration is additionally guaranteed.

[0037] The sensitivity coefficients of various types of information in different projects are weighted according to the first sensitive weight coefficients, that is, the sensitivity coefficients of various types of information are dynamically adjusted according to the collaborative relationship between the projects, and an updated first sensitivity coefficient set is output. Among them, when a project is highly collaborative with multiple other projects, the information related to these projects may be given a higher sensitivity coefficient. For example, a technical solution may involve resources from multiple collaborative projects, so the sensitivity of the technical solution needs to be appropriately improved to prevent leakage. The adjusted sensitivity coefficient set reflects the sensitivity of each information item in different project collaborative environments.

[0038] By identifying the projects in which users participate, analyzing the collaborative relationships between projects, calculating collaborative indicators, and generating sensitive weight coefficients based on these collaborative indicators, the sensitivity coefficient of the information is finally adjusted to ensure that the sensitivity of information is properly managed and protected in a multi-project collaborative environment, thereby improving the security and flexibility of the system.

[0039] Furthermore, the present application also includes: dividing customer functions for the second user group and obtaining multiple layers of customer user tags; establishing sensitivity coefficients of each layer of customer user tags for various types of information in the project based on the multiple layers of customer user tags, and obtaining a second set of sensitivity coefficients; generating access rights levels for each type of information based on the second set of sensitivity coefficients; configuring accessible information items corresponding to each layer of customer user tags based on the access rights levels for each type of information, and establishing a second mapping relationship based on the accessible information items corresponding to each layer of customer user tags; and constructing the second verification channel according to the second mapping relationship.

[0040] Specifically, customers are classified according to the different functional relationships between the enterprise and the customers, and different labels are given to each customer group, so as to better manage the access needs and information sensitivity of different customers. For example, the enterprise may have an "account manager" who is directly involved in the project, or an "account representative" who is only responsible for reviewing the project report. By dividing customers into multiple levels of functions, it is possible to provide tailored information access rights for customers with different functions.

[0041] Based on the multi-layer customer user tags, establish the sensitivity coefficient of each layer of customer user tags for various types of information in the project, reflecting the customer's sensitivity to a certain type of information, and obtain the second sensitivity coefficient set. It varies according to the customer's function. For example, a "project account manager" may need to access more detailed project data, so the sensitivity coefficient is lower; while a "customer representative" who is only responsible for monitoring the progress of the project may only be able to access summary data, and the sensitivity coefficient is higher, and then the sensitivity of the information that the customer can access can be determined according to the customer's role.

[0042] The access permission level is generated for each information based on the second sensitivity coefficient set. The access permission level is usually divided according to the sensitivity coefficient. The information with higher sensitivity has lower access permission for customers, while the information with lower sensitivity can be opened to more customers.

[0043] According to the access permission level of each piece of information, the accessible information items corresponding to each layer of customer user tags are configured. Different information access permissions will be assigned to different customer functional levels, and a mapping relationship between each layer of customer tags and information items will be established.

[0044] Finally, the corresponding second verification channel is constructed according to the second mapping relationship to ensure the authenticity of the customer's identity and verify the customer's access rights according to the customer's functional level. Through the multi-layer verification mechanism, it is ensured that only customers with corresponding permissions can access the specified information items, avoiding the leakage of sensitive data.

[0045] By dividing the functions of customers, identifying the sensitivity coefficients of different customers, generating corresponding access rights levels, and ensuring that customers access information within their authority through mapping relationships and verification channels, the security of corporate customer information is ensured, while also meeting customers' needs for information transparency in projects. Through a hierarchical management approach, customers' access to different sensitive information can be effectively controlled, thereby reducing the risk of data leakage and enhancing customer trust.

[0046] Furthermore, the present application also includes: obtaining historical cooperation projects of the first sharing user; obtaining related cooperation projects corresponding to the historical cooperation projects; calculating project association indicators of the historical cooperation projects and the related cooperation projects; generating a second sensitive weight coefficient based on the project association index; weighting the sensitivity coefficients of various types of information in different projects according to the second sensitive weight coefficient, and outputting an updated second sensitive coefficient set.

[0047] Specifically, historical cooperation projects of the first sharing user are obtained, and all historical cooperation projects that the first sharing user has participated in are identified and listed, including projects that the user has previously completed or is currently in progress, to provide a basis for subsequent analysis.

[0048] Next, identify other projects associated with the historical collaborative project in which the first sharing user participated. The associated projects may overlap with the historical projects in terms of resources, goals, or team members. For example, the historical collaborative project "Project A" may have shared some team members or resources with "Project B", so "Project B" can be considered a project associated with "Project A".

[0049] By analyzing the connection between historical cooperation projects and project correlation indicators, the project correlation index is calculated, which reflects the strength of the relationship between two projects in terms of cooperation, resource sharing, progress synchronization, etc. For example, if "Project A" and "Project B" share a lot of resources and have closely related progress, then the project correlation index between the two may be high, helping to evaluate the similarity and collaboration between the projects.

[0050] Based on the calculated project association index, a sensitive weight coefficient is generated for each project to reflect the impact of the collaborative relationship between projects on the sensitivity of information. For example, if two projects are highly associated, the information related to the two projects may be given a greater weight due to its high sharing and sensitivity, which helps to dynamically adjust the sensitivity of information between projects, thereby providing more secure data access control.

[0051] According to the calculated second sensitivity weight coefficient, the sensitivity coefficient of each type of information in different projects is adjusted. If the sensitivity of a certain project increases due to the increase in correlation, the sensitivity coefficient of the related information will also increase accordingly, and an updated second sensitivity coefficient set will be output, thereby improving the protection of the information.

[0052] By identifying the historical projects and related projects in which the first sharing user participated, calculating the collaborative relationship indicators between projects, and regenerating the sensitivity weight coefficient, the information sensitivity of different projects is dynamically adjusted. The information security can be automatically adjusted according to the relationship between projects to ensure that the collaboration between different projects will not lead to information leakage. The dynamic sensitivity adjustment mechanism can help enterprises reasonably allocate and protect key data in the process of multiple project collaboration, thereby improving overall information security management.

[0053] Furthermore, the present application also includes: receiving a first encryption parameter corresponding to a first party, wherein the first party is a target enterprise; receiving a second encryption parameter corresponding to a second party, wherein the second party is a docking customer of the target enterprise; sending the first encryption parameter and the second encryption parameter to the third-party encryption platform, and obtaining a first authority key and a second authority key according to the third-party encryption platform; the first shared user decrypts and accesses the multi-project collaborative sharing platform with the first authority key or the second authority key according to the access permission level.

[0054] Specifically, a first encryption parameter related to a target enterprise (i.e., a first party) is received. The first encryption parameter is a set of keys or data used to ensure the security of information during transmission and storage. For example, the encryption parameter of the target enterprise may be a specific key used within the enterprise to ensure that only authorized personnel can decrypt and access relevant information during data exchange or information access.

[0055] Next, a second encryption parameter related to the target enterprise's docking customer (i.e., the second party) is received. The second encryption parameter is used to ensure that the customer can exchange data with the target enterprise securely. For example, when the customer shares project data with the target enterprise, the second encryption parameter is used to ensure that the data will not be accessed by unauthorized third parties.

[0056] The first encryption parameter and the second encryption parameter are sent to the third-party encryption platform, and the first authority key and the second authority key are obtained according to the third-party encryption platform. The third-party encryption platform uses an encryption algorithm to generate a key related to the data exchange authority between the target enterprise and the customer for subsequent decryption and authority verification operations.

[0057] The first sharing user uses the first authority key or the second authority key obtained from the third-party encryption platform to decrypt and access the multi-project collaborative sharing platform according to his / her access permission level, thereby ensuring that only authorized data can be accessed.

[0058] Through the coordination of encryption parameters, third-party encryption platforms and permission keys, the security of information of all parties is ensured during the multi-party data exchange process. It can flexibly control the access rights of different users to the multi-project collaborative sharing platform, providing guarantees for secure data sharing between enterprises and customers, while also ensuring the privacy and security of information during the access process.

[0059] Furthermore, the present application also includes: detecting the user access frequency, user access duration and user task change information of the first shared user; obtaining permission update instructions based on the user access frequency, user access duration and user task change information; and dynamically adjusting the access permission level of the first shared user based on the permission update instructions.

[0060] Specifically, by monitoring and collecting the behavioral data of the first sharing user on the multi-project collaborative sharing platform, including the frequency of access, the duration of each access, and the changes in tasks in different time periods. For example, if a user frequently accesses project data and each access lasts for a long time, the information is recorded, and the access pattern is comprehensively evaluated in combination with whether the user has any task changes, so as to fully understand the user's behavioral characteristics for subsequent analysis and permission management.

[0061] According to the user's access frequency, user access duration and user task change information, the permission update instruction is obtained, that is, by analyzing the above monitored user behavior data, a permission update instruction is generated, and then the user's permissions are dynamically adjusted according to the user's actual usage. For example, if the user accesses frequently and for a long time, or if there is a significant change in his task, it may indicate that the user's demand for information has increased, and then an update instruction is issued to allow the user to access more or more sensitive information.

[0062] Finally, according to the permission update instruction, the access permission level of the first shared user is actually adjusted, and the scope and content of data that the user can access can be automatically adjusted according to real-time data and instructions. For example, if a user starts to participate in more complex projects, his access permission can be upgraded to allow him to access more project details, while if the user's tasks are reduced, his access permission may be downgraded to limit his access to other projects.

[0063] By monitoring the access frequency, access duration and task change information of the first shared user, it is possible to obtain important data about user behavior, generate permission update instructions, and dynamically adjust the user's access rights accordingly, thereby ensuring that users can always access the required information in the ever-changing work needs, while avoiding unnecessary excessive opening of permissions and ensuring the data security of the platform.

[0064] In summary, the enterprise project management system for multi-project collaboration provided by the present application has the following technical effects: by obtaining a multi-project collaborative sharing platform, the multi-project collaborative sharing platform includes a dual-channel verification module; when the first shared user accesses the multi-project collaborative sharing platform, the user type of the first shared user is obtained, wherein the user type includes a first type of user and a second type of user, wherein the first type of user is an internal employee of the enterprise, and the second type of user is a customer contact person of the enterprise; when the first shared user belongs to the first type of user, the identity information of the first shared user is verified by the first verification channel of the dual-channel verification module, the access permission level is matched, and partial access to the multi-project collaborative sharing platform is performed according to the access permission level; when the first shared user belongs to the second type of user, the identity information of the first shared user is verified by the second verification channel of the dual-channel verification module, the access permission level is matched, and partial access to the multi-project collaborative sharing platform is performed according to the access permission level. That is to say, by realizing the technical goal of a refined permission management system that dynamically adjusts permissions based on user roles and behaviors, the technical effect of effectively improving data security, reducing the risk of information leakage and improving work efficiency is achieved.

[0065] Embodiment 2: Based on the enterprise project management system for multi-project collaboration in the previous embodiment, the present application also provides an enterprise project management method for multi-project collaboration, as shown in the attached Figure 2, including: obtaining a multi-project collaborative sharing platform, the multi-project collaborative sharing platform including a dual-channel verification module; when a first shared user accesses the multi-project collaborative sharing platform, obtaining a user type of the first shared user, wherein the user type includes a first type of user and a second type of user, wherein the first type of user is an internal employee of the enterprise, and the second type of user is a customer contact person of the enterprise; when the first shared user belongs to the first type of user, performing authority verification on the identity information of the first shared user according to the first verification channel of the dual-channel verification module, matching the access permission level, and partially accessing the multi-project collaborative sharing platform according to the access permission level; when the first shared user belongs to the second type of user, performing authority verification on the identity information of the first shared user according to the second verification channel of the dual-channel verification module, matching the access permission level, and partially accessing the multi-project collaborative sharing platform according to the access permission level.

[0066] Furthermore, the enterprise project management method for multi-project collaboration is also used to: divide enterprise functions for the first user group and obtain multiple layers of enterprise user tags; based on the multiple layers of enterprise user tags, establish sensitivity coefficients for each layer of user tags for various types of information in the project and obtain a first set of sensitivity coefficients; based on the first set of sensitivity coefficients, generate access rights levels for each piece of information; based on the access rights levels for each piece of information, configure accessible information items corresponding to each layer of enterprise user tags and establish a first mapping relationship based on the accessible information items corresponding to each layer of enterprise user tags; and construct the first verification channel according to the first mapping relationship.

[0067] Furthermore, the enterprise project management method for multi-project collaboration is also used to: identify participating projects of the first sharing user; identify project collaboration indicators of the participating projects of the first sharing user and other projects, and output a project collaboration indicator set; generate a first sensitive weight coefficient based on the project collaboration indicator set; adjust the sensitivity coefficients of various types of information in different projects based on the first sensitive weight coefficient, and output an updated first sensitivity coefficient set.

[0068] Furthermore, the enterprise project management method for multi-project collaboration is also used to: divide customer functions for the second user group and obtain multiple layers of customer user tags; based on the multiple layers of customer user tags, establish sensitivity coefficients of each layer of customer user tags for various types of information in the project and obtain a second set of sensitivity coefficients; based on the second set of sensitivity coefficients, generate access permission levels for each piece of information; based on the access permission levels for each piece of information, configure accessible information items corresponding to each layer of customer user tags and establish a second mapping relationship based on the accessible information items corresponding to each layer of customer user tags; and construct the second verification channel according to the second mapping relationship.

[0069] Furthermore, the enterprise project management method for multi-project collaboration is also used to: obtain historical cooperation projects of the first sharing user; obtain related cooperation projects corresponding to the historical cooperation projects; calculate project correlation indicators of the historical cooperation projects and the related cooperation projects; generate a second sensitive weight coefficient based on the project correlation index; adjust the sensitivity coefficients of various types of information in different projects according to the second sensitive weight coefficient, and output an updated second sensitivity coefficient set.

[0070] Furthermore, the enterprise project management method for multi-project collaboration is also used to: receive a first encryption parameter corresponding to a first party, where the first party is a target enterprise; receive a second encryption parameter corresponding to a second party, where the second party is a docking customer of the target enterprise; send the first encryption parameter and the second encryption parameter to the third-party encryption platform, and obtain a first authority key and a second authority key based on the third-party encryption platform; the first shared user decrypts and accesses the multi-project collaborative sharing platform with the first authority key or the second authority key according to the access authority level.

[0071] Furthermore, the enterprise project management method for multi-project collaboration is also used to: detect the user access frequency, user access duration and user task change information of the first shared user; obtain permission update instructions based on the user access frequency, user access duration and user task change information; and dynamically adjust the access permission level of the first shared user based on the permission update instructions.

[0072] The various embodiments in this specification are described in a progressive manner, and each embodiment focuses on the differences from other embodiments. The enterprise project management system for multi-project collaboration and the specific examples in the aforementioned embodiment 1 are also applicable to the enterprise project management method for multi-project collaboration in this embodiment. Through the aforementioned detailed description of the enterprise project management system for multi-project collaboration, those skilled in the art can clearly understand the enterprise project management method for multi-project collaboration in this embodiment, so for the sake of brevity of the specification, it will not be described in detail here.

[0073] The above description of the disclosed embodiments enables those skilled in the art to implement or use the present application. Various modifications to these embodiments will be apparent to those skilled in the art, and the general principles defined herein may be implemented in other embodiments without departing from the spirit or scope of the present application. Therefore, the present application will not be limited to the embodiments shown herein, but will conform to the widest scope consistent with the principles and novel features disclosed herein.

[0074] Obviously, those skilled in the art can make various changes and modifications to the present application without departing from the spirit and scope of the present application. Thus, if these modifications and variations of the present application belong to the scope of the present application and its equivalent technology, the present application is also intended to include these modifications and variations.

Claims

1. An enterprise project management system for multi-project collaboration, characterized by: The system includes: A sharing platform acquisition module, the sharing platform acquisition module is used to acquire a multi-project collaborative sharing platform, the multi-project collaborative sharing platform includes a dual-channel verification module; A user type acquisition module, the user type acquisition module is used to acquire the user type of the first sharing user when the first sharing user accesses the multi-project collaborative sharing platform, wherein the user type includes a first type of user and a second type of user, wherein the first type of user is an internal employee of the enterprise, and the second type of user is a customer contact person of the enterprise; A first-category user access module, the first-category user access module is used to, when the first shared user belongs to the first-category user, perform permission verification on the identity information of the first shared user according to the first verification channel of the dual-channel verification module, match the access permission level, and partially access the multi-project collaborative sharing platform according to the access permission level; The second type of user access module is used to verify the identity information of the first shared user according to the second verification channel of the dual-channel verification module when the first shared user belongs to the second type of user, match the access permission level, and partially access the multi-project collaborative sharing platform according to the access permission level.

2. The enterprise project management system for multi-project collaboration as claimed in claim 1, characterized in that: The method of building the first verification channel includes: Divide the enterprise functions for the first user group and obtain multi-layer enterprise user labels; According to the multi-layer enterprise user tags, establish the sensitivity coefficient of each layer of user tags for various types of information in the project, and obtain a first sensitivity coefficient set; Generating access permission levels for various information according to the first sensitivity coefficient set; According to the access permission level of each piece of information, the accessible information items corresponding to each layer of enterprise user tags are configured, and a first mapping relationship is established according to the accessible information items corresponding to each layer of enterprise user tags; According to the first mapping relationship, the first verification channel is constructed.

3. The enterprise project management system for multi-project collaboration as claimed in claim 2, characterized in that: Obtaining a first sensitivity coefficient set also includes: identifying a participating project of the first sharing user; Identify project collaboration indicators between the project in which the first sharing user participates and other projects, and output a project collaboration indicator set; Generating a first sensitive weight coefficient according to the project coordination indicator set; The sensitivity coefficients of various types of information in different projects are weighted according to the first sensitivity weight coefficients, and an updated first sensitivity coefficient set is output.

4. The enterprise project management system for multi-project collaboration as claimed in claim 2, characterized in that: The method of building the second verification channel includes: Divide customer functions for the second user group and obtain multi-layer customer user tags; According to the multiple layers of customer user tags, a sensitivity coefficient of each layer of customer user tags for various types of information in the project is established to obtain a second sensitivity coefficient set; Generating access permission levels for various information according to the second sensitivity coefficient set; According to the access permission level of each piece of information, the accessible information items corresponding to each layer of customer user tags are configured, and a second mapping relationship is established according to the accessible information items corresponding to each layer of customer user tags; According to the second mapping relationship, the second verification channel is constructed.

5. The enterprise project management system for multi-project collaboration as claimed in claim 4, characterized in that: Obtaining a second sensitivity coefficient set also includes: Acquire historical cooperation projects of the first sharing user; Acquire the associated cooperation project corresponding to the historical cooperation project; Calculating project correlation indicators of the historical cooperation projects and the associated cooperation projects; Generating a second sensitive weight coefficient according to the project association index; The sensitivity coefficients of various types of information in different projects are weighted according to the second sensitivity weight coefficient, and an updated second sensitivity coefficient set is output.

6. The enterprise project management system for multi-project collaboration as claimed in claim 1, characterized in that: The dual-channel verification module includes an encryption module, wherein the encryption module includes a third-party encryption platform, including: Receiving a first encryption parameter corresponding to a first party, wherein the first party is a target enterprise; Receiving a second encryption parameter corresponding to a second party, where the second party is a docking customer of the target enterprise; Sending the first encryption parameter and the second encryption parameter to the third-party encryption platform, and obtaining a first authority key and a second authority key according to the third-party encryption platform; The first sharing user decrypts and accesses the multi-project collaborative sharing platform using the first authority key or the second authority key according to the access authority level.

7. The enterprise project management system for multi-project collaboration according to claim 1, characterized in that: The dual-channel verification module also includes a dynamic authority adjustment mechanism, and the dynamic authority adjustment mechanism includes: Detecting the user access frequency, user access duration, and user task change information of the first sharing user; Obtaining permission update instructions based on the user access frequency, user access duration, and user task change information; The access authority level of the first sharing user is dynamically adjusted according to the authority update instruction.

8. An enterprise project management method for multi-project collaboration, characterized by: The method is implemented by an enterprise project management system for multi-project collaboration according to any one of claims 1 to 7, comprising: Acquire a multi-project collaborative sharing platform, wherein the multi-project collaborative sharing platform includes a dual-channel verification module; When a first sharing user accesses the multi-project collaborative sharing platform, a user type of the first sharing user is obtained, wherein the user type includes a first type of user and a second type of user, wherein the first type of user is an internal employee of the enterprise, and the second type of user is a customer contact person of the enterprise; When the first sharing user belongs to the first category of users, the identity information of the first sharing user is authenticated according to the first authentication channel of the dual-channel authentication module, the access authority level is matched, and partial access to the multi-project collaborative sharing platform is granted according to the access authority level; When the first shared user belongs to the second category of users, the identity information of the first shared user is authenticated according to the second verification channel of the dual-channel verification module, the access permission level is matched, and partial access to the multi-project collaborative sharing platform is performed according to the access permission level.

Images