System permission configuration method, resource management system, device, medium and product

Abstract

The embodiment of the invention discloses a system authority configuration method, a resource management system, equipment, a medium and a product, and the system authority configuration method comprises the steps: providing different personnel basic information input interfaces, building different employee accounts according to different channels, binding the employee accounts with corresponding employee organizations, and carrying out the management of the employees. The employee accounts are managed through different employee organizations, so that the same system manages the personnel with different identities, on one hand, the management cost of the personnel with different identities can be reduced, on the other hand, different employee accounts are set for the personnel with different identities, and corresponding system use permissions are configured according to different employee accounts, so that the management efficiency is improved. According to the method and the system, the employee account can only access the system service with the authority, so that the risk of leakage of company information is avoided, the security of personnel management is improved, and the dual purposes of account management of external workers and data security are realized.

Description

Technical Field

[0001] The present disclosure relates to Internet technology, and in particular to a system authority configuration method, a resource management system, a device, a medium and a product. Background Art

[0002] For some companies with a wide range of businesses, in addition to managing their own internal employees, they may also need to manage external personnel such as external suppliers and franchisees. Take a company in the home improvement business as an example. There will be many franchise workers in the upstream and downstream of the industry: such as carpenters, bricklayers, electricians, etc. However, these franchise workers generally do not sign labor contracts directly with the company. In this way, these franchise workers cannot use the company's resource management system (such as Human Resource System, human resources system), and the company cannot manage these franchise workers through the resource management system. Summary of the invention

[0003] In order to solve the technical problems in the related art, the embodiments of the present disclosure provide a system permission configuration method, a resource management system, a device, a medium and a product.

[0004] According to a first aspect of an embodiment of the present disclosure, a system permission configuration method is provided, wherein the resource management system includes a first management component, a second management component, a middle platform, and a third management component, and the method includes:

[0005] Receiving first personnel basic information input through an interface, wherein the interface is the first management component or the second management component;

[0006] Determine an interface for inputting the first personnel basic information;

[0007] In response to the first basic personnel information coming from the first management component, generating a first type of employee account through the first management component, wherein the first type of employee account belongs to a first employee general organization;

[0008] In response to the first basic personnel information coming from the second management component, generating a second type of employee account through the second management component, wherein the second type of employee account belongs to a second employee general organization;

[0009] configuring corresponding system usage permissions for the first type of employee account and the second type of employee account, wherein different types of employee accounts have different corresponding system usage permissions;

[0010] The first basic information of the personnel and the first type of employee account and the second type of employee account after the system use permission is configured are transmitted to the third management component through the middle platform, so that the third management component stores the first basic information of the personnel and the employee account after the system use permission is configured;

[0011] Binding the employee organizations corresponding to the first type of employee account and the second type of employee account respectively through the first management component to obtain an organization matching relationship, and sending the organization matching relationship to the third management component through the middle platform;

[0012] The organization matching relationship is added to the first stored basic personnel information through the third management component to obtain second basic personnel information, wherein the second basic personnel information is employee attribute information.

[0013] As an optional embodiment of the present disclosure, the first management component is used to bind the employee organizations corresponding to the first type of employee account and the second type of employee account to obtain an organization matching relationship, and the organization matching relationship is sent to the third management component through the middle station, including:

[0014] For the first type of employee account, after the first management component generates the first type of employee account, the first management component determines a first target employee organization from the first employee general organization according to the first basic information of the personnel corresponding to the first type of employee account;

[0015] Managing and binding the first type of employee account with the first target employee organization through the first management component to obtain a first organization matching relationship;

[0016] The first organization matching relationship is sent to the third management component through the first management component via the middle platform.

[0017] As an optional embodiment of the present disclosure, the first management component is used to bind the employee organizations corresponding to the first type of employee account and the second type of employee account to obtain an organization matching relationship, and the organization matching relationship is sent to the third management component through the middle station, including:

[0018] For the second type of employee account, sending the second type of employee account to the first management component through the third management component;

[0019] Determining, by the first management component, a second target employee organization corresponding to the second type of employee account from the first employee general organization;

[0020] Managing and binding the second type of employee account with the second target employee organization through the first management component to obtain a second organization matching relationship;

[0021] The second organization matching relationship is sent to the third management component through the first management component via the middle platform.

[0022] As an optional embodiment of the present disclosure, the organization matching relationship is added to the first stored basic personnel information by the third management component to obtain second basic personnel information, wherein the second basic personnel information is employee attribute information, including:

[0023] In response to receiving the organization matching relationship, the third management component queries the first personnel basic information corresponding to the employee account in the organization matching relationship;

[0024] The third management component confirms whether the first basic information of the person queried contains the organization matching relationship;

[0025] In response to confirming that the queried first personnel basic information does not contain the organization matching relationship, the third management component adds the organization matching relationship to the stored first personnel basic information to obtain second personnel basic information, wherein the second personnel basic information is employee attribute information.

[0026] As an optional embodiment of the present disclosure, the transmitting the first personnel basic information and the employee account after the system use permission is configured to the third management component through the middle platform, so that the third management component stores the first personnel basic information and the employee account after the system use permission is configured, including:

[0027] For the first type of employee account, the first management component transmits the first person basic information received and the first type of employee account generated with the configured system usage authority to the third management component via the middle station;

[0028] In response to the first type of employee account, the first management component transmits the first personnel basic information received and the first type of employee account generated with the system use permission configured to the third management component via the middle platform, and the third management component stores the first personnel basic information and the first type of employee account with the system use permission configured in the employee data corresponding to the first management component;

[0029] For the second type of employee account, the second management component transmits the first person basic information received and the second type of employee account generated with the configured system usage authority to the third management component via the middle platform;

[0030] In response to the second type of employee account, the second management component transmits the first personnel basic information received and the second type of employee account generated with the configured system usage permissions to the third management component via the middle platform, and the third management component stores the first personnel basic information and the second type of employee account with the configured system usage permissions in the employee data corresponding to the second management component.

[0031] As an optional embodiment of the present disclosure, the method further includes:

[0032] Upon receiving a login request from any employee account, verify the system usage authority of the employee account;

[0033] In response to the system usage authority verification of the employee account being passed, the employee account accesses the system service having the system usage authority.

[0034] According to a second aspect of an embodiment of the present disclosure, a resource management system is provided, the resource management system comprising a first management component, a second management component, a middle platform and a third management component, wherein:

