Authority management control method and device, equipment and storage medium

Abstract

The invention relates to an authority management control method and device, equipment and a storage medium, and the method comprises the steps: obtaining business information, and setting at least one flow node according to the business information; acquiring identity information of the user, and determining responsibility of the user in each process node according to the identity information of the user; a form is obtained, the form comprises a plurality of labels, and each label is provided with different label contents; according to the label content and the responsibility of the user in each process node, based on a permission rule, allocating permissions of one or more labels in an operable form to the user; and determining agreement / rejection of the operation request of the current user according to the permission. According to the method, the complexity of service and process configuration is effectively reduced through a method for flexibly configuring the labels, the posts, the roles and the groups, a mode of fusing the service and the process and a permission configuration mechanism of different process nodes of the form, so that a user can more conveniently carry out related operations, and the actual requirements of the user are met.

Description

Technical Field

[0001] The present application relates to the technical field of rights management, and in particular to a rights management control method, apparatus, device and storage medium. Background Art

[0002] In the current technical field, permission identification and control are crucial links. Traditional permission management methods often have many limitations. In many systems, the configuration of business and processes is often complex and lacks flexibility. When it is necessary to configure related businesses according to specific process processing nodes, existing technical means are often difficult to meet actual needs; for example, the permission configuration in some systems is relatively fixed and cannot be adjusted in time according to the dynamic changes of the business. This leads to problems such as inconvenient operation and low efficiency in actual applications. At the same time, the existing permission management method is also insufficient in terms of integration with the business and cannot adapt well to various complex business scenarios. This situation not only limits the scope of application of the system, but also affects the user experience, seriously affecting the overall performance of the system and user satisfaction.

[0003] In this context, there is an urgent need to provide a rights management control method, device, equipment and storage medium to solve the technical problems raised above. Summary of the invention

[0004] Based on this, the present application provides a permission management control method, apparatus, device and storage medium, which assigns users permissions to operate one or more labels in the form according to several labels in the form and the user's responsibilities in each process node, and based on permission rules. Then, by utilizing permission rules to flexibly configure labels and the user's responsibilities in each process node, it can better adapt to various complex business scenarios, better meet the user's actual needs, and enhance the user's usage experience.

[0005] In a first aspect, a rights management control method is provided, the method comprising:

[0006] Acquire business information, and set a process node according to the business information, wherein the process node has at least one;

[0007] Obtaining the identity information of the user, and determining the responsibilities of the user in each of the process nodes according to the identity information of the user;

[0008] Obtain a form, wherein the form includes a plurality of tags, and each of the tags is set with different tag content;

[0009] According to the content of the label and the responsibilities of the user in each process node, and based on the permission rules, the user is assigned the permission to operate one or more labels in the form;

[0010] Determine whether to approve or deny the current user's operation request based on the permissions.

[0011] Preferably, the obtaining of the user's identity information and determining the user's responsibilities in each of the process nodes according to the user's identity information includes:

[0012] Get the user's position information, role information, and group information;

[0013] The user's responsibilities in each of the process nodes are determined based on the acquired position information, role information, and group information.

[0014] Preferably, the permission rules include one or more of visibility rules, fillability rules, and system enumeration data access rules;

[0015] The visibility rule is a rule that determines whether a user can see the content of a specific form;

[0016] The fillability rule is a rule that specifies whether a user can fill in or modify data in a form;

[0017] The system enumeration data acquisition rule is a rule for determining whether a user can obtain system enumeration data for form filling.

[0018] Preferably, the permissions include permissions for controlling the filling, modification, visibility and invisibility of the tag content in the tag.

[0019] Preferably, the determining of approving / rejecting the operation request of the current user according to the authority includes:

[0020] Determining whether the current user has permission to operate one or more tags in the form according to the current process node and the permission;

[0021] If it is determined that the current user has the corresponding authority, the current user is allowed to perform the operation;

[0022] Otherwise, the current user's operation request is rejected.

[0023] Preferably, before determining whether the current user has the authority to operate one or more tags in the form according to the current process node and the authority, the method further includes:

[0024] Verify the identity information of the current user;

[0025] If the verification is passed, the permission to operate one or more tags in the form in each process node is allocated according to the identity information of the current user.

[0026] Preferably, the verifying the identity information of the current user includes:

[0027] Collect the current user's face image and obtain the current user's work number information;

[0028] Comparing the collected facial image and work number information with the pre-collected identity information;

