Method for managing instant messaging account in management system

Abstract

The present invention discloses a method for managing an instant messaging account in a management system. The method includes: creating a system role which is an independent individual; and according to a work content of a role in the management system, and associating the role with a role property instant messaging account, wherein the role property instant messaging account can only be associated with one role, and a role can only be associated with one role property instant messaging account during a period; and establishing the association between the user and the role, and taking the role property instant messaging account associated with the role property associated with the user as the role property instant messaging account for the user and / or the employee corresponding to the user. The employee obtains the role property instant messaging account through the corresponding role associated with the user. When the employee leaves the enterprise, the association between the user and the role corresponding to the employee is canceled, and the employee who leaves the enterprise automatically loses the authority to avoid the risk of leakage of the confidential information of the enterprise. When, the employee transfers position, seamless docking is achieved, and communication account handover is prevented from lag or omission.

Description

technical field [0001] The invention relates to a method for managing instant messaging accounts in management systems such as ERP and CRM. 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). Traditional discretionary access control has high flexibility but low security, mandatory access control has high security but is too restrictive; role-based access control combines both, which is not only easy to manage but also reduces complexity, cost and error probability , which has been greatly developed in recent years. 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,...

AI Technical Summary

Problems solved by technology

[0012] 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. The permissions of the role are also easy to confuse; if you want to associate a new user, you cannot accurately determine how to choose the association

[0013] 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

[0014] 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

The above is already a relatively good situation. If the QQ used by the financial personnel and the QQ used by the R&D personnel are associated with the sales personnel after multiple associations, the confidential information of R&D or confidential financial information will be associated now. Sales staff know that it is very easy to leak sensitive information, which may cause serious losses to the company

[0019] D. When an employee joins a job or is transferred, he needs to associate an instant messaging account for the employee every time, which is a heavy workload; and there is a certain lag in re-association of the instant messaging account for the employee, which will affect the normal development of related work

For example, when employee A is transferred from the production supervisor to the sales supervisor, after handing over the existing instant messaging account of employee A to his successor, if the new instant messaging account is not associated with employee A, then employee A has no instant messaging at this time The account will not be able to carry out the corresponding work; if the existing instant messaging account of employee A is not handed over to his successor, then the successor will not be able to understand the previous business-related communication information, which is not conducive to the development of work

For another example, employee A holds the positions of production supervisor and after-sales supervisor, and is no longer the production supervisor (employee A's instant messaging account cannot be given to the successor, because it also contains the work-related communication information of the after-sales supervisor), if he becomes the production supervisor again If the supervisor's successor assigns a new instant messaging account, it is necessary to notify the communication contacts (for example, equipment maintenance personnel, subcontractors, etc.) one by one. It is also possible to receive subsequent production communication messages (for example, the sender of the information does not know that employee A is no longer the production supervisor)

For another example, when employee A is transferred from the production supervisor to the sales supervisor, he fails to assign a new instant messaging account to employee A immediately after handing over the existing instant messaging account of employee A to his successor. Handle work through instant messaging accounts, which is not conducive to the normal development of work

Images