[0035] The first management component and the second management component respectively respond to the first basic personnel information input by the user as interfaces, wherein the first management component generates a first type of employee account in response to the first basic personnel information input by the user, and the first type of employee account belongs to a first employee general organization; the second management component generates a second type of employee account in response to the first basic personnel information input by the user, and the second type of employee account belongs to a second employee general organization; and configures corresponding system usage permissions for the first type of employee account and the second type of employee account, and different types of employees have different corresponding system service permissions;

[0036] And, the first management component is further used to bind the employee account and the employee organization corresponding to the employee account to obtain an organization matching relationship, wherein the employee account includes the first type of employee account and the second type of employee account;

[0037] The middle platform is used for transmitting the first basic information of the personnel and the employee account after the system use permission is configured to the third management component in response to the first management component and the second management component sending the first basic information of the personnel and the employee account after the system use permission is configured; and for sending the organization matching relationship to the third management component in response to the organization matching relationship sent by the first management component;

[0038] The third management component is used to store the first personnel basic information and the employee account after configuring system usage permissions in response to the first management component and the second management component sent via the middle station; and in response to the organization matching relationship sent by the first management component via the middle station, add the organization matching relationship to the stored first personnel basic information to obtain the second personnel basic information, wherein the second personnel basic information is employee attribute information.

[0039] As an optional embodiment of the present disclosure, the first management component is further used to, after generating the first type of employee account, determine a first target employee organization from the first employee general organization according to the first personnel basic information corresponding to the first type of employee account, manage and bind the first type of employee account with the first target employee organization to obtain a first organization matching relationship, and send the first organization matching relationship to the third management component via the middle station;

[0040] as well as,

[0041] The first management component is further used to respond to the second type of employee account sent by the third management component, determine the second target employee organization corresponding to the second type of employee account from the first employee general organization according to the first personnel basic information corresponding to the second type of employee account, manage and bind the second type of employee account with the second target employee organization, obtain a second organization matching relationship, and send the second organization matching relationship to the third management component via the middle station.

[0042] According to a third aspect of an embodiment of the present disclosure, there is provided an electronic device, including:

[0043] A memory for storing a computer program product;

[0044] The processor is used to execute the computer program product stored in the memory, and when the computer program product is executed, the method described in the first aspect above is implemented.

[0045] According to a fourth aspect of an embodiment of the present disclosure, a computer-readable storage medium is provided, on which computer program instructions are stored. When the computer program instructions are executed by a processor, the method described in the first aspect above is implemented.

[0046] According to a fifth aspect of an embodiment of the present disclosure, a computer program product is provided, comprising computer program instructions, which, when executed by a processor, implement the method described in the first aspect above.

[0047] According to the technical solution of the embodiment of the present disclosure, by providing different personnel basic information input interfaces, and establishing different employee accounts according to different interfaces, and binding the employee accounts with their corresponding employee organizations, so that the employee accounts can be managed by different employee organizations, the same system can manage personnel of different identities, on the one hand, it can reduce the cost of managing personnel of different identities, on the other hand, different employee accounts are set for personnel of different identities, and the corresponding system usage permissions are configured according to different employee accounts, so that the employee accounts can only access the system services with their permissions, and the allocation and restriction of employee system permissions are realized, which not only meets the needs of managing employees of different identities with the same system, but also avoids the risk of company information leakage, improves the security of personnel management, and achieves the dual goals of account management and data security for external workers; in addition, the information such as different employee accounts is uniformly stored and managed by a component (such as the third management component) in the system, which can reduce the cost of system management. Furthermore, the embodiment of the present disclosure is based on the developed system and the existing information entry rules, and increases the reasonable range of permissions for outsourced employees (i.e., the first type of employee accounts) The opening, the learning cost for the business side is low, and the upgrade of the resource management system is completed efficiently to meet the needs of the business side.

[0048] The technical solution of the present disclosure is further described in detail below through the accompanying drawings and embodiments. BRIEF DESCRIPTION OF THE DRAWINGS

[0049] The accompanying drawings, which constitute a part of the specification, illustrate embodiments of the present disclosure and, together with the description, serve to explain the principles of the present disclosure.

[0050] The present disclosure may be more clearly understood from the following detailed description with reference to the accompanying drawings, in which:

[0051] Figure 1 This is one of the flowcharts of a system permission configuration method according to an embodiment of the method disclosed herein.

[0052] Figure 2 This is a second flowchart of a system permission configuration method according to an embodiment of the method disclosed herein.

[0053] Figure 3 This is a third flowchart of a system permission configuration method according to an embodiment of the method disclosed herein.

[0054] Figure 4 This is a fourth flowchart of a system permission configuration method according to an embodiment of the method disclosed herein.

[0055] Figure 5 The figure is a schematic diagram of the management process of the first type of employee accounts according to an embodiment of the method disclosed herein.

[0056] Figure 6 This is a schematic diagram of the management process of the second type of employee accounts in one embodiment of the method disclosed herein.

[0057] Figure 7 The present invention is a structural block diagram of a resource management system according to an embodiment of the present invention.

[0058] Figure 8 The present invention is a structural block diagram of an electronic device according to an embodiment of the present invention. DETAILED DESCRIPTION

[0059] In the related art, for some non-company internal employees (such as external suppliers and franchisees) who need to be managed by employee services, if the company's resource management system (for example, Human Resource System) is used indiscriminately to manage these personnel, these personnel may have the same permissions as internal employees, for example, they can log in to the company system and see the information disclosed to the outside by the company. In this way, there will be a security risk of important information leakage. However, if these personnel are not managed and they are completely restricted from logging in to the company's resource management system, they will not be able to use some of the company's services (such as attendance application, on-the-job training, etc.). If these services are managed entirely by foremen, for example, when the number of workers increases sharply, the management cost is high and the management level is uneven. If a new system is developed to manage non-company internal employees separately, the company's development and management costs will be greatly increased, and the learning cost is also high for the business side.

[0060] In order to solve the technical problems in the related art, the embodiments of the present disclosure provide a system permission configuration method, a resource management system, a device, a medium and a product. The technical solution of the embodiments of the present disclosure will be described in detail below in conjunction with the accompanying drawings.