[0029] If the comparison is successful, it means that the current user has passed the verification.

[0030] In a second aspect, the present application further provides a rights management control device, the device comprising:

[0031] A first acquisition module, which is used to acquire business information and set a process node according to the business information, wherein the process node has at least one;

[0032] A second acquisition module, which is used to acquire the identity information of the user and determine the user's responsibilities in each of the process nodes according to the identity information of the user;

[0033] A third acquisition module is used to acquire form information, wherein the form information includes a plurality of tags, and each of the tags is provided with different tag content;

[0034] An allocation module, which is used to allocate permissions for users to operate one or more labels in the form according to the label content and the user's responsibilities in each process node and based on permission rules;

[0035] A processing module is used to determine whether to approve or reject the operation request of the current user according to the authority.

[0036] In a third aspect, a computer device is provided, comprising:

[0037] at least one processor; and

[0038] a memory communicatively connected to at least one processor; wherein,

[0039] The memory stores computer instructions that can be executed by at least one processor, and the computer instructions are executed by at least one processor to enable the at least one processor to execute the method involved in the first aspect above.

[0040] In a fourth aspect, a computer-readable storage medium is provided, on which computer instructions are stored, characterized in that the computer instructions are used to enable a computer to execute the method involved in the above-mentioned first aspect.

[0041] According to the specific embodiments provided in this application, the technical solution provided in this application can have the following advantages:

[0042] In this application, the business and process are deeply integrated by using tags and positions, groups and roles for flexible configuration; specifically, a combination strategy of business block permissions and multiple methods such as positions, groups and roles is adopted, so that different business forms can be configured with different permissions at different process nodes. This improvement method not only greatly improves the flexibility of permission configuration, but also can better adapt to various complex business scenarios. In practical applications, it can effectively reduce the complexity of business and process configuration, so that users can perform related operations more conveniently; at the same time, through precise permission control and flexible configuration, the security and reliability of the system are improved. In addition, by closely integrating business and processes, it can better meet the actual needs of users and enhance the user experience; this improvement is a major breakthrough in the existing technology, and brings new ideas and methods to the field of permission identification and control. It not only solves the current problems, but also provides strong support for future technological development. BRIEF DESCRIPTION OF THE DRAWINGS

[0043] Figure 1 A hardware system architecture diagram of a rights management control method in an embodiment;

[0044] Figure 2 A flowchart of a rights management control method in one embodiment;

[0045] Figure 3 A flowchart of a rights management control method in one embodiment;

[0046] Figure 4 It is a structural block diagram of a rights management control device in one embodiment;

[0047] Figure 5 FIG. 4 is a schematic structural diagram of a computer device in one embodiment. DETAILED DESCRIPTION

[0048] The present application is further described in detail below in conjunction with the accompanying drawings and embodiments. It should be understood that the specific embodiments described herein are only used to explain the present application and are not used to limit the present application.

[0049] For ease of understanding, the system to which this application is applicable is first described. This application provides a rights management control method that can be applied to Figure 1The system architecture shown in FIG. 1 includes: a user space file server 103 and a terminal device 101, wherein the terminal device 101 communicates with the user space file server 103 through a network. The user space file server 103 may be a file server based on the NFSv3\v4 protocol, running in a Linux environment, and NFS (Network File System) is a network abstraction on the file system, which allows a remote client running on the terminal device 101 to access through the network in a manner similar to a local file system. The terminal device 101 may be, but is not limited to, various personal computers, laptops, smart phones, tablet computers, etc., and the user space file server 103 may be implemented with an independent server or a server cluster consisting of multiple servers.

[0050] Figure 2 A flowchart of a permission management control method provided in an embodiment of the present application, the method can be performed as follows Figure 1 The method may include the following steps:

[0051] Step 201: Obtain business information, and set a process node according to the business information, wherein there is at least one process node;

[0052] Step 202: Obtain the user's identity information, and determine the user's responsibilities in each of the process nodes according to the user's identity information;

[0053] Step 203: Obtain a form, wherein the form includes a plurality of tags, and each of the tags is provided with different tag contents;

[0054] Step 204: assigning permissions for operating one or more labels in the form to the user based on the label content and the user's responsibilities in each process node and based on permission rules;

[0055] Step 205: Determine whether to approve / reject the operation request of the current user according to the authority.

