Forum management method

Abstract

The invention discloses a forum management method, comprising the following steps: creating a system role, wherein the role is an independent individual, not a group / class; setting the forum board, the forum contains one or more forum boards; setting the participation roles / management roles of each forum board, and setting the permissions of the participation roles / management roles in the forum board; associating users with roles in the system, wherein users can use forums according to the permissions of their associated roles in forums, only one role can be associated with unique users at thesame time, and one user can be associated with one or more roles. The right in the forum board is assigned to the role, employees obtain their corresponding permissions in the forum through the rolesassociated with the corresponding users, and when employees leave their posts or transfer their posts, they can seamlessly connect with each other, and there will be no delay or omission in setting forum permissions, so employees' normal access to the forum will not be affected, and also the risk of confidential information disclosure is avoided.

Description

technical field [0001] The invention relates to a forum management method. 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, and users can indirectly access database resources by being assi...

AI Technical Summary

Problems solved by technology

[0007] 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 / job nature 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. Instead, change the permissions of the entire role, because the role is also associated with other employees whose permissions have not changed

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

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

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

[0013] There are three main modes of management of forum users in the traditional system: (1) Directly set the permissions of forum participants and administrators (persons, users): For companies with a large number of employees, the frequency of job transfer and job entry is high. It is necessary to set the permissions of employees in the forum for job transfer and entry. The operation is frequent, the workload is heavy, and it is easy to make mistakes.

What is especially fatal is: if the setting of employees' forum permissions is delayed or omitted, on the one hand, it will affect the normal use of employees in the forum, and on the other hand, it may lead to the leakage of company confidential information, which will bring unpredictable losses to the company

For example, Zhang San is now doing research and development, and authorized the viewing and deletion of posts in the R&D section of the forum, but after a while he will be transferred to sales, if he does not modify his forum permissions in time, on the one hand, it will affect Zhang San's normal access to the sales section ; On the other hand, Zhang San can still view and delete posts in the R&D section, which may cause leaks or be maliciously manipulated

When new employees join the company, if the forum authority is not set up for them in time, it will affect the new employees' understanding or learning of the company and the job position, and may affect the development of work

[0014] (2) Authorization by type of work: Refined control of permissions cannot be achieved, which may easily lead to information leakage. For example: for sales type authorization, if there are sales forums of the aircraft business department and furniture business department in a system, if the sales type of work can be set Seeing the above two forum sections, the salesperson of the furniture business department who is a sales worker can also see the sales forum of the aircraft business department. Obviously, this cannot meet the company's needs for forum authority management, and there is still a risk of confidential information leakage

[0015] (3) Authorization by department: It cannot be applied to certain specific situations and may easily lead to information leakage. For example, there may be multiple types of work in each department. Assemblers, testing workers, etc., if authorized by department, will lead to the same authority of different types of personnel in the forum forum, which will easily lead to information leakage; in addition, the department includes ordinary employees and department managers. The department head of the department participates in a certain section, which is simply not possible in this way

[0016] If you set the manager directly as a person: now Zhang San is engaged in sales management and is responsible for the management of the sales section (Zhang San is the moderator of the sales section). Now that Zhang San is transferred to production, another person should be assigned To take over Zhang San's management of the sales section; if it is not set in time, Zhang San can still see the company's subsequent sales or market information in the forum section, and there is a risk of confidential information leakage

On the other hand, if the moderator needs to review the new posts in the sales section, because Zhang San has been transferred from the post and he is no longer responsible, he may think that there is no need to review the pending posts in the sales section, which will lead to pending review. Posts cannot be reviewed in time, even if the new moderator takes over the management of this forum, he cannot review the previously submitted pending posts, because the review task is with Zhang San

Images