[0061] Among them, the resource management system can be, for example, an HR system, an OA system (Office Automation, office automation system), etc. In the embodiment of the present disclosure, in order to facilitate the classified management of different types of employees and ensure the security of the company's system permissions, data permissions, etc., the resource management system is divided into a first management component, a second management component, a middle platform, and a third management component, wherein the first management component, the second management component, and the third management component can be, for example, a front-end application service layer, and the middle platform can be a logic layer, for example, providing service interfaces for the first management component, the second management component, and the third management component. Different types of employees include at least two types of personnel, such as external suppliers, franchisees, etc. (for example, in the home improvement business, there will be many franchise workers, such as carpenters, bricklayers, electricians, etc.) and internal company employees.

[0062] Figure 1 This is one of the flowcharts of a system permission configuration method according to an embodiment of the method disclosed herein. Figure 1 As shown, a system permission configuration method of an embodiment of the present disclosure, wherein the resource management system may include a first management component, a second management component, a middle platform and a third management component. Based on this, the management method of the internal management system of the embodiment of the present disclosure may include the following steps:

[0063] Step 101, receiving first personnel basic information input through an interface, wherein the interface includes a first management component and a second management component.

[0064] The user may be, for example, a human resources manager of a company, who may input the basic information of the first person through an interface. In the embodiment of the present disclosure, at least two interfaces are provided, exemplarily including a first management component and a second management component, wherein the first management component and the second management component are two different user graphical interfaces and their corresponding interfaces, and the user may input the basic information of the first person by selecting a corresponding graphical user interface, inputting text or using a selection button provided by the interface, and the like.

[0065] In the disclosed embodiment, the first basic personnel information may include at least basic information such as the employee's name, telephone number, address, and ID number, and may also include the employee's job role information, such as product manager, R&D engineer, bricklayer, electrician, etc. After receiving the first basic personnel information, the employee account type corresponding to the first basic personnel information may be determined according to the input interface (first management component or second management component) of the first basic personnel information.

[0066] Step 102, determine the interface of the first person's basic information.

[0067] In some embodiments, different interfaces may include different interface identifiers, so as to distinguish the interfaces of the sources of the basic personnel information, and then determine which personnel type the first basic personnel information belongs to through the interface.

[0068] In other embodiments, the type of personnel corresponding to the first personnel basic information can be distinguished through an interface, and the personnel type can include, for example, internal employees and non-internal employees. As another optional embodiment, the interface can also be determined according to the user's input click operation. For example, the user clicks on the graphical user interface of the first management component to determine that the interface is the first management component. This is not limited in the embodiments of the present disclosure.

[0069] Step 103, in response to the first personnel basic information coming from the first management component, a first type of employee account is generated by the first management component, wherein the first type of employee account belongs to the first employee general organization.

[0070] In the case where it is determined that the first personnel basic information comes from the first management component, a first type of employee account can be generated through the first management component. In the embodiments of the present disclosure, the first management component can be used for information management or account registration of franchise workers or external supplier workers.

[0071] Among them, the first type of employee account is, for example, a franchise worker account or an external supplier worker account. Thus, the first overall employee organization can be, for example, a franchise worker organization or an external supplier worker organization, so as to determine the job relationship of the employees. The first type of employee account can be set as a 16-digit C-terminal account.

[0072] In addition, the first overall employee organization can be further divided into multiple sub-organizations. For example, if the first overall employee organization is a franchise worker organization, it can be divided into a bricklayer worker organization, an electrician worker organization, a carpenter worker organization, etc.

[0073] Step 104, in response to the first personnel basic information coming from the second management component, generate a second type of employee account through the second management component, where the second type of employee account belongs to the second overall employee organization.

[0074] In the case where it is determined that the first personnel basic information comes from the second management component, a second type of employee account can be generated through the second management component. In the embodiments of the present disclosure, the second management component can be used for information management or account registration of the company's internal employees.

[0075] Among them, the second type of employee account is an internal employee account. Thus, the second overall employee organization can be, for example, an internal employee organization. The second type of employee account can be set, for example, as a 10-digit B-terminal account. And the second overall employee organization can also be divided into multiple sub-organizations. For example, if the second overall employee organization is an internal employee organization, it is divided into various departments within the company. The second type of employee account can be classified into specific departments, such as the product department, the R & D department, the administrative department, etc. Further, it can be further divided into different positions, such as software development engineer, product manager, administrative staff, etc.

[0076] In some embodiments, the employee account in the embodiments of the present disclosure can be, for example, its mobile phone number. In other embodiments, it can also be a management number automatically generated by the resource management system according to the employee's entry order.

[0077] Step 105, configure corresponding system usage permissions for the first type of employee account and the second type of employee account, where different types of employee accounts have different corresponding system usage permissions.

[0078] System usage rights may include, on the one hand, the usage rights of the resource management system (e.g., human resource management) in the embodiment of the present disclosure, and on the other hand, may also include, for example, other company systems (e.g., the company's R&D code hosting system, the company's project management system, financial management system, etc.). In the embodiment of the present disclosure, corresponding system usage rights may be configured for employee accounts of different employee types. For example, for some service functions of the resource management system or other systems of the company that may contain sensitive information or core business operations, they are only allocated to employee accounts corresponding to the internal employee types of the enterprise. For other systems or service functions in the resource management system that may contain some non-sensitive work tasks or collaboration tools, they may be allocated to both employee accounts corresponding to the internal employee types of the enterprise and employee accounts corresponding to non-internal employee types.

[0079] As another embodiment, for the same system, different service function permission points can be set for employee accounts of different employee types. For example, assuming that the resource management system includes leave service function, clock-in service function, performance evaluation service function, training management service function, employee data maintenance service function, salary and welfare management server function, etc., for employee accounts corresponding to internal employee types of the enterprise, for example, leave service function, clock-in service function, performance evaluation service function, training management service function and salary and welfare management service can be allocated, while for employee accounts corresponding to non-internal employee types, only leave service function, clock-in service function and training management service function are allocated. In this way, it can be ensured that only accounts with corresponding permissions can access the corresponding service functions of the corresponding system, thereby improving the security of the company's system services.