[0056] In this application, the business process nodes and form labels are deeply integrated. Specifically, according to the user's responsibilities in each process node and the labels set in the form, the user is assigned the permission to operate one or more labels in the form through permission rules, and then different process nodes are linked to one or more labels of the form through permission control, so that different process nodes can be configured with different permissions. This improved method not only greatly improves the flexibility of permission configuration, but also can better adapt to various complex business scenarios; in actual applications, it can also effectively reduce the complexity of business and process configuration, so that users can perform related operations more conveniently. At the same time, through precise permission control and flexible configuration, the security and reliability of the system are improved; in addition, by closely integrating business and process, it can better meet the actual needs of users and enhance the user experience.

[0057] Each step is described in detail below:

[0058] Please refer to Figure 2 , Figure 3 As shown, step 201, obtain business information, set a process node according to the business information, and the process node has at least one;

[0059] In this embodiment, it should be noted that a complete process engine system is first established, on the basis of which business information can be set according to actual needs. The business information can include procurement business, reimbursement business, contract approval business, etc., and process nodes are set according to different business information. The process nodes have at least one or more process nodes such as application, review, approval, and filing. For example, for the procurement business, four process nodes are set including procurement application, procurement review, procurement approval, and procurement filing. In this embodiment, each process node is operated by a corresponding user.

[0060] Step 202, obtaining the identity information of the user, and determining the responsibilities of the user in each of the process nodes according to the identity information of the user;

[0061] In this embodiment, it should be noted that the user's identity information is obtained, where the identity information can be position information, role information and group information; then the user's responsibilities in each process node are determined based on the obtained position information, role information and group information; where the group information is that the same position is divided into multiple groups according to different division of labor, and each group has special responsibilities.

[0062] Step 203, obtaining a form, wherein the form includes a plurality of tags, and each of the tags is provided with different tag contents;

[0063] In this embodiment, it should be noted that different forms are set according to different business information. In other words, each business has a corresponding form, and each form contains several tags, and each tag is set with different tag content. For example, for the purchase application business, the form contains a purchase plan tag, a supplier information query tag, a purchase plan approval tag, a purchase confirmation tag, etc. For the purchase plan tag, the content of the tag mainly displays information such as department, purchase time, etc.; for the supplier information query tag, the content of the tag mainly displays information such as supplier name, etc.; for the purchase plan approval tag, the content of the tag mainly displays information such as purchase plan, purchaser, and purchase cost, etc.

[0064] Step 204, assigning permissions to the user to operate one or more labels in the form according to the label content and the user's responsibilities in each process node and based on permission rules;

[0065] In this embodiment, it should be noted that after the process nodes of the business information and the label contents of the form have been confirmed, the user is then assigned the permission to operate one or more labels in the form based on the permission rules, in combination with the user's responsibilities in each process node and the label contents represented by each label in the form. Among them, the number of labels can be increased or decreased according to the specific business information; the permission includes the permission to control the filling, modification, visibility and invisibility of the label contents in several labels; the permission rules include one or more of the visibility rules, the fillability rules and the system enumeration data access rules; the visibility rules are the rules that determine whether the user can see the content of a specific form, for example, the sensitive information form may only be visible to users of specific positions or roles; the fillability rules are the rules that specify whether the user can fill in or modify the data in the form, for example, the application form may only be filled in by the applicant, and the approver can only view and approve, but cannot modify the application content; the system enumeration data access rules are the rules that determine whether the user can obtain the system enumeration data for form filling, for example, when selecting the supplier type, only users of specific positions can select from the system enumerated supplier categories.

