A permission control method that supports both employee and channel business data

Abstract

The present invention provides a permission control method that supports both employee and channel business data, including the following steps: Step 1: Access the DingTalk API, after the user logs in through DingTalk, obtain the name and user ID of the current user, Step 2: Process the obtained user data through the Java spring framework, judge the user data permission, and output the judgment result, Step 3: Output the ID according to the judgment result, and form an ID set, and give feedback on abnormal data permissions, prompting that the user does not have editing permissions, Step 4: Access the ID set to the interface, after the user logs in, display the user permission information and the data that the user can browse and edit. The present invention isolates the permissions of different personnel by continuously dividing permissions, and processes the permission data set. When used, the data displayed between personnel with different permissions is also different, which reduces the situation where non-authorized personnel receive invalid information to interfere with their work, and improves work results.

Description

Technical Field

[0001] The present invention relates to the technical field of office automation, and in particular to a permission control method that supports both employee and channel business data. Background Art

[0002] With the continuous development of science and technology, traditional office methods are gradually being replaced by more innovative automated offices. Office automation is a new office method that combines modern office and computer technology. By realizing office automation, or digital office, we can optimize the existing management organizational structure, adjust the management system, and increase collaborative office capabilities and strengthen decision-making consistency on the basis of improving efficiency.

[0003] However, as the company continues to expand, the number of people involved in different businesses also increases. It is impossible to isolate data for people in different departments and positions in the company's internal system, nor can it ensure that sensitive data such as orders, finance, and settlements are not leaked. Employees also need to focus only on the data of their own tasks. As the organizational structure becomes clearer, it is also constantly affecting the use of office automation software, and some special personnel may need cross-departmental data. Therefore, data permissions cannot be hard-coded, and need to be flexible enough to support dynamic configuration. In addition, the reuse rate of system components is low, and the cost of later system changes is very high, requiring a certain learning cost. Summary of the invention

[0004] In view of the shortcomings of the prior art, the purpose of the present invention is to provide a permission control method that supports both employee and channel business data to solve the problems raised in the above background technology. The present invention allows different personnel to have corresponding data through permission division, and corresponding permissions can be added at any time, which reduces the configuration difficulty and solves the problems in the prior art.

[0005] In order to achieve the above object, the present invention is implemented through the following technical solution: a method for controlling the authority of both employee and channel business data, comprising the following steps:

[0006] Step 1: Access the DingTalk API. After the user logs in through DingTalk, obtain the user data, including the user name and user ID;

[0007] Step 2: Process the acquired user data through the Java spring framework, judge the user data permissions, and output the judgment results;

[0008] Step 3: Output the ID based on the judgment result and form an ID set. Provide feedback on abnormal data permissions and prompt the user through DingTalk that they do not have editing permissions.

[0009] Step 4: Connect the ID collection to the DingTalk interface. After the user logs in, the user's permission information and the data that the user can browse and edit are displayed to complete the permission allocation.

[0010] As an improvement to the permission control method supporting both employee and channel data described in the present invention, the judgment process in step 2 includes: judging whether the user data permission exists, if the data permission is judged not to exist, not checking the data permission, and prompting the employee, if the data permission exists, then judging whether the permission is super-managed, and if the permission is super-managed, not checking the data permission. The judgment of super-managed permissions can reduce the impact of super-managed permissions on the judgment of subsequent permissions.

[0011] As an improvement to the permission control method supporting both employee and channel business data described in the present invention, the judgment process also includes: when the permission is determined to be super-management, judging whether the user permission is allocated, if the permission has been allocated, identifying the permission type, and outputting the corresponding ID, if the permission has not been allocated, outputting the user ID to form an ID set. Identifying different types of permissions can better isolate the information of people with different permissions and reduce information interference.

[0012] As an improvement to the permission control method supporting both employee and channel business data described in the present invention, the permission type identification process is as follows: first determine whether the permission is a global permission, if it is a global permission, no longer verify the data, if it is not a global permission, enter the subsequent judgment and output the user ID. Identifying global permissions can better allocate permissions and separate large permissions in advance.