[0080] As an embodiment of the present disclosure, in order to ensure that only accounts with corresponding permissions can access corresponding system service functions, thereby improving the security of the corresponding system, the system usage permissions of the employee account can be verified when the employee account logs in. Exemplarily, upon receiving a login request from any employee account, the system usage permissions of the employee account are verified, and in response to the system usage permissions of the employee account being verified, the employee account accesses the system service with system usage permissions. In the embodiment of the present disclosure, the system usage permissions verification may include two parts: verification of the employee account and verification of its system usage permissions. For example, when receiving a login request from any employee account, the employee account is first verified, such as verifying the password of the employee account, to determine whether the employee account has the authority to log in to the resource management system; after the login authority verification is passed, the employee account is allowed to enter the resource management system interface, and then the system usage authority is verified to determine which system functions the employee account has the authority to use. For example, for an employee account M corresponding to a non-internal employee type, it is verified whether the employee account M has the resource management system's leave service function, clock-in service function, and training management service function and other service functions. This can be determined by checking the system service functions allocated in the system usage authority configured for the employee account M. If it is determined that these service functions are available, the employee account M can access the resource management system's leave service function, clock-in service function, and training management service function and other service functions accordingly, otherwise it cannot.

[0081] Step 106, transmit the first person's basic information and the first and second employee accounts after configuring system usage permissions to the third management component through the middle platform, so that the third management component stores the first person's basic information and the employee accounts after configuring system usage permissions.

[0082] The third management component is, for example, UC (User Center), which is used for employee data maintenance, and may include a storage function to store employee data. In addition, the third management component may interact with the first management component and the second management component to obtain data from the first management component and the second management component for storage, and may also provide a query interface for the first management component and the second management component, so that the first management component and the second management component can perform data query, etc.

[0083] In the embodiment of the present disclosure, after completing the corresponding system usage permission configuration for the employee account, the interface of the third management component can be called through the middle platform to send the employee account and the corresponding first personnel basic information to the third management for storage.

[0084] Different employee accounts are transmitted to the third management component in different ways. In some embodiments, for employee accounts corresponding to non-internal employee types, such employee accounts and the corresponding first personnel basic information can be transmitted to the third management component through the first management component via the middle platform; for employee accounts corresponding to internal employee types of the enterprise, such employee accounts are transmitted to the third management component via the middle platform via the second management component. The third management component will respond to different employee accounts and the corresponding first personnel basic information transmitted from different channels (the first management component or the second management component) and store them. In this way, the employee accounts and the corresponding first personnel basic information are stored through the third management component, and the employee data (employee accounts and the corresponding first personnel basic information) can be managed uniformly, reducing the data management of multiple systems or multiple channels and increasing the employee data management costs.

[0085] Step 107, the employee organizations corresponding to the first type of employee account and the second type of employee account are bound respectively through the first management component to obtain an organization matching relationship, and the organization matching relationship is sent to the third management component through the middle station.

[0086] In the disclosed embodiment, the employee organization can be distinguished for different employee types, so as to uniformly manage the corresponding employee accounts. Exemplarily, for employee accounts corresponding to non-internal employee types, the employee organization may include, for example, a first-level organization "non-internal employee" and a second-level organization, and the second-level organization may include, for example, a bricklaying department, a carpentry department, an electrician department, etc.; for employee accounts corresponding to internal employee types of the enterprise, the employee organization may include, for example, a first-level organization "internal employee" and a second-level organization, and the second-level organization may include, for example, a research and development department, a product department, an administrative department, a financial department, etc. As another embodiment, it may also include only a first-level organization, and for employee accounts corresponding to non-internal employee types, the employee organization may include only one level of employee organizations such as a bricklaying department, a carpentry department, an electrician department, etc.; for employee accounts corresponding to internal employee types of the enterprise, the employee organization may include a research and development department, a product department, an administrative department, a financial department, etc.

[0087] Furthermore, for different employee accounts, they are bound to corresponding employee organizations. For example, for an employee account B with a 10-digit number, it belongs to the internal employee type of the enterprise, and its employee organization is the product department, then an organizational matching relationship is established between the employee account B with the 10-digit number and the product department; for an employee account C with a 16-digit number, it belongs to the non-internal employee type, and its employee organization is the bricklaying department, then an organizational matching relationship is established between the employee account C with the 16-digit number and the bricklaying department.

[0088] After completing the employee organization binding and obtaining the organization matching relationship, the organization matching relationship is sent to the third management component through the middle platform. That is, the interface of the third management organization can be called through the middle platform to transfer the obtained organization matching relationship data to the third management component.

[0089] Step 108: Add the organization matching relationship to the stored first personnel basic information through the third management component to obtain second personnel basic information, wherein the second personnel basic information is employee attribute information.

[0090] Exemplarily, the third management component has stored the first personnel basic information including the employee's name, telephone number, address, ID number and other basic information and job role information, and then added the organizational matching relationship based on the basic information and job role information to obtain the second personnel basic information, wherein the second personnel basic information is employee attribute information and is stored by the third management component.

[0091] Taking an employee account D corresponding to an internal employee type of an enterprise as an example, the first basic information of the employee includes:

[0092] Employee name: Li;

[0093] Tel: 132xxxxxxxx;

[0094] The address is: Building C, Community B, Street A;

[0095] ID number: 123456xxxxxxxx4567;

[0096] Position roles: Project Manager;

[0097] After the aforementioned step 107, in addition to binding the employee organization to which the internal employee belongs as the project department, the obtained organization matching relationship is employee account D-project department. After adding the organization matching relationship to the first employee basic information, the second employee basic information is obtained, wherein the second employee basic information is employee attribute information, for example:

[0098] Employee name: Li;

[0099] Tel: 132xxxxxxxx;

[0100] The address is: Building C, Community B, Street A;

[0101] ID number: 123456xxxxxxxx4567;

[0102] Position roles: Project Manager;

[0103] Organization matching relationship: employee account D—project department.

[0104] It should be noted that the above expression of employee attribute information (ie, the second personnel basic information) is an example and does not limit the present disclosure.

[0105] In some embodiments, step 108 can be further specifically implemented as follows: for the first type of employee account, the first management component transmits the first personnel basic information received and the first type of employee account generated after the system use permission is configured to the third management component through the middle platform, and the third management component can respond to the first personnel basic information from the first management component and the first type of employee account generated after the system use permission is configured, and then store the first personnel basic information and the first type of employee account after the system use permission is configured in the employee data corresponding to the first management component; for the second type of employee account, the first personnel basic information received and the second type of employee account generated after the system use permission is configured are transmitted to the third management component through the middle platform by the second management component, and the third management component responds to the first personnel basic information from the second management component and the second type of employee account generated after the system use permission is configured, and stores the first personnel basic information and the second type of employee account after the system use permission is configured in the employee data corresponding to the second management component. Through this embodiment, the third management component can store the employee data corresponding to the interface according to different interfaces (the first management component or the second management component), so that in the subsequent data query process, the employee data corresponding to the interface can be accurately and quickly found.

