Method for displaying authority after employee in system logs in account thereof

Abstract

The invention discloses a method for displaying the authority after an employee in a system logs in an account thereof. The method comprises the steps that a created and non-frozen account which is not associated with employees is selected for an employee as the account of the employee, or an account is separately created for the employee; the employee logs in the system according to the corresponding account; and the system displays first information or second information to the employee, wherein the first information comprises all roles associated with the account and authorities corresponding to the roles, and the second information comprises main roles of all the roles associated with the account and the authorities corresponding to the main roles. According to the method, after the employee logs in the account thereof, the corresponding authorities are clearly displayed according to the roles associated with the account so that the employee can conveniently carry out work; and inaddition, each employee corresponds to one account, and each account corresponds to one employee so that the operation of each account can be conveniently traced, and corresponding persons in charge can be checked.

Description

technical field [0001] The invention relates to a method for displaying user rights of management software systems such as ERP, in particular to a method for displaying rights of employees in the system after they log in to their accounts. Background technique [0002] Role-based access control (RBAC) is the most researched and thoughtful database permission management mechanism in recent years. It is considered to be an ideal candidate to replace traditional mandatory access control (MAC) and discretionary access control (DAC). The basic idea of ​​role-based access control (RBAC) is to divide different roles according to different functional positions in the enterprise organization view, encapsulate the access rights of database resources in roles, and users can indirectly access database resources by being assigned different roles. [0003] There are often a large number of tables and views in large-scale application systems, which makes the management and authorization of...

AI Technical Summary

Problems solved by technology

[0005] However, the traditional role-based user rights management methods all adopt the "role-to-user one-to-many" association mechanism. / Position / Type of work and other concepts, the authorization of user rights under this association mechanism is basically divided into the following three forms: 1. figure 1 As shown, directly authorizing users has the disadvantages of heavy workload, frequent and cumbersome operations; 2. figure 2 As shown, authorize the role (category / group / position / type of work) (a role can be associated with multiple users), and the user obtains the authority through the role; 3. For example image 3 As shown, the combination of the above two methods

[0006] In the above statement, both 2 and 3 need to authorize the role of class / group nature, but the way of authorization through the role of class / group / post / work type has the following disadvantages: 1. The operation is difficult when the user authority changes: In the actual system use, it is often necessary to adjust the user's permissions during the operation process. For example, when dealing with changes in employee permissions, the permissions of an employee associated with a role change. We cannot Changes to change the permissions of the entire role, because the role is also associated with other employees whose permissions have not changed

The above two processing methods not only take a long time to authorize the role in the case of many role permissions, but also are prone to mistakes. The operation of the user is cumbersome and troublesome, and it is also easy to make mistakes and cause losses to the system user.

[0007] 2. It is difficult to remember the specific permissions contained in the role for a long time: If the role has many permission function points, it is difficult to remember the specific permissions of the role over time, and it is even more difficult to remember the permission differences between roles with similar permissions. To associate a new user, it is impossible to accurately determine how to choose the association

[0008] 3. Due to the change of user permissions, more and more roles will be created (if no new roles are created, the direct authorization to users will be greatly increased), and it is more difficult to distinguish the specific differences between the permissions of each role

[0009] 4. When transferring a post, if you want to assign many permissions of the transferred user to several other users, you must distinguish these permissions of the transferred user during processing, and then create roles to associate with the other users. users, such an operation is not only complicated and time-consuming, but also prone to errors

[0010] In the existing ERP and other management systems, employees cannot clearly understand the authority of each position / station number after logging into their accounts, which is not conducive to the development of work

In addition, in the existing ERP and other management systems, there are situations where multiple employees use the same user (account) to operate at work. At this time, the system cannot simply and clearly analyze the operation behavior or traces of the employees when performing analysis, resulting in Tracing work to its source becomes complicated

Images