[0066] Please refer to Figure 3As shown, for a better understanding, the following example is given. For procurement business, there are different process nodes. Each process node contains multiple positions and roles such as procurement specialists, procurement managers, and leaders in charge to perform operations. Each position and role is given different permissions according to its responsibilities and needs, and each permission can operate one or more labels in the form. For example, as the initiator of the process node, the procurement specialist is mainly responsible for specific procurement operations and has permission 1 to initiate the procurement application process, fill in the procurement plan, and conduct preliminary communication with suppliers. This permission 1 can operate labels 1, 2, and 3 in the form. For labels 1 and 2, the procurement specialist has the permission to fill in, while for label 3, the procurement specialist only has visible permissions and cannot fill in or modify. The purchasing manager in the position has permission 2 to view, modify and fill in the approval opinions of the purchasing plan. This permission 2 can operate the labels 1, 2, 3 and 4 in the form. For label 1, the purchasing manager only has the permission to see it. For label 2, the purchasing manager has the permission to modify it. For label 3, the purchasing manager has the permission to fill in it. For label 4, the purchasing manager only has the permission to see it. The leader in charge in the role has permission 3 to view the purchasing plan, the approval opinions of the purchasing plan and fill in the confirmation of the purchasing results. This permission 3 can operate the labels 1, 2, 3, 4 and 5 in the form. For label 1, the leader in charge has only the permission to see it. For label 2, the leader in charge has only the permission to see it. For label 3, the leader in charge has the permission to modify it. For label 4, the leader in charge has the permission to fill in it. For label 5, the leader in charge has the permission to fill in it. In addition, for some positions, due to different responsibilities, grouping may occur, that is, the roles are divided into several groups. Each group is given different permissions according to its responsibilities and needs, so as to further refine the control of permissions. Different process nodes will be triggered to run according to different conditions at runtime. For example, the procurement role is divided into the equipment procurement group and the office supplies procurement group according to the attributes of the purchased materials. The equipment procurement group has special permissions for large-scale equipment procurement, while the office supplies procurement group focuses on the procurement permissions of daily office supplies. The group can share a permission 4, but the shared permission 4 can be used to control the filling, modification, visibility and invisibility of the label content in label 3, label 4 and label 5 in the form according to the different responsibilities of the equipment procurement group and the office supplies procurement group. Then, through the differentiated configuration of the above permissions, the compliance and quality of the procurement process can be ensured.

[0067] For another example, the financial business includes multiple roles such as financial specialist, financial manager, and responsible leader. Each role is given different permissions according to its responsibilities and needs. For example, the financial specialist has the permission to initiate the expense application process; the financial manager has the permission to review and approve expense reimbursements, etc. This embodiment will not be elaborated in detail.

[0068] Therefore, in this embodiment, corresponding permission rules are set according to different process nodes. When the form is running at different process nodes, permissions for multiple labels in the operable form are allocated according to the different responsibilities of the user's position, role, and group. Thus, by combining labels with factors such as positions, groups, and roles, the flexibility of permission configuration can be improved, and it can also better adapt to various complex business scenarios. Compared with the prior art, when increasing the number of labels in a form, each process node needs to modify the permissions of the labels separately. In this application, permissions are used to link multiple labels with the user's position, role, and group. Even when increasing the number of labels, only the permission rules need to be modified, which can achieve flexible configuration.

[0069] Step 205: Determine whether to approve or reject the operation request of the current user according to the authority.

[0070] In this embodiment, it should be noted that in the actual operation process, the user logs in to the process engine system, and the identity information of the current user is verified during the login process; if the verification is passed, the permission of one or more labels in the operable form in each process node is allocated according to the identity information of the current user, and then when the process node runs to the current user, the corresponding operation can be performed; otherwise, the operation request of the current user is rejected.

[0071] In one feasible method, a facial image of the current user is collected, and the work number information of the current user is obtained; the collected facial image and work number information are compared with the pre-collected identity information; if the comparison is successful, it means that the current user has passed the verification; wherein the pre-collected identity information is user information related to each position, group and role, including facial images, work number information, identity card number, etc., which are entered into the system.

[0072] In this embodiment, it should also be noted that the system can also be configured with a management interface, through which the permission rules of the form can be conveniently modified and adjusted to adapt to different business needs. It can be understood that different businesses have different process nodes, and the corresponding positions, groups and roles will also be different. Therefore, it is necessary to increase or modify the number or content of labels in the form according to different businesses, and dynamically modify and adjust one or more labels in the user-operable form according to the permission rules, so that different positions, different groups and roles can be configured with permissions to operate corresponding labels in each process node of different businesses, thereby realizing differentiated configuration of permissions.

[0073] The working principle of this embodiment is as follows: after the user logs in to the system, the system will automatically obtain the corresponding permissions according to the user's position, group, role and other information. When the user performs specific business operations, the system will determine whether the user has the permission to operate one or more labels in the form according to the permission rules of the current process node and form. If the user has the corresponding permission, he will be allowed to operate; otherwise, the user's operation request will be rejected. This application greatly improves the ease of use and operability of the system by solving the problem of complex business and process configuration, allowing users to work more efficiently; secondly, it realizes the function of configuring related businesses according to process nodes, so that the system can better adapt to different business scenarios and improve the adaptability and flexibility of the system; furthermore, by flexibly configuring the form business permissions, the role of the form is fully utilized, and the efficiency and quality of business processing are improved; in addition, this permission identification and control method enhances the security and reliability of the system, protects the data and information security of users, and at the same time, provides strong support for the management and operation of enterprises, which helps to improve the competitiveness and benefits of enterprises.