[0106] As an optional embodiment, in the aforementioned Figure 1 Based on the embodiment shown, Figure 2 This is a flowchart of a method for configuring system permissions in accordance with an embodiment of the disclosed method. Figure 2 As shown, step 107 can be implemented by the following steps:

[0107] Step 1071, for the first type of employee account, after the first management component generates the first type of employee account, the first management component determines a first target employee organization from the first employee general organization according to the first personnel basic information corresponding to the first type of employee account;

[0108] Step 1072: managing and binding the first type of employee account with the first target employee organization through the first management component to obtain a first organization matching relationship;

[0109] Step 1073: Send the first organization matching relationship to the third management component via the first management component through the middle station.

[0110] As another optional embodiment, in the aforementioned Figure 1 and Figure 2 On the basis of Figure 3As shown, step 107 can also be implemented by the following steps:

[0111] Step 1074, for the second type of employee account, send the second type of employee account to the first management component through the third management component;

[0112] Step 1075, determining a second target employee organization corresponding to the second type of employee account from the first employee general organization through the first management component;

[0113] Step 1076, managing and binding the second type of employee account with the second target employee organization through the first management component to obtain a second organization matching relationship;

[0114] Step 1077: Send the second organization matching relationship to the third management component through the first management component via the middle station.

[0115] In the embodiments of the present disclosure, Figure 3 In the embodiment shown, the corresponding employee organization can be determined according to the employee accounts of different categories, and then the two are bound to each other. The first type of employee account can be completed in the first management component. For example, the first basic information of the employee includes the type of work, such as bricklayer. Then, it is bound to the first target employee organization bricklayer organization under the first employee general organization. In this embodiment, referring to the content of the aforementioned step 107, the first employee general organization is, for example, a "non-internal employee organization", and the target employee organization is a secondary organization or sub-organization under the first employee general organization. The secondary organization or sub-organization includes, for example, a bricklayer department, a carpenter department, an electrician department, etc. In this way, assuming that the type of work in the work attribute information of a first type of employee account A is bricklayer, then the first employee general organization is a "non-internal employee organization", and the "bricklayer department" is determined from the "non-internal employee organization" through the type of work in the work attribute information. The "bricklayer department" is the first target employee organization, and a management binding relationship is established between the first type of employee account A and the "bricklayer department" to form a first organization matching relationship.

[0116] Similarly, for the second type of employee account, for example, if it belongs to the product manager position and belongs to the second employee organization, the relationship binding between the account and the employee organization can be completed in the second management component. However, it may also have to serve as a position under the first employee organization. In this case, the third management component can send the second type of employee account or the second type of employee account and its corresponding first personnel basic information to the first management component, so that the second type of employee account can be bound to the target employee organization under the first employee organization (for example, the bricklayer foreman) through the first management component. In this way, it can view the employee information managed by it under the target employee organization under the first employee organization and use related services.

[0117] After completing the organization relationship binding and obtaining the organization matching relationship, the interface of the third management component can be called through the middle station, so that the organization matching relationship is sent to the third management component through the middle station.

[0118] In this way, binding the employee account and the employee organization to which it belongs helps to classify and manage the employee account without confusing the management of internal and non-internal employees, thus ensuring the security of company data. In addition, for some people who have to work in both internal and external positions (for example, a product manager who also works as a bricklaying foreman), in addition to binding them to the sub-organization or secondary organization in the second employee organization, they are also bound to the sub-organization or secondary organization of the first employee organization. In this way, they can be allocated more system usage permissions and realize more job roles. At the same time, more system usage permissions are opened only for specific personnel (working in both internal and external positions), which can ensure the security of the company's system and data security.

[0119] For example, in the aforementioned Figures 1 to 3 On the basis of Figure 4 As shown, step 108 can be implemented as follows:

[0120] Step 1081, in response to receiving the organization matching relationship, the third management component queries the first person basic information corresponding to the employee account in the organization matching relationship;

[0121] Step 1082, confirming through the third management component whether the queried first personnel basic information already contains an organization matching relationship;

[0122] Step 1083, in response to confirming that the queried first personnel basic information does not contain an organization matching relationship, the third management component adds the organization matching relationship to the stored first personnel basic information to obtain second personnel basic information, wherein the second personnel basic information is employee attribute information.

[0123] In this embodiment, when the third management component receives the organization matching relationship (including the first organization matching relationship and the second organization matching relationship), it will query the stored first personnel basic information corresponding to the employee account with the employee account and other information in the organization matching relationship, so as to determine whether the originally stored first personnel basic information contains the currently received organization matching relationship. If the originally stored first personnel basic information does not contain the organization matching relationship, the third management component will add the organization matching relationship to the originally stored first personnel basic information to obtain new first personnel basic information with the organization matching relationship added, that is, the second personnel basic information, wherein the second personnel basic information is employee attribute information. In this way, repeated storage of organization matching relationships can be avoided, resulting in data redundancy and increased storage resource burden.

[0124] Combine the following Figure 5and Figure 6 The establishment and storage processes of the first type of employee account and the second type of employee account in the embodiments of the present disclosure are respectively introduced.

[0125] like Figure 5 As shown, the establishment and storage process of the first type of employee account, the employee attribute information of the first type of employee account is input into the first management component, and then the first management component generates the corresponding first type of employee account according to the first personnel basic information, and then, firstly, the first type of employee account and its first personnel basic information are transmitted to the third management component through the middle platform, and the third management component stores the first type of employee account and its first personnel basic information, and then, the first management component binds the corresponding first target employee organization according to the employee organization to which the first type of employee account belongs, and obtains the corresponding first organization matching relationship, and after completion, the interface of the third management component is called through the middle platform to synchronize the first organization matching relationship to the third management component, so that the third management component updates the first organization matching relationship to the first type of employee account and its corresponding first personnel basic information.

[0126] like Figure 6 As shown, the establishment and storage process of the second type of employee account, the employee attribute information of the second type of employee account is input into the second management component, and then the second management component generates the corresponding second type of employee account according to the first personnel basic information, and then calls the third management component interface through the middle station, so as to synchronize the second type of employee account and its corresponding first personnel basic information to the third management component for storage. In the case where the second type of employee account also manages the employee position corresponding to the first type of employee account, the third management component then sends the second type of employee account and its corresponding first personnel basic information to the first management component, and the first management component binds the second target employee organization to obtain the second organization matching relationship, and then sends the second organization matching relationship to the third management component, so that the third management organization updates the second organization matching relationship to the second type of employee account and its corresponding first personnel basic information. In some embodiments, in the process of synchronizing the second organization matching relationship to the third management component, the interface of the third management component can be called through the middle station for synchronization.