[0013] As an improvement to the permission control method supporting both employee and channel business data described in the present invention, the subsequent judgment includes: identifying whether the permission is a channel business permission, if it is a channel business permission, obtaining the associated channel business ID, and outputting the associated channel business user ID data, if it is not a channel business permission, continuing the subsequent judgment. The data of employees in non-organizational structures is identified, the subsequent identification speed is improved, and it is more convenient to contact channel business.

[0014] As an improvement to the permission control method supporting both employee and channel business data described in the present invention, the subsequent judgment also includes: identifying whether the permission is a department permission, if it is a department permission, obtaining the user ID included in the department, and outputting the user ID data associated with the department permission, if it is not a department permission, continuing the subsequent judgment. Distinguishing between ordinary employees and department managers, better data management.

[0015] As an improvement to the permission control method supporting both employee and channel data in the present invention, the subsequent judgment further includes: identifying whether the permission is an employee permission, if it is an employee permission, outputting the user ID data associated with the employee permission, and if it is not an employee permission, obtaining the user ID and outputting the abnormal ID data. The screening of employee permissions and abnormal permissions makes the organizational structure simpler and clearer.

[0016] Compared with the prior art, the present invention has the following beneficial effects:

[0017] 1. The present invention isolates the permissions of different personnel by continuously dividing permissions and processes the permission data set. When used, the data displayed by personnel with different permissions are also different, which reduces the situation where non-authorized personnel receive invalid information and interfere with their work, thereby improving work efficiency;

[0018] 2. The present invention adds super-management authority with most of the authority, does not limit its authority, and can modify the authority of personnel with lower authority, which is convenient for subsequent authority modification, improves the convenience of use, and can also reduce the difficulty of configuration during use;

[0019] 3. After the present invention is connected to the API of DingTalk, it can realize system login by scanning the DingTalk code, without the need for secondary development, thereby improving the adaptation scope. While doing a good job of data isolation, it also allows cross-departmental processing personnel to better obtain information and improve the use effect. BRIEF DESCRIPTION OF THE DRAWINGS

[0020] In order to more clearly illustrate the specific implementation of the present invention or the technical solution in the prior art, the drawings required for describing the specific implementation or the prior art will be briefly introduced below. Obviously, the drawings described below are only one implementation of the present invention. For ordinary technicians in this field, other drawings can be obtained based on these drawings without paying creative work.

[0021] Figure 1 It is a schematic diagram of the work flow structure of the present invention;

[0022] Figure 2 This is a schematic diagram of the permission configuration structure of the present invention;

[0023] Figure 3 It is a schematic diagram of the data output structure of the present invention. DETAILED DESCRIPTION

[0024] In order to make the technical means, creative features, objectives and effects achieved by the present invention easy to understand, the technical scheme in the specific implementation mode of the present invention is clearly and completely described below to further illustrate the present invention. Obviously, the specific implementation mode described is only a part of the implementation mode of the present invention, rather than all styles.

[0025] This specific implementation method is a permission control method that supports both employee and channel data. The workflow structure diagram is as follows: Figure 1 As shown, the schematic diagram of the permission configuration structure is as follows Figure 2 As shown, the data output structure diagram is as follows Figure 3 As shown, the permission control method that supports both employee and channel business data includes the following steps:

[0026] Step 1: Access the DingTalk API. After the user logs in through DingTalk, obtain the user data, including the user name and user ID;

[0027] Step 2: Process the acquired user data through the Java spring framework, judge the user data permissions, and output the judgment results;

[0028] Step 3: Output the ID based on the judgment result and form an ID set. Provide feedback on abnormal data permissions and prompt the user through DingTalk that they do not have editing permissions.

[0029] Step 4: Connect the ID collection to the DingTalk interface. After the user logs in, the user's permission information and the data that the user can browse and edit are displayed to complete the permission allocation.