[0074] It should be understood that although Figure 2 The steps in the embodiment are shown in sequence according to the arrows, but these steps are not necessarily performed in the order indicated by the arrows. Unless otherwise specified in the present application, there is no strict order restriction for the execution of these steps, and these steps can be performed in other orders.

[0075] Figure 4 A schematic diagram of a rights management control device provided in an embodiment of the present application, which can be arranged at Figure 1 In the hardware system shown in FIG. Figure 2 The method flow shown in Figure 4 As shown, the device may include: a first acquisition module 301, a second acquisition module 302, a third acquisition module 303, an allocation module 304 and a processing module 305. The main functions of each component module are as follows:

[0076] A first acquisition module 301, which is used to acquire business information and set a process node according to the business information, wherein the process node has at least one;

[0077] A second acquisition module 302, which is used to acquire the identity information of the user, and determine the user's responsibilities in each of the process nodes according to the identity information of the user;

[0078] The third acquisition module 303 is used to acquire form information, wherein the form information includes a plurality of tags, and each of the tags is provided with different tag content;

[0079] An allocation module 304, which is used to allocate permissions for operating one or more labels in the form to the user according to the label content and the user's responsibilities in each process node and based on permission rules;

[0080] The processing module 305 is used to determine whether to approve or reject the operation request of the current user according to the authority.

[0081] The same or similar parts between the above embodiments can be referred to each other, and each embodiment focuses on the differences from other embodiments. In particular, for the device embodiment, since it is basically similar to the method embodiment, the description is relatively simple, and the relevant parts can be referred to the partial description of the method embodiment.

[0082] It should be noted that the embodiments of the present application may involve the use of user data. In actual applications, user-specific personal data can be used in the scheme described in this article within the scope permitted by applicable laws and regulations, provided that the applicable laws and regulations of the country are met (for example, the user's explicit consent, effective notification to the user, and the user's explicit authorization, etc.).

[0083] According to an embodiment of the present application, the present application also provides a computer device and a computer-readable storage medium.

[0084] like Figure 5 , is a block diagram of a computer device according to an embodiment of the present application. The computer device is intended to represent various forms of digital computers or mobile devices. The digital computer may include a desktop computer, a portable computer, a workbench, a personal digital assistant, a server, a mainframe computer, and other suitable computers. The mobile device may include a tablet computer, a smart phone, a wearable device, etc.

[0085] like Figure 5As shown, the device 500 includes a computing unit 501, a ROM 502, a RAM 503, a bus 504, and an input / output (I / O) interface 505, and the computing unit 501, ROM 502 and RAM 503 are connected to each other through the bus 504. The input / output (I / O) interface 505 is also connected to the bus 504.

[0086] The computing unit 501 can perform various processes in the method embodiment of the present application according to the computer instructions stored in the read-only memory (ROM) 502 or the computer instructions loaded from the storage unit 508 to the random access memory (RAM) 503. The computing unit 501 can be various general and / or special processing components with processing and computing capabilities. The computing unit 501 may include, but is not limited to, a central processing unit (CPU), a graphics processing unit (GPU), various dedicated artificial intelligence (AI) computing chips, various computing units running machine learning model algorithms, digital signal processors (DSPs), and any appropriate processors, controllers, microcontrollers, etc. In some embodiments, the method provided in the embodiment of the present application can be implemented as a computer software program, which is tangibly contained in a computer-readable storage medium, such as a storage unit 508.

[0087] RAM 503 may also store various programs and data required for the operation of device 500. Part or all of the computer program may be loaded and / or installed on device 500 via ROM 502 and / or communication unit 509.

[0088] The input unit 506, output unit 507, storage unit 508 and communication unit 509 in the device 500 can be connected to the I / O interface 505. The input unit 506 can be, for example, a keyboard, a mouse, a touch screen, a microphone, etc. The output unit 507 can be, for example, a display, a speaker, an indicator light, etc. The device 500 can exchange information, data, etc. with other devices through the communication unit 509.

[0089] It should be noted that the device may also include other components necessary for normal operation, or may only include components necessary for implementing the solution of the present application, rather than all the components shown in the figure.