[0127] According to the technical solution of the embodiment of the present disclosure, by providing different personnel basic information input interfaces, and establishing different employee accounts according to different channels, and binding the employee accounts with their corresponding employee organizations, so that the employee accounts can be managed by different employee organizations, the same system can manage personnel of different identities, on the one hand, it can reduce the cost of managing personnel of different identities, on the other hand, different employee accounts are set for personnel of different identities, and the corresponding system usage permissions are configured according to different employee accounts, so that the employee accounts can only access the system services with their permissions, and the allocation and restriction of employee system permissions are realized, which not only meets the needs of managing employees of different identities with the same system, but also avoids the risk of company information leakage, improves the security of personnel management, and achieves the dual goals of account management and data security for external workers; in addition, the information of different employee accounts is uniformly stored and managed by a component (such as the third management component) in the system, which can reduce the cost of system management. Furthermore, the embodiment of the present disclosure is based on the developed system and the existing information entry rules, and increases the reasonable range of permissions of outsourced employees (i.e., the first type of employee accounts) The opening, the learning cost for the business side is low, and the upgrade of the resource management system is completed efficiently to meet the needs of the business side.

[0128] Correspondingly, the embodiments of the present disclosure also provide system embodiments corresponding to the aforementioned method embodiments. Figure 7 FIG. 1 is a structural block diagram of a resource management system according to an embodiment of the device disclosed herein. Figure 7 As shown, a resource management system according to an embodiment of the present disclosure may include a first management component 801, a second management component 802, a middle platform 803, and a third management component 804, wherein:

[0129] The first management component 801 and the second management component 802 respectively serve as interfaces to respond to the first basic information of a person input by a user, wherein the first management component generates a first type of employee account in response to the first basic information of a person input by a user, and the first type of employee account belongs to a first employee general organization;

[0130] The second management component generates a second type of employee account in response to the first basic information of the personnel input by the user, and the second type of employee account belongs to a second employee general organization; and configures corresponding system usage permissions for the first type of employee account and the second type of employee account, and different types of employees have different corresponding system service permissions;

[0131] Furthermore, the first management component 801 is further used to bind the employee account to the employee organization corresponding to the employee account to obtain an organization matching relationship, wherein the employee account includes a first type of employee account and a second type of employee account;

[0132] The middle platform 803 is used for transmitting the first basic personnel information and the employee account after the system use permission is configured to the third management component 804 in response to the first management component 801 and the second management component 802 sending the first basic personnel information and the employee account after the system use permission is configured; and in response to the organization matching relationship sent by the first management component 801, sending the organization matching relationship to the third management component 804;

[0133] The third management component 804 is used to store the first personnel basic information and the employee account after configuring system usage permissions in response to the first management component 801 and the second management component 802 sent via the middle station 803; and in response to the organization matching relationship sent by the first management component 801 via the middle station 803, add the organization matching relationship to the stored first personnel basic information to obtain second personnel basic information, wherein the second personnel basic information is employee attribute information.

[0134] According to the technical solution of the embodiment of the present disclosure, by providing different personnel basic information input interfaces, and establishing different employee accounts according to different channels, and binding the employee accounts with their corresponding employee organizations, so that the employee accounts can be managed by different employee organizations, the same system can manage personnel of different identities, on the one hand, it can reduce the cost of managing personnel of different identities, on the other hand, different employee accounts are set for personnel of different identities, and the corresponding system usage permissions are configured according to different employee accounts, so that the employee accounts can only access the system services with their permissions, and the allocation and restriction of employee system permissions are realized, which not only meets the needs of managing employees of different identities with the same system, but also avoids the risk of company information leakage, improves the security of personnel management, and achieves the dual goals of account management and data security for external workers; in addition, the information of different employee accounts is uniformly stored and managed by a component (such as the third management component) in the system, which can reduce the cost of system management. Furthermore, the embodiment of the present disclosure is based on the developed system and the existing information entry rules, and increases the reasonable range of permissions of outsourced employees (i.e., the first type of employee accounts) The opening, the learning cost for the business side is low, and the upgrade of the resource management system is completed efficiently to meet the needs of the business side.

[0135] As an optional embodiment of the present disclosure, the first management component 801 is further used to, after generating the first type of employee account, determine a first target employee organization from the first employee general organization according to the first personnel basic information corresponding to the first type of employee account, manage and bind the first type of employee account with the first target employee organization, obtain a first organization matching relationship, and send the first organization matching relationship to the third management component 804 via the middle station 803;

[0136] as well as,

[0137] The first management component 801 is further used to respond to the second type of employee account sent by the third management component 804, determine the second target employee organization corresponding to the second type of employee account from the first employee general organization according to the first personnel basic information corresponding to the second type of employee account, manage and bind the second type of employee account with the second target employee organization, obtain a second organization matching relationship, and send the second organization matching relationship to the third management component 804 via the middle station 803.

[0138] The technicians in the relevant field can clearly understand that for the convenience and simplicity of description, only the division of the above-mentioned functional units and modules is used as an example for illustration. In practical applications, the above-mentioned function allocation can be completed by different functional units and modules as needed, that is, the internal structure of the device can be divided into different functional units or modules to complete all or part of the functions described above. The functional units and modules in the embodiment can be integrated in a processing unit, or each unit can exist physically separately, or two or more units can be integrated in one unit. The above-mentioned integrated unit can be implemented in the form of hardware or in the form of software functional units. In addition, the specific names of the functional units and modules are only for the convenience of distinguishing each other, and are not used to limit the scope of protection of this application. The specific working process of the units and modules in the above-mentioned system can refer to the corresponding process in the aforementioned method embodiment, which will not be repeated here.

[0139] Below, reference Figure 8 The electronic device according to the embodiment of the present disclosure is described. The electronic device may be any one or both of the first device and the second device, or a stand-alone device independent of them, and the stand-alone device may communicate with the first device and the second device to receive the collected input signals from them.

[0140] Figure 8 A block diagram of an electronic device according to an embodiment of the present disclosure is illustrated.