[0030] When using this technical solution, the DingTalk API is accessed. After the user logs in through DingTalk, the name and user ID of the current user are obtained, and the obtained user data is processed through the Java spring framework. The user data authority is judged, and whether the user data authority exists is judged. If the data authority is judged not to exist, the data authority is not checked, and the employee is prompted. If the data authority exists, then judge whether the authority is super-managed, and when the authority is super-managed, the data authority is not checked. When the authority is judged to be super-managed, it is judged whether the user authority is allocated. If the authority has been allocated, the corresponding ID is output after identifying the type of authority. If the authority is not allocated, the user ID is output to form an ID set. First, it is judged whether the authority is a global authority. If it is a global authority, the data is no longer checked. If it is not a global authority, it enters the subsequent judgment and outputs the user ID. It is identified whether the authority is a channel merchant authority. If it is a channel merchant authority, the associated channel is obtained. If it is not the channel merchant authority, then continue to make subsequent judgments to identify whether the authority is department authority. If it is department authority, obtain the user IDs included in the department, and output the user ID data associated with the department authority. If it is not department authority, then continue to make subsequent judgments to identify whether the authority is employee authority. If it is employee authority, output the user ID data associated with employee authority. If it is not employee authority, obtain the user ID, output the abnormal ID data, and output the judgment result. According to the judgment result, output the ID, form an ID set, and feedback the abnormal data authority, prompting that the user does not have editing authority, connect the ID set to the interface, and display the user authority information and the data that the user can browse and edit after logging in.

[0031] The above describes the main technical features and basic principles of the present invention and the related advantages. It is obvious to those skilled in the art that the present invention is not limited to the details of the above exemplary embodiments, and the present invention can be implemented in other specific forms without departing from the concept or basic features of the present invention. Therefore, no matter from which point of view, the above specific embodiments should be regarded as exemplary and non-restrictive. The scope of the present invention is defined by the attached claims rather than the above description, and it is intended that all changes falling within the meaning and scope of the equivalent elements of the claims are included in the present invention.

Claims

1. A permission control method that supports both employee and channel data, characterized in that: The steps include: Step 1: Access the DingTalk API. After the user logs in through DingTalk, obtain the user data, including the user name and user ID; Step 2: Process the acquired user data through the Java spring framework, judge the user data permissions, and output the judgment results; The judgment process in step 2 includes: judging whether the user data permission exists, if the data permission is judged not to exist, not checking the data permission, and prompting the employee, if the data permission exists, then judging whether the permission is super-managed, and if the permission is super-managed, not checking the data permission; The judgment process further includes: when it is judged that the authority is super management, judging whether the user authority is allocated, if the authority is allocated, identifying the authority type, and outputting the corresponding ID, if the authority is not allocated, outputting the user ID to form an ID set; The process of identifying the permission type is as follows: first determine whether the permission is a global permission, if it is a global permission, then no further verification is performed on the data, if it is not a global permission, then proceed to subsequent judgment and output the user ID; The subsequent judgment includes: identifying whether the permission is a channel business permission, if it is a channel business permission, obtaining the associated channel business ID, and outputting the user ID data of the associated channel business, if it is not a channel business permission, continuing the subsequent judgment; The subsequent judgment further includes: identifying whether the authority is a department authority, if it is a department authority, obtaining the user ID included in the department, and outputting the user ID data associated with the department authority, if it is not a department authority, continuing the subsequent judgment; The subsequent judgment further includes: identifying whether the permission is an employee permission, if it is an employee permission, outputting the user ID data associated with the employee permission, and if it is not an employee permission, obtaining the user ID and outputting the abnormal ID data; Step 3: Output the ID based on the judgment result and form an ID set. Provide feedback on abnormal data permissions and prompt the user through DingTalk that they do not have editing permissions. Step 4: Connect the ID collection to the DingTalk interface. After the user logs in, the user's permission information and the data that the user can browse and edit are displayed to complete the permission allocation.

Images