[0090] Various implementations of the systems and techniques described herein can be realized in digital electronic circuit systems, integrated circuit systems, field programmable gate arrays (FPGAs), application specific integrated circuits (ASICs), application specific standard products (ASSPs), system on a chip (SOCs), load programmable logic devices (CPLDs), computer hardware, firmware, software, and / or combinations thereof.

[0091] The computer instructions for implementing the method of the present application can be written in any combination of one or more programming languages. These computer instructions can be provided to the computing unit Y01, so that when the computer instructions are executed by the computing unit Y01 such as a processor, the steps involved in the method embodiment of the present application are executed.

[0092] The computer-readable storage medium provided in the present application may be a tangible medium that may contain or store computer instructions for executing the steps involved in the method embodiments of the present application. The computer-readable storage medium may include, but is not limited to, electronic, magnetic, optical, electromagnetic, and other forms of storage media.

[0093] The above specific implementations do not constitute a limitation on the protection scope of this application. It should be understood by those skilled in the art that various modifications, combinations, sub-combinations and substitutions can be made according to design requirements and other factors. Any modifications, equivalent substitutions and improvements made within the spirit and principles of this application should be included in the protection scope of this application.

Claims

1. A rights management control method, characterized in that: The method comprises: Acquire business information, and set a process node according to the business information, wherein the process node has at least one; Obtaining the identity information of the user, and determining the responsibilities of the user in each of the process nodes according to the identity information of the user; Obtain a form, wherein the form includes a plurality of tags, and each of the tags is set with different tag content; According to the content of the label and the responsibilities of the user in each process node, and based on the permission rules, the user is assigned the permission to operate one or more labels in the form; Determine whether to approve or deny the current user's operation request based on the permissions.

2. The rights management control method according to claim 1, characterized in that: The obtaining of the user's identity information and determining the user's responsibilities in each of the process nodes according to the user's identity information includes: Get the user's position information, role information, and group information; The user's responsibilities in each of the process nodes are determined based on the acquired position information, role information, and group information.

3. The rights management control method according to claim 1, characterized in that: The permission rules include one or more of visibility rules, fillability rules, and system enumeration data access rules; The visibility rule is a rule that determines whether a user can see the content of a specific form; The fillability rule is a rule that specifies whether a user can fill in or modify data in a form; The system enumeration data acquisition rule is a rule for determining whether a user can obtain system enumeration data for form filling.

4. The rights management control method according to claim 1, characterized in that: The permissions include permissions to control the filling, modification, visibility and invisibility of the tag content in the tag.

5. The rights management control method according to claim 1, characterized in that: The determining of approving / rejecting the operation request of the current user according to the authority includes: Determining whether the current user has permission to operate one or more tags in the form according to the current process node and the permission; If it is determined that the current user has the corresponding authority, the current user is allowed to perform the operation; Otherwise, the current user's operation request is rejected.

6. The method for controlling rights management according to claim 5, characterized in that: Before determining whether the current user has the authority to operate one or more tags in the form according to the current process node and the authority, the method further includes: Verify the identity information of the current user; If the verification is passed, the permission to operate one or more tags in the form in each process node is allocated according to the identity information of the current user.

7. The method for controlling rights management according to claim 6, characterized in that: The verifying of the identity information of the current user includes: Collect the current user's face image and obtain the current user's work number information; Comparing the collected facial image and work number information with the pre-collected identity information; If the comparison is successful, it means that the current user has passed the verification.

8. A rights management control device, characterized in that: The device includes: A first acquisition module, which is used to acquire business information and set a process node according to the business information, wherein the process node has at least one; A second acquisition module, which is used to acquire the identity information of the user and determine the user's responsibilities in each of the process nodes according to the identity information of the user; A third acquisition module is used to acquire form information, wherein the form information includes a plurality of tags, and each of the tags is provided with different tag content; An allocation module, which is used to allocate permissions for users to operate one or more labels in the form according to the label content and the user's responsibilities in each process node and based on permission rules; A processing module is used to determine whether to approve or reject the operation request of the current user according to the authority.

9. A computer device comprising: at least one processor; as well as a memory communicatively connected to the at least one processor; wherein, The memory stores computer instructions that can be executed by the at least one processor, and the computer instructions are executed by the at least one processor to enable the at least one processor to perform the method according to any one of claims 1 to 7.

10. A computer-readable storage medium having computer instructions stored thereon, characterized in that: The computer instructions are used to cause a computer to execute the method according to any one of claims 1 to 7.

Images