[0141] like Figure 8 As shown, an electronic device (or device) includes one or more processors and memory.

[0142] The processor may be a central processing unit (CPU) or other forms of processing units having data processing capabilities and / or instruction execution capabilities, and may control other components in the electronic device to perform desired functions.

[0143] The memory may store one or more computer program products, and the memory may include various forms of computer-readable storage media, such as volatile memory and / or non-volatile memory. The volatile memory may include, for example, a random access memory (RAM) and / or a cache memory (cache), etc. The non-volatile memory may include, for example, a read-only memory (ROM), a hard disk, a flash memory, etc. One or more computer program products may be stored on the computer-readable storage medium, and the processor may run the computer program product to implement the system permission configuration method of each embodiment of the present disclosure described above and / or other desired functions.

[0144] In one example, the electronic device may further include: an input device and an output device, and these components are interconnected via a bus system and / or other forms of connection mechanisms (not shown).

[0145] In addition, the input device may also include, for example, a keyboard, a mouse, and the like.

[0146] The output device can output various information to the outside, including determined distance information, direction information, etc. The output device can include, for example, a display, a speaker, a printer, a communication network and a remote output device connected thereto, and the like.

[0147] Of course, to simplify, Figure 8 Only some of the components related to the present disclosure in the electronic device are shown, and components such as a bus, an input / output interface, etc. are omitted. In addition, according to specific application situations, the electronic device may further include any other appropriate components.

[0148] In addition to the above-mentioned methods and devices, an embodiment of the present disclosure may also be a computer program product (or product), which includes computer program instructions, which, when executed by a processor, enable the processor to execute the steps in the system permission configuration method according to various embodiments of the present disclosure described in the above part of this specification.

[0149] The computer program product may be written in any combination of one or more programming languages ​​to write program code for performing the operations of the disclosed embodiments, including object-oriented programming languages ​​such as Java, C++, etc., and conventional procedural programming languages ​​such as "C" or similar programming languages. The program code may be executed entirely on the user computing device, partially on the user device, as a separate software package, partially on the user computing device and partially on a remote computing device, or entirely on a remote computing device or server.

[0150] In addition, an embodiment of the present disclosure may also be a computer-readable storage medium (or medium) on which computer program instructions are stored, and when the computer program instructions are executed by a processor, the processor executes the steps of the system permission configuration method according to various embodiments of the present disclosure described in the above part of this specification.

[0151] The computer readable storage medium can adopt any combination of one or more readable media. The readable medium can be a readable signal medium or a readable storage medium. The readable storage medium can include, for example, but is not limited to, a system, device or device of electricity, magnetism, light, electromagnetic, infrared, or semiconductor, or any combination of the above. More specific examples (non-exhaustive list) of readable storage media include: an electrical connection with one or more wires, a portable disk, a hard disk, a random access memory (RAM), a read-only memory (ROM), an erasable programmable read-only memory (EPROM or flash memory), an optical fiber, a portable compact disk read-only memory (CD-ROM), an optical storage device, a magnetic storage device, or any suitable combination of the above.

[0152] The basic principles of the present disclosure are described above in conjunction with specific embodiments. However, it should be noted that the advantages, strengths, effects, etc. mentioned in the present disclosure are only examples and not limitations, and it cannot be considered that these advantages, strengths, effects, etc. are required by each embodiment of the present disclosure. In addition, the specific details disclosed above are only for the purpose of illustration and ease of understanding, and are not limitations. The above details do not limit the present disclosure to the necessity of adopting the above specific details to be implemented.

[0153] Each embodiment in this specification is described in a progressive manner, and each embodiment focuses on the differences from other embodiments. The same or similar parts between the embodiments can be referred to each other. For the system embodiment, since it basically corresponds to the method embodiment, the description is relatively simple, and the relevant parts can be referred to the partial description of the method embodiment.

[0154] The block diagrams of the devices, apparatuses, equipment, and systems involved in this disclosure are only illustrative examples and are not intended to require or imply that they must be connected, arranged, and configured in the manner shown in the block diagrams. As will be appreciated by those skilled in the art, these devices, apparatuses, equipment, and systems can be connected, arranged, and configured in any manner. Words such as "including," "comprising," "having," and the like are open words, referring to "including but not limited to," and can be used interchangeably therewith. The words "or" and "and" used herein refer to the words "and / or," and can be used interchangeably therewith, unless the context clearly indicates otherwise. The word "such as" used herein refers to the phrase "such as but not limited to," and can be used interchangeably therewith.

[0155] The method and apparatus of the present disclosure may be implemented in many ways. For example, the method and apparatus of the present disclosure may be implemented by software, hardware, firmware, or any combination of software, hardware, and firmware. The above order of steps for the method is for illustration only, and the steps of the method of the present disclosure are not limited to the order specifically described above, unless otherwise specifically stated. In addition, in some embodiments, the present disclosure may also be implemented as a program recorded in a recording medium, which includes machine-readable instructions for implementing the method according to the present disclosure. Therefore, the present disclosure also covers a recording medium storing a program for executing the method according to the present disclosure.

[0156] It should also be noted that in the apparatus, device and method of the present disclosure, each component or each step can be decomposed and / or recombined. Such decomposition and / or recombination should be regarded as equivalent solutions of the present disclosure.

[0157] The above description of the disclosed aspects is provided to enable any person skilled in the art to make or use the present disclosure. Various modifications to these aspects will be readily apparent to those skilled in the art, and the general principles defined herein may be applied to other aspects without departing from the scope of the present disclosure. Therefore, the present disclosure is not intended to be limited to the aspects shown herein, but rather to the widest scope consistent with the principles and novel features disclosed herein.

[0158] The above description has been given for the purpose of illustration and description. In addition, this description is not intended to limit the embodiments of the present disclosure to the forms disclosed herein. Although multiple example aspects and embodiments have been discussed above, those skilled in the art will recognize certain variations, modifications, changes, additions and sub-combinations thereof.

Claims

1. A system authority configuration method, applied to a resource management system, wherein the resource management system includes a first management component, a second management component, a middle platform, and a third management component, and the method includes: Receiving first personnel basic information input through an interface, wherein the interface is the first management component or the second management component; Determine an interface for inputting the first personnel basic information; In response to the first basic personnel information coming from the first management component, generating a first type of employee account through the first management component, wherein the first type of employee account belongs to a first employee general organization; In response to the first basic personnel information coming from the second management component, generating a second type of employee account through the second management component, wherein the second type of employee account belongs to a second employee general organization; configuring corresponding system usage permissions for the first type of employee account and the second type of employee account, wherein different types of employee accounts have different corresponding system usage permissions; The first basic information of the personnel and the first type of employee account and the second type of employee account after the system use permission is configured are transmitted to the third management component through the middle platform, so that the third management component stores the first basic information of the personnel and the employee account after the system use permission is configured; Binding the employee organizations corresponding to the first type of employee account and the second type of employee account respectively through the first management component to obtain an organization matching relationship, and sending the organization matching relationship to the third management component through the middle platform; The organization matching relationship is added to the first stored basic personnel information through the third management component to obtain second basic personnel information, wherein the second basic personnel information is employee attribute information.

2. The method according to claim 1, characterized in that The step of binding the employee organizations corresponding to the first type of employee account and the second type of employee account respectively through the first management component to obtain an organization matching relationship, and sending the organization matching relationship to the third management component through the middle station includes: For the first type of employee account, after the first management component generates the first type of employee account, the first management component determines a first target employee organization from the first employee general organization according to the first basic information of the personnel corresponding to the first type of employee account; Managing and binding the first type of employee account with the first target employee organization through the first management component to obtain a first organization matching relationship; The first organization matching relationship is sent to the third management component through the first management component via the middle platform.

3. The method according to claim 1, characterized in that The step of binding the employee organizations corresponding to the first type of employee account and the second type of employee account respectively through the first management component to obtain an organization matching relationship, and sending the organization matching relationship to the third management component through the middle station includes: For the second type of employee account, sending the second type of employee account to the first management component through the third management component; Determining, by the first management component, a second target employee organization corresponding to the second type of employee account from the first employee general organization; Managing and binding the second type of employee account with the second target employee organization through the first management component to obtain a second organization matching relationship; The second organization matching relationship is sent to the third management component through the first management component via the middle platform.

4. The method according to any one of claims 1 to 3, characterized in that: The third management component adds the organization matching relationship to the first stored basic personnel information to obtain second basic personnel information, wherein the second basic personnel information is employee attribute information, including: In response to receiving the organization matching relationship, the third management component queries the first personnel basic information corresponding to the employee account in the organization matching relationship; The third management component confirms whether the first basic information of the person queried contains the organization matching relationship; In response to confirming that the queried first personnel basic information does not contain the organization matching relationship, the third management component adds the organization matching relationship to the stored first personnel basic information to obtain second personnel basic information, wherein the second personnel basic information is employee attribute information.

5. The method according to claim 1, characterized in that The transmitting the first personnel basic information and the employee account after the system use permission is configured to the third management component through the middle platform, so that the third management component stores the first personnel basic information and the employee account after the system use permission is configured, includes: For the first type of employee account, the first management component transmits the first person basic information received and the generated first type of employee account with configured system usage permissions to the third management component via the middle station; In response to the first type of employee account, the first management component transmits the first personnel basic information received and the first type of employee account generated with the system use permission configured to the third management component via the middle platform, and the third management component stores the first personnel basic information and the first type of employee account with the system use permission configured in the employee data corresponding to the first management component; For the second type of employee account, the second management component transmits the first person basic information received and the second type of employee account generated with the configured system usage authority to the third management component via the middle platform; In response to the second type of employee account, the second management component transmits the first personnel basic information received and the second type of employee account generated with the configured system usage permissions to the third management component via the middle platform, and the third management component stores the first personnel basic information and the second type of employee account with the configured system usage permissions in the employee data corresponding to the second management component.

6. The method according to any one of claims 1 to 5, characterized in that: The method further comprises: In response to receiving a login request from any employee account, verifying the system usage authority of the employee account; In response to the system usage authority verification of the employee account being passed, the employee account accesses the system service having the system usage authority.

7. A resource management system, comprising a first management component, a second management component, a middle platform and a third management component, wherein: The first management component and the second management component respectively respond to the first basic personnel information input by the user as interfaces, wherein the first management component generates a first type of employee account in response to the first basic personnel information input by the user, and the first type of employee account belongs to a first employee general organization; the second management component generates a second type of employee account in response to the first basic personnel information input by the user, and the second type of employee account belongs to a second employee general organization; and configures corresponding system usage permissions for the first type of employee account and the second type of employee account, and different types of employees have different corresponding system service permissions; Furthermore, the first management component is further used to bind an employee account to an employee organization corresponding to the employee account to obtain an organization matching relationship, wherein the employee account includes the first type of employee account and the second type of employee account; The middle platform is used for transmitting the first basic information of the personnel and the employee account after the system use permission is configured to the third management component in response to the first management component and the second management component sending the first basic information of the personnel and the employee account after the system use permission is configured; and for sending the organization matching relationship to the third management component in response to the organization matching relationship sent by the first management component; The third management component is used to store the first personnel basic information and the employee account after configuring system usage permissions in response to the first management component and the second management component sent via the middle station; and in response to the organization matching relationship sent by the first management component via the middle station, add the organization matching relationship to the stored first personnel basic information to obtain the second personnel basic information, wherein the second personnel basic information is employee attribute information.

8. The resource management system according to claim 7, wherein: The first management component is further configured to, after generating the first type of employee account, determine a first target employee organization from the first employee general organization according to the first personnel basic information corresponding to the first type of employee account, manage and bind the first type of employee account with the first target employee organization to obtain a first organization matching relationship, and send the first organization matching relationship to the third management component via the middle station; as well as, The first management component is further used to respond to the second type of employee account sent by the third management component, determine the second target employee organization corresponding to the second type of employee account from the first employee general organization according to the first personnel basic information corresponding to the second type of employee account, manage and bind the second type of employee account with the second target employee organization, obtain a second organization matching relationship, and send the second organization matching relationship to the third management component via the middle station.

9. An electronic device, characterized in that: include: A memory for storing a computer program product; A processor, configured to execute a computer program product stored in the memory, wherein when the computer program product is executed, the method described in any one of claims 1 to 6 is implemented.

10. A computer-readable storage medium, characterized in that: Computer program instructions are stored thereon, and when the computer program instructions are executed by a processor, the method described in any one of claims 1 to 6 is implemented.

11. A computer program product, characterized in that The method comprises computer program instructions, which, when executed by a processor, implement the method according to any one of claims 1 to 6.

Images