CN113496037A

CN113496037A - Organization architecture authority setting method, device, equipment and storage medium

Info

Publication number: CN113496037A
Application number: CN202010195561.7A
Authority: CN
Inventors: 张礼庆; 罗强; 吴春颖
Original assignee: Tencent Technology Shenzhen Co Ltd
Current assignee: Tencent Technology Shenzhen Co Ltd
Priority date: 2020-03-19
Filing date: 2020-03-19
Publication date: 2021-10-12

Abstract

The embodiment of the application discloses a method, a device, equipment and a storage medium for setting organization architecture authority, wherein the method comprises the following steps: acquiring a target authority attribute set for a target node in a target organization architecture, wherein the target authority attribute is at least used for representing that the public state of the target node in the target organization architecture is different from the default public state of the node in the target organization architecture; determining a related node range corresponding to a node in a target organization framework according to a preset rule and a target authority attribute of the target node; and setting the association authority of the node in the target organization framework according to the association node range corresponding to the node. The method can reduce the workload required to be consumed when enterprise management personnel set the organizational structure authority, and improve the operation experience.

Description

Organization architecture authority setting method, device, equipment and storage medium

Technical Field

The present application relates to the field of computer technologies, and in particular, to a method, an apparatus, a device, and a storage medium for setting an organization structure authority.

Background

At present, many enterprise Instant Messaging (IM) software provide a function of viewing enterprise organization architecture, and a user can view department hierarchy of the company and basic information of employees belonging to each department through the function of viewing the organization architecture on a software interface, and can also initiate conversation or audio-video conversation with related employees. However, the organizational structure of an enterprise may often contain very important and sensitive information, and the organizational structure information of the enterprise is fully opened for all employees in the enterprise, which often does not meet the real appeal of enterprise managers.

In view of the above situation, in the related art, enterprise managers are mainly configured with corresponding associated authorities for various employees manually, for example, assuming that employees belonging to the same department are used as a class of employees, the enterprise managers need to configure their corresponding associated authorities for the employees in each department respectively, so as to control the departments and employees that the employees can see in the organization structure, and the departments and employees that the employees can communicate in the organization structure. For large and medium-sized enterprises, a large number of departments are usually included, enterprise managers configure corresponding associated authorities for each type of employees respectively through the method, extremely large workload needs to be consumed, and operation experience is poor.

Disclosure of Invention

The embodiment of the application provides a method, a device, equipment and a storage medium for setting organization architecture authority, which can reduce the workload required to be consumed when enterprise managers set organization architecture association authority and improve operation experience.

In view of the above, a first aspect of the present application provides a method for setting organization structure authority, where the method includes:

acquiring a target authority attribute set for a target node in a target organization architecture, wherein the target authority attribute is at least used for representing that the public state of the target node in the target organization architecture is different from the default public state of the node in the target organization architecture;

determining a relevant node range corresponding to a node in the target organization framework according to the target authority attribute of the target node and a preset rule;

and setting the association authority of the node in the target organization framework according to the association node range corresponding to the node.

A second aspect of the present application provides a tissue architecture visibility range setting device, the device including:

an obtaining module, configured to obtain a target permission attribute set for a target node in a target organization architecture, where the target permission attribute is at least used to characterize that a disclosure state of the target node in the target organization architecture is different from a default disclosure state of a node in the target organization architecture;

the association range determining module is used for determining an association node range corresponding to a node in the target organization framework according to the target authority attribute of the target node and a preset rule;

and the association authority setting module is used for setting the association authority of the node in the target organization framework according to the association node range corresponding to the node.

A third aspect of the application provides an apparatus comprising a processor and a memory:

the memory is used for storing a computer program;

the processor is configured to execute the steps of the organizational structure permission setting method according to the first aspect.

A fourth aspect of the present application provides a computer-readable storage medium for storing a computer program for executing the steps of the organizational scheme permission setting method according to the first aspect.

A fifth aspect of the present application provides a computer program product comprising instructions which, when run on a computer, cause the computer to perform the steps of the organizational scheme privilege setting method described in the first aspect above.

According to the technical scheme, the embodiment of the application has the following advantages:

the embodiment of the application provides an organization architecture authority setting method, which allows an enterprise administrator to configure a target authority attribute for a specific node from the perspective of enterprise organization global, so that the public state of the node in an organization architecture is different from the default public state of the node in the organization architecture, for example, in the case that the default public state of the node in the organization architecture is public for each node in the organization architecture, the enterprise administrator can set the target authority attribute for the target node in the organization architecture, so that the target node is hidden from the node in the organization architecture. After the related device obtains the target authority attribute set by the enterprise manager for the target node, the related device can determine the associated node range corresponding to the corresponding joint point in the organization structure according to the target authority attribute of the target node and the preset rule, and correspondingly set the associated authority of the related node in the organization structure according to the associated node range corresponding to the corresponding joint point. Therefore, enterprise management personnel do not need to configure corresponding associated authorities for each type of staff one by one, and only need to set target authority attributes for special nodes in the organization structure, so that the workload required to be consumed during the configuration of the associated authorities of the organization structure can be greatly reduced, the operation experience is improved, and the operation efficiency is improved.

Drawings

Fig. 1 is a schematic view of an application scenario of a method for setting organization structure permissions according to an embodiment of the present application;

fig. 2 is a schematic flowchart of an organization structure authority setting method according to an embodiment of the present application;

fig. 3 is a schematic diagram illustrating a relationship between a node and a white list according to an embodiment of the present application;

FIG. 4 is a schematic representation of an organizational structure according to an embodiment of the present application;

fig. 5 is a schematic diagram of a range of associated nodes according to an embodiment of the present application;

fig. 6 is a schematic diagram of a range of associated nodes according to an embodiment of the present application;

fig. 7 is a schematic diagram of a range of associated nodes according to an embodiment of the present application;

fig. 8 is a schematic diagram of a range of associated nodes according to an embodiment of the present application;

fig. 9 is a schematic diagram of a range of associated nodes according to an embodiment of the present application;

fig. 10 is a schematic application scenario diagram of another organizational structure permission setting method according to an embodiment of the present application;

fig. 11 is an interaction signaling diagram of an organization architecture permission setting method according to an embodiment of the present application;

fig. 12 is a schematic structural diagram of an organization structure authority setting device according to an embodiment of the present application;

fig. 13 is a schematic structural diagram of an organization structure authority setting device according to an embodiment of the present application;

fig. 14 is a schematic structural diagram of an organization structure authority setting device according to an embodiment of the present application;

fig. 15 is a schematic structural diagram of an organization structure authority setting device according to an embodiment of the present application;

fig. 16 is a schematic structural diagram of a server according to an embodiment of the present application.

Detailed Description

In order to make the technical solutions of the present application better understood, the technical solutions in the embodiments of the present application will be clearly and completely described below with reference to the drawings in the embodiments of the present application, and it is obvious that the described embodiments are only a part of the embodiments of the present application, and not all of the embodiments. All other embodiments, which can be derived by a person skilled in the art from the embodiments given herein without making any creative effort, shall fall within the protection scope of the present application.

The terms "first," "second," "third," "fourth," and the like in the description and in the claims of the present application and in the drawings described above, if any, are used for distinguishing between similar elements and not necessarily for describing a particular sequential or chronological order. It is to be understood that the data so used is interchangeable under appropriate circumstances such that the embodiments of the application described herein are capable of operation in sequences other than those illustrated or described herein. Furthermore, the terms "comprises," "comprising," and "having," and any variations thereof, are intended to cover a non-exclusive inclusion, such that a process, method, system, article, or apparatus that comprises a list of steps or elements is not necessarily limited to those steps or elements expressly listed, but may include other steps or elements not expressly listed or inherent to such process, method, article, or apparatus.

In the related art, when an enterprise administrator sets corresponding association rights for employees in an enterprise, the enterprise administrator generally needs to configure corresponding association rights for each type of employees. For large and medium-sized enterprises containing a large number of employees, the types of the employees contained in the large and medium-sized enterprises are extremely rich, enterprise managers configure associated authorities for each type of employees one by one, extremely large workload needs to be consumed, and operation experience is poor.

In order to solve the above technical problem, an embodiment of the present application provides a method for setting an organization architecture permission, which provides a new implementation manner for configuring an associated permission in an organization architecture, that is, on the premise that each node in a default organization architecture is presented in a default public state, an enterprise administrator is allowed to configure a target permission attribute for a target node in the organization architecture, so that the public state of the target node in the organization architecture is different from the default public state. After the related device obtains the target authority attribute configured by the enterprise management personnel for the target node, the related device can determine the related node range corresponding to the related node in the organization structure according to the target authority attribute of the target node and the preset rule, and correspondingly set the related authority of the related node in the target organization structure according to the related node range corresponding to the related node.

Compared with the implementation mode that enterprise managers need to configure corresponding associated authorities for each type of employees respectively in the related technology, the method provided by the embodiment of the application only needs the enterprise managers to configure the target authority attributes for the special nodes in the organization structure, so that the disclosure state of the special nodes in the organization structure is different from the default disclosure state, the workload consumed when the enterprise managers configure the authority of the organization structure can be reduced to a great extent, the operation experience is improved, and the working efficiency is also improved.

It should be understood that the organizational structure permission setting method provided by the embodiment of the present application may be applied to a device with data processing capability, such as a server. The server may be specifically an application server or a Web server; in actual deployment, the server may be an independent server or a cluster server.

In order to facilitate understanding of the technical solution provided by the embodiment of the present application, an application scenario of the method for setting an organizational structure permission provided by the embodiment of the present application is described below.

Referring to fig. 1, fig. 1 is a schematic view of an application scenario of the organizational structure permission setting method provided in the embodiment of the present application. As shown in fig. 1, the application scenario includes: a terminal device 110 facing the enterprise manager, a server 120 and a terminal device 130 facing the enterprise employee; the server 120 is configured to execute the organizational structure permission setting method provided in the embodiment of the present application.

In specific implementation, an enterprise administrator may set a target authority attribute for a target node in a target organization architecture through an enterprise management page displayed on the terminal device 110, so that an disclosure state of the target node in the target organization architecture is different from a default disclosure state of the node in the target organization architecture. For example, assuming that the default public state of a node in the target organization architecture is that each node in the target organization architecture is public, each node in the target organization architecture is allowed to view and communicate, after an enterprise administrator sets a target authority attribute for a target node, the public state of the target node in the target organization architecture can be hidden, and even if a node in the target organization architecture that is not directly associated with the target node cannot view the target node, the node cannot communicate with the target node. After detecting that the enterprise administrator confirms that the target authority attribute is set for the target node, the terminal device 110 may send the identifier of the target node and the target authority attribute to the server 120 through the network.

After receiving the identifier of the target node and the target authority attribute sent from the terminal device 110, the server 120 confirms that the enterprise administrator sets the target authority attribute for the target node. Further, determining a related node range corresponding to related nodes in the target organization framework according to a preset rule and the target authority attribute of the target node; and correspondingly setting the association authority of the relevant nodes in the target organization framework according to the associated node range corresponding to the relevant joint points.

In addition, the server 120 may also generate the to-be-updated organizational structure data of the relevant node by combining the associated node range corresponding to the relevant node and the basic information of the target organizational structure (such as the name, avatar, personal information, etc. corresponding to the node in the target organizational structure). Finally, the client corresponding to the control related joint point displays the organization structure based on the data of the organization structure to be updated, that is, controls the client operating in the terminal device 130 to update and display the current visible organization structure based on the data of the organization structure to be updated.

It should be noted that the nodes in the embodiment of the present application may refer to department nodes in an organization architecture, and may also refer to employee nodes in the organization architecture. If the enterprise administrator sets the target authority attribute for the department node, the employee node belonging to the department node may also be set as the target authority attribute by default, for example, assuming that the enterprise administrator sets the target authority attribute for a certain department node, so that the disclosure state of the department node in the organization structure is set as hidden, the disclosure state of the employee node belonging to the department node in the organization structure may also be set as hidden accordingly.

It should be understood that the application scenario shown in fig. 1 is only an example, and in an actual application, the multiple servers may cooperate to execute the organizational structure permission setting method provided in the embodiment of the present application, and no limitation is made to the application scenario of the organizational structure permission setting method provided in the embodiment of the present application.

The organization architecture authority setting method provided by the present application is described in detail through embodiments below.

Referring to fig. 2, fig. 2 is a schematic flowchart of a method for setting organizational structure permissions provided in an embodiment of the present application. For convenience of description, the following embodiments are described taking a server as an execution subject as an example. As shown in fig. 2, the method for setting organizational structure permission includes the following steps:

step 201: acquiring a target permission attribute set for a target node in a target organization architecture, wherein the target permission attribute is at least used for representing that the public state of the target node in the target organization architecture is different from the default public state of the node in the target organization architecture.

In the technical solution provided in the embodiment of the present application, the server may set the disclosure state of each node in the target organization architecture to a default disclosure state in advance, and if the server detects that an enterprise administrator sets a target authority attribute for a target node in the target organization architecture, it is determined that the enterprise administrator triggers a disclosure state modification operation for the target node, so that the disclosure state of the target node in the target organization architecture is different from the default disclosure state.

It should be noted that, in the technical solution provided in the embodiment of the present application, if the public state of the target node is disclosed in the target organization architecture, it indicates that the target node allows other nodes of the target organization architecture to view the target node, and perform communication operations such as information transmission and reception, audio and video call, and mail transmission and reception with the target node; if the public state of the target node is hidden in the target organization architecture, the public state indicates that the target node does not allow the node in the target organization architecture to check the public state and/or perform communication operations such as information receiving and transmitting, audio and video call, mail receiving and transmitting and the like with the public state.

Taking the default public state of the node in the target organization architecture as an example of disclosing all nodes in the target organization architecture, if the server detects that the enterprise administrator sets the target authority attribute for the target node, it indicates that the enterprise administrator wants the target node to be hidden from the node in the target organization architecture, that is, the enterprise administrator does not want all nodes in the target organization architecture to view the target node and/or communicate with the target node.

It should be understood that, in practical applications, the default public state of the nodes in the target organization architecture may be either public to all nodes in the target organization architecture or hidden to all nodes in the target organization architecture. When the default open state of the nodes in the target organization architecture is that all the nodes in the target organization architecture are open, the server detects that the enterprise administrator sets the target authority attribute aiming at the target nodes, and then the server indicates that the enterprise administrator expects that the target nodes are hidden and expects that other nodes in the target organization architecture cannot check the target nodes and/or cannot communicate with the target nodes; when the default open state of the nodes in the target organization architecture is that all the nodes in the target organization architecture are hidden, the server detects that the enterprise administrator sets the target authority attribute aiming at the target nodes, and then the server indicates that the enterprise administrator wants the target nodes to be opened and wants other nodes in the target organization architecture to view the target nodes and communicate with the target nodes. The default open state of the nodes in the target organization architecture is not limited, and the meaning represented by the operation of setting the target authority attribute for the target nodes is not limited.

For convenience of description, the following describes a technical solution provided by an embodiment of the present application, taking a default public state of a node in a target organization architecture as an example for disclosing all nodes in the target organization architecture. It should be understood that, when the default public state of the node in the target organization architecture is hidden from all nodes in the target organization architecture, the implementation manner of the technical solution provided by the embodiment of the present application is similar thereto.

It should be noted that, in the technical solution provided in the embodiment of the present application, the target node may be a department node in the target organization architecture, and may also be an employee node in the target organization architecture. When the target node is a department node, if the server detects that the enterprise management personnel sets the target authority attribute for the target node, the fact that the enterprise management personnel hope that the department and staff affiliated to the department are hidden in the target organization structure is represented. When the target node is an employee node, if the server detects that the enterprise manager sets the target authority attribute for the target node, the server indicates that the enterprise manager only wants to hide the open state of the employee in the target organization architecture.

It should be noted that, in many cases, simply hiding the target node from all nodes in the target organization architecture that have no direct association with the target node may not meet the real appeal of the enterprise administrator. In practical applications, there may still exist some nodes in the target organization structure that do not have a direct association relationship with the target node and need to perform service communication with the target node, and if the some nodes cannot find the target node in the target organization structure and cannot communicate with the target node, the development of related services may be affected.

In view of the above situation, the method provided in the embodiment of the present application further supports enterprise managers to set a target white list for a target node. When the default open state of the nodes in the target organization architecture is that all the nodes in the target organization architecture are open, and the target authority attribute set for the target node is used for representing that the target node is hidden from the nodes in the target organization architecture, an enterprise manager can record the nodes which have the associated authority with the target node in the target organization architecture through the target white list, and for the nodes which have the associated authority with the target node, the enterprise manager can view the target node and communicate with the target node even if the target node is hidden.

It should be noted that, in practical applications, even if the target permission attribute is set for the target node so that the target node is hidden from the nodes in the target organization structure, there are some nodes in the target organization structure that have associated permissions with the target node by default, such as the target node itself, the upper node (which does not exist when the target node does not have the upper node) to which the target node belongs, and the lower node (which does not exist when the target node does not have the lower node) to which the target node belongs, since the associated permissions of the nodes and the target node are not affected by the target permission attribute set by the enterprise administrator for the target node, the nodes may be ignored when the enterprise administrator sets the target white list for the target node, i.e., the nodes are not recorded in the target white list.

It should be noted that the nodes recorded in the target white list may include employee nodes and/or department nodes. And when the target white list comprises the department node, indicating that the department node and the employee nodes belonging to the department node have associated authority with the target node. In practical application, only one node may be recorded in the target white list, or a plurality of nodes may be recorded, and the number of nodes recorded in the target white list is not limited in any way herein. In addition, one employee node may be recorded in a plurality of target white lists set for different target nodes, and one department node may also be recorded in a plurality of target white lists set for different target nodes.

It should be understood that, in practical applications, the server assigns a corresponding node Identity (ID) to each node in the target organizational structure, and the target whitelist is essentially a node ID list in which node IDs having authority to view the target nodes are recorded.

In order to facilitate understanding of the relationship between the department node, the employee node and the target white list, the relationship diagram shown in fig. 3 is described below. As shown in fig. 3, the nodes in the target organization architecture may correspond to employees and departments in the target organization architecture, the nodes corresponding to the employees are employee nodes, and the nodes corresponding to the departments are department nodes; the target white list set for the target node may be divided into an employee white list and a department white list (of course, the two may also be combined into the same target white list), the employee white list records employee nodes having associated authority with the target node, the department white list records department nodes having associated authority with the target node, one employee node may be configured in a plurality of employee white lists, and one department node may also be configured in a plurality of department white lists.

In practical application, enterprise managers can set target authority attributes aiming at target nodes through an organization architecture management interface in a management client. Specifically, the organization architecture management interface may present each node in the target organization architecture, and support the operation of setting the target permission attribute triggered by the user for each node; enterprise management personnel can select a target node in the target organization architecture according to own management requirements, and set a target authority attribute for the target node, so that the open state of the target node in the target organization architecture is different from the default open state.

After detecting that enterprise managers complete the operation of setting the target authority attribute aiming at the target node, the management client can generate an authority attribute setting request according to the node ID of the target node and send the authority attribute setting request to the server through the network. After receiving the permission attribute setting request, the server may immediately return a response message to the management client to inform the management client that the management client has learned the target permission attribute set for the target node, in order to avoid the management client requesting for an expiration.

It should be understood that, in practical applications, after the management client detects that the enterprise administrator sets the target authority attribute for the target node, the management client may further support the enterprise administrator to configure the target white list for the target node, and if the management client detects that the enterprise administrator configures the target white list for the target node, the management client needs to send the target white list to the server.

Step 202: and determining the associated node range corresponding to the node in the target organization framework according to the target authority attribute of the target node and a preset rule.

After the server obtains the target authority attribute set by the enterprise manager for the target node, the server can further determine the associated node range corresponding to the node in the target organization architecture according to the preset rule. The preset rule refers to a pre-agreed association rule between nodes in the target organization architecture.

An exemplary set of predetermined rules is provided herein, and is described below in conjunction with fig. 4. The preset rule provided by the embodiment of the application mainly comprises the following five points:

firstly, in a target organization architecture, the range of the associated nodes of the employee nodes is a complete tree structure; with the organization structure shown in fig. 4, if node B and node H have an association relationship, node B must have an association relationship with node G and node F.

Second, within the target organizational structure, the superior node may recursively down-correlate all nodes in the subordinate organizational structure; in connection with the organizational scheme shown in FIG. 4, node A must be associated with node B through node H.

Thirdly, in the target organization framework, the subordinate nodes can be associated with the directly-belonging superior department nodes and the public employee nodes belonging to the superior department nodes, and in addition, the subordinate nodes can also be recursively associated with the superior nodes of the directly-belonging superior department nodes; in conjunction with the organizational structure shown in fig. 4, node H may recursively associate node G, node F, and node a, and in the case where there are other public nodes at the same level as node H under node G, node H may also associate these nodes.

Fourthly, in the target organization structure, if a department node is associated, all the open department nodes and employee nodes in the subordinate organization structure of the department node are associated correspondingly; in conjunction with the organizational structure shown in fig. 4, if node B is associated with node F, node B is also associated with node G and node H in the open state of node G and node H.

Fifthly, in the target organization structure, if a certain department node is associated with a node, the node in the lower-level organization structure of the department node inherits the association recursively; in conjunction with the organizational structure shown in FIG. 4, if node C associates with node F, then node D and node E also associate with node F.

It should be understood that the preset rule described above is an exemplary set of preset rules provided in the embodiments of the present application, and in practical applications, other preset rules may also be set according to actual requirements, and the present application does not limit the preset rules in any way.

When the server determines the visible node range corresponding to the node in the target organization framework according to the target state attribute of the target node and the preset rule introduced above, the server may first determine the target node, a higher node to which the target node belongs, and a lower node to which the target node belongs, as a first class node; for a first type of node in a target organization architecture, a server can determine that a corresponding associated node range comprises a target node and a lower node subordinate to the target node; for other nodes except the first type of node in the target organization architecture, the server may determine that the corresponding associated node range does not include the target node and the lower level nodes belonging to the target node.

Specifically, even if the enterprise administrator sets the target authority attribute for the target node, and intends to hide the target node from the nodes in the target organization structure, so that the nodes in the target organization structure can no longer view the target node, and/or can not communicate with the target node, the server can determine that the target node itself, the upper node to which the target node belongs, and the lower node (i.e. the first node) to which the target node belongs in the target organization structure still have the associated authority with the target node according to the second point and the third point in the preset rule, so that for the first node in the target organization structure, the server will set the associated node range including the target node and the lower node to which the target node belongs, and for the other nodes except the first node in the target organization structure, the server will set its associated node range to exclude the target node and the subordinate nodes subordinate to the target node.

To facilitate understanding of the above implementation, the following is illustrated in conjunction with fig. 5. Assuming that the enterprise manager sets the node B of the department in the target organization architecture shown in (a) in fig. 5 to be hidden, the range of the associated nodes of the node B of the employee 1, the node B of the employee 2 and the node B of the employee 3 is shown in (B) in fig. 5, that is, the node B of the department, the node B of the employee 4 and the node B of the employee 5 belonging to the department B cannot be checked by the employee 1, the node B of the employee 2 and the node B of the employee 3 in the target organization architecture, and the node B of the employee 4 and the node B of the employee 5 belonging to the department B cannot communicate with the node B of the employee 5; for the employee 4 node and the employee 5 node, the range of the associated node is as shown in (c) in fig. 5, that is, based on the third point in the preset rule, the association relationship between the employee 4 node and the employee 5 node and the department B node to which the employee 5 node belongs is not affected by the change of the associated authority of the department B node in the target organization architecture.

When the server obtains the target white list set for the target node through step 201 and determines the associated node range corresponding to the node in the target organization architecture, the associated node range of the node in the target organization architecture needs to be determined according to the public state of the target node in the target organization architecture and the target white list according to the preset rule introduced above. Specifically, the server may determine, according to the preset rule in the foregoing, that, for a first class of nodes in the target organization structure (including the target node itself, a higher-level node to which the target node belongs, and a lower-level node which belongs to the target node), and nodes in the target white list, a corresponding associated node range includes the target node and the lower-level node which belongs to the target node; and aiming at other nodes except the first class node and the node in the target white list in the target organization architecture, determining that the corresponding associated node range does not comprise the target node and the lower node which is subordinate to the target node.

To facilitate understanding of the above implementation, the following is illustrated with reference to fig. 6 and 7, respectively.

Assume that the business manager sets the department node B in the target organization architecture shown in fig. 6 (a) to hidden and adds the department node C in the target white list set for the department node B. Then, for the employee 1 node and the employee 2 node belonging to the department C node and the employee 4 node and the employee 5 node belonging to the department B, the associated node ranges are as shown in (B) in fig. 6, that is, based on the fourth point and the fifth point in the preset rule, the employee 1 node and the employee 2 node can inherit the associated authority of the department C node to the department B node and can see the subordinate node belonging to the department B node and communicate with the subordinate node belonging to the department B node, and based on the third point in the preset rule, the associated authority of the employee 4 node and the employee 5 node to the department B node to which they belong is not affected by the change of the associated authority of the department B node in the target organizational structure. For the employee 3 node, the range of the associated node is as shown in (c) in fig. 6, that is, under the condition that the employee 3 node does not belong to the target white list, nor does it comply with the preset rule, the employee 3 node cannot see the department B node whose associated authority is not associated with the node in the target organization architecture, and the lower node belonging to the department B node.

Assume that the business manager sets employee 1 node in the target organization architecture shown in fig. 7 (a) as hidden, and adds employee 3 node and department B node in the target white list set for employee 1 node. Then, for employee 2 node belonging to department a node as well, the range of the associated nodes is as shown in (b) of fig. 7, that is, in the case that the public status of employee 1 node is hidden, even employee 2 node belonging to the same department node as employee 1 node cannot see employee 1 node and cannot communicate with employee 1 node. For employee 3 node and employee 4 node and employee 5 node belonging to department B node, their associated node ranges are shown in fig. 7 (c), i.e. employee 3 node, employee 4 node and employee 5 node all directly or indirectly exist in the target white list, so employee 3 node, employee 4 node and employee 5 node can all see employee 1 node in the target organization architecture and communicate with employee 1 node.

In some possible cases, a node whose disclosure state is set to be hidden may only be able to view itself and subordinate nodes subordinate to itself, i.e., the range of associated nodes of the node whose disclosure state is set to be hidden may only include itself and subordinate nodes subordinate to itself. Taking the example that the department node B in the target organization architecture shown in fig. 8 (a) is set to be hidden, for the employee 1 node, the employee 2 node and the employee 3 node, the associated node ranges are shown in fig. 8 (B), that is, the employee 1, the employee 2 and the employee 3 cannot see the department node B and the employee 4 node and the employee 5 node belonging to the department B in the target organization architecture, and cannot communicate with the employee 4 node and the employee 5 node belonging to the department B; for the employee 4 node and the employee 5 node belonging to the department B node, the associated node ranges are as shown in (c) in fig. 8, that is, the employee 4 node and the employee 5 node can only see the department B node and the employee node belonging to the department B node and communicate with these nodes, but cannot see other nodes in the target organization architecture and cannot communicate with other nodes in the target organization architecture.

Further, a node whose disclosure state is set to be hidden may include, in addition to itself and a lower node subordinate to itself, a node higher in level than itself and a lower node subordinate to itself in its associated node range according to the level of the node. Taking the target organization architecture shown in (a) in fig. 9 as an example in which the department node B is set to be hidden and the level of the department node a is higher than that of the department node B, for the employee 1 node, the employee 2 node and the employee 3 node, the associated node ranges are shown in (B) in fig. 9, that is, the employee 1, the employee 2 and the employee 3 cannot see the department node B and the employee 4 node and the employee 5 node belonging to the department B in the target organization architecture, and cannot communicate with the employee 4 node and the employee 5 node belonging to the department B; for the employee 4 node and the employee 5 node belonging to the department B node, the associated node ranges are shown in (c) in fig. 9, that is, the employee 4 node and the employee 5 node can see both the department B node and the employee node belonging to the department B node, and can see the department a node higher in level than the department B node and the subordinate node belonging to the department a node, and communicate with these nodes.

In one possible implementation, the server may set the associated node range for the full number of nodes in the target organizational architecture. That is, the server may determine the associated node range corresponding to each node in the target organization structure according to the target authority attribute of the target node and the preset rule introduced above.

Specifically, for each department node in the target organization structure, the server may determine, according to the association relationship between the department node and the target node, the influence of the change of the disclosure state of the target node in the target organization structure on the range of the association node of the department node in combination with the above-described preset rule, then determine the range of the association node of the department node based on the influence, and further give the range of the association node of the department node to the employee node belonging to the department node accordingly.

It should be understood that, in the case that the server further acquires a target white list set for the target node, the server may determine, in combination with the target white list, an influence of a change in the disclosure state of the target node in the target organization architecture on the associated node range of the department node.

In another possible implementation manner, in order to reduce the amount of computation required to be consumed when the server sets the visible range of the organization architecture as much as possible, the server may determine the nodes whose associated node ranges need to be changed, and then perform subsequent operations such as determining the associated node ranges only for the nodes. That is, the server may determine, according to the target authority attribute of the target node and the preset rule, a node in the target organization architecture, for which the associated node range needs to be changed, as a node to be processed, and then determine, according to the target authority attribute of the target node, the associated node range corresponding to the node to be processed.

Specifically, the server may determine, for each department node in the target organization structure, according to the association relationship between the department node and the target node, in combination with the above-described preset rule, whether the change of the disclosure state of the target node in the target organization structure affects the range of the association node of the department node, and if it is determined that no affect is generated, it is determined that the department node and the subordinate node subordinate to the department node do not belong to the node to be processed, otherwise, it is determined that the department node and the subordinate node subordinate to the department node belong to the node to be processed. And then, aiming at the nodes to be processed, determining the corresponding associated node range according to the influence of the change of the public state of the target node in the target organization framework on the associated node range of the department node.

It should be understood that, in the case that the server further acquires a target white list set for the target node, the server may determine, in combination with the target white list, whether the change of the public state of the target node in the target organization architecture has an influence on the associated node range of the department node.

It should be noted that, in practical applications, the setting process of the organizational structure association range is usually performed by cooperatively coordinating multiple microservices. Specifically, after the server obtains the target authority attribute set for the target node, the server generally invokes the associated node range calculation service computing _ svr to execute the step 202, determines the associated node range of the node in the target organization structure, and then the associated node range calculation service computing _ svr stores the determined associated node range of the node in the target organization structure in the database, and sets the synchronization flag bit of the stored associated node range to the to-be-synchronized state.

The synchronization service sync _ svr scans the database, and once the database is scanned with the data with the synchronization flag bit set to be in the synchronization state, the synchronization service sync _ svr will correspondingly acquire the associated node range with the synchronization flag bit set to be in the synchronization state, and then start to execute the subsequent steps.

Step 203: and setting the association authority of the node in the target organization framework according to the association node range corresponding to the node.

After the server determines the range of the associated node corresponding to the node in the target organization structure, the server can correspondingly set the associated authority of the node in the target organization structure to determine the node which can be viewed in the target organization structure and the node which can communicate.

Specifically, the server may set that the node has a view authority and a communication authority for nodes within the range of the associated node corresponding to the node, for example, if the range of the associated node corresponding to the first node includes the second node, the third node, and the fourth node, it indicates that the first node can view the second node, the third node, and the fourth node in the target organization structure, and can perform communication interaction with the second node, the third node, and the fourth node.

The server may set that the node does not have a view authority and/or a communication authority for nodes outside the range of the associated node corresponding to the node, for example, if the range of the associated node corresponding to the first node does not include the fifth node, it indicates that the first node cannot view the fifth node in the target organization structure and/or cannot perform communication interaction with the fifth node.

In addition, after the server determines the associated node range corresponding to the node, the server may further generate the organization structure data to be updated of the node according to the associated node range corresponding to the node and the basic information of the target organization structure.

After the server determines the associated node range corresponding to the node in the target organization architecture, the server needs to further generate the organization architecture data to be updated of the node according to the associated node range corresponding to the node and the basic information of the target organization architecture. The basic information of the target organization architecture substantially refers to the basic information of the nodes in the target organization architecture, such as the names of the nodes, the head images of the nodes, the related contact ways of the employees corresponding to the nodes, the basic introduction contents of the nodes, and the like; the organization structure data to be updated of the node substantially refers to data required by the client corresponding to the node when loading and displaying the organization structure.

When the server specifically generates the organization structure data to be updated corresponding to the node in the target organization structure, the server may obtain the basic information corresponding to the node in the associated node range according to the associated node range corresponding to the node, and further generate the organization structure data to be updated of the node by using the obtained basic information.

It should be understood that, if the server determines the corresponding associated node range for all nodes in the target organization structure when executing step 202, at this time, the server needs to respectively determine the organization structure data to be updated corresponding to all nodes in the target organization structure.

If the server determines the corresponding associated node range only for the node (i.e., the to-be-processed node) in the target organization structure whose associated node range needs to be changed when executing step 202, at this time, the server only needs to determine the to-be-updated organization structure data corresponding to the to-be-processed node in the target organization structure.

And controlling the client corresponding to the node to display the organization architecture based on the data of the organization architecture to be updated. After the server generates the organization architecture data to be updated aiming at the nodes in the target organization architecture, the client corresponding to the nodes can be correspondingly controlled to load and display the organization architecture based on the organization architecture data to be updated.

In a possible implementation manner, the server may directly issue the data of the organization structure to be updated to the client of the node corresponding to the server, so that the client directly loads and displays the organization structure based on the data of the organization structure to be updated received by the client.

In another possible implementation manner, considering that in some cases, the data of the organization structure to be updated may be too large, if the data of the organization structure to be updated is directly sent to the client, the client loads and displays the organization structure based on the data of the organization structure to be updated, and the speed of loading and displaying the organization structure may be affected.

Specifically, the server may obtain historical organization architecture data based on the last update of the organization architecture by the client corresponding to the node, and then determine organization architecture change data according to the organization architecture data to be updated and the historical organization architecture data of the node, thereby controlling the client to display the organization architecture based on the organization architecture change data.

The server may specifically obtain historical organization architecture data based on the last time the client updated the organization architecture in the following manner: and acquiring a time stamp sent by the client, wherein the time stamp corresponds to the generation time of the historical organization architecture data based on the last time the organization architecture is updated by the client, and further, calling the historical organization architecture data based on the last time the organization architecture is updated by the client from the database according to the time stamp.

It should be understood that, in practical applications, after a server generates organization structure data to be updated corresponding to a certain node, the server may send an organization structure change notification message to a client corresponding to the node, and after receiving the organization structure change notification message, the client may return a response message with a time stamp to the server, so that the server knows the generation time of the historical organization structure data according to which the client updated the organization structure last time. Or, the client may also send an organization structure update request carrying a time difference to the server at a specific time (for example, when the user login is detected) or periodically, and if the server generates the organization structure data to be updated for the node corresponding to the client before receiving the organization structure update request, the server may obtain the corresponding historical organization structure data according to the timestamp carried by the organization structure update request.

It should be noted that, if the server determines the corresponding associated node range and the organization architecture data to be updated for all nodes in the target organization architecture before the control client displays the organization architecture based on the organization architecture data to be updated, at this time, the server may determine the node to be updated of the organization architecture to be updated based on the historical organization architecture data and the organization architecture data to be updated, which are based on the last time the organization architecture is updated by the client corresponding to each node, so as to avoid controlling all nodes in the target organization architecture to execute the operation of updating the organization architecture, which causes unnecessary waste of network resources and client computing resources.

Specifically, the server may obtain, for each node in the target organization architecture, historical organization architecture data based on the last update of the organization architecture by the client corresponding to the node in the manner described above, and then determine whether the historical organization architecture data is consistent with the organization architecture data to be updated of the node, if so, determine that the node does not belong to the node to be updated, otherwise, determine that the node belongs to the node to be updated. And controlling the client of the node to be updated to display the organization architecture based on the corresponding organization architecture data to be updated.

It should be noted that, if the server determines the corresponding visible node range and the organization architecture data to be updated only for the to-be-processed node in the target organization architecture, which needs to change the visible node range, before controlling the client to display the organization architecture based on the organization architecture data to be updated, at this time, the server may directly control only the client corresponding to the to-be-processed node, and display the organization architecture based on the organization architecture data to be updated of the to-be-processed node.

Compared with the implementation mode that enterprise managers need to configure corresponding associated authorities for each type of employees respectively in the related art, the organization architecture authority setting method provided by the embodiment of the application only needs to configure the target authority attributes for the special nodes in the organization architecture by the enterprise managers, so that the disclosure states of the special nodes in the organization architecture are different from the default disclosure states, the workload consumed when the enterprise managers configure the organization architecture authority can be reduced to a great extent, the operation experience is improved, and the working efficiency is also improved.

In order to further understand the organizational structure permission setting method provided in the embodiment of the present application, the organizational structure permission setting method provided in the embodiment of the present application is cooperatively completed by a web server, a visible range computing server, a database, a synchronization server, and a client, which is described below with reference to fig. 10 and 11 as an example.

Fig. 10 is a schematic diagram of an exemplary application scenario of the organizational structure permission setting method according to the embodiment of the present application, where the application scenario includes a web server 1001, a visibility range calculation server 1002, a database 1003, a synchronization server 1004, and a client 1005. Fig. 11 is a signaling diagram of interaction between devices in the application scenario shown in fig. 10.

Enterprise managers can set target authority attributes and a target white list for target nodes in a target organization structure through a front-end Web management interface, and after the setting of the target authority attributes and the target white list is completed, the front end can send node IDs and the target white list of the target nodes to a Web server, and the Web server forwards the node IDs and the target white list of the target nodes to the visible range calculation server 1002.

After receiving the node ID of the target node and the target white list, the visible range calculation server 1002 may immediately send a response message to the front end through the Web server to prompt that the front end has currently received the node ID of the target node and the target white list. The visible range calculation server 1002 may determine, according to a target permission attribute and a target white list set for the target node, an associated node range of the associated node in the target organization architecture according to a preset visibility rule, store the determined associated node range in the database 1003, and set a synchronization flag bit of the stored associated node range to a state to be synchronized.

The synchronization server 1004 periodically scans the database 1003, and once the associated node range in which the synchronization flag bit is set to be in the to-be-synchronized state is scanned, the associated node range is combined with the basic information of the target organization architecture to generate the to-be-updated organization architecture data of the node. After generating the organization structure data to be updated, the synchronization server 1004 may send an organization structure change notification to the client 1005 corresponding to the node, and after receiving the organization structure change notification, the client 1005 sends a message carrying a timestamp corresponding to the historical organization structure data based on the last time the organization structure was updated to the synchronization server 1004, so that the synchronization server 1004 obtains the corresponding historical organization structure data according to the timestamp, determines the organization structure change data of the current organization structure data to be updated relative to the historical organization structure data, and sends the organization structure change data to the client 1005, so that the client 1005 updates the organization structure based on the organization structure change data.

Aiming at the organizational structure permission setting method described above, the application also provides a corresponding organizational structure permission setting device, so that the organizational structure permission setting method can be applied and realized in practice.

Referring to fig. 12, fig. 12 is a schematic structural diagram of an organization structure authority setting device corresponding to the organization structure authority setting method shown in fig. 2. As shown in fig. 12, the apparatus includes:

an obtaining module 1201, configured to obtain a target permission attribute set for a target node in a target organization architecture, where the target permission attribute is at least used to characterize that a disclosure state of the target node in the target organization architecture is different from a default disclosure state of a node in the target organization architecture;

an association range determining module 1202, configured to determine, according to the target permission attribute of the target node, an association node range corresponding to a node in the target organization architecture according to a preset rule;

an association authority setting module 1203, configured to set an association authority of the node in the target organization architecture according to an association node range corresponding to the node.

Optionally, on the basis of the organizational structure permission setting apparatus shown in fig. 12, when the target state attribute is used to characterize that the target node is hidden from nodes in the target organizational structure, the association range determining module 1202 is specifically configured to:

determining the target node, a superior node to which the target node belongs and a subordinate node to which the target node belongs as a first class node;

for the first class of nodes in the target organization architecture, determining that the corresponding associated node range comprises the target nodes and lower nodes subordinate to the target nodes;

and aiming at other nodes except the first class node in the target organization architecture, determining that the corresponding associated node range does not comprise the target node and lower nodes which are subordinate to the target node.

Optionally, on the basis of the organizational structure permission setting apparatus shown in fig. 12, the obtaining module 1201 is further configured to:

acquiring a target white list set for the target node, wherein other nodes which have associated authority with the target node except the first type of node in the target organization architecture are recorded in the target white list;

the association range determination module 1202 is specifically configured to:

determining, for the first class of nodes in the target organization architecture and the nodes in the target white list, that the corresponding associated node range includes the target node and lower nodes that belong to the target node;

and aiming at other nodes except the first class nodes and the nodes in the target white list in the target organization structure, determining that the corresponding associated node range does not comprise the target nodes and lower nodes which belong to the target nodes.

Optionally, the target white list includes: department nodes and/or employee nodes.

Optionally, on the basis of the organizational structure permission setting apparatus shown in fig. 12, the association permission setting module 1203 is specifically configured to:

and setting that the node has a viewing authority and a communication authority for nodes in the range of the associated node corresponding to the node, and setting that the node does not have the viewing authority and/or the communication authority for nodes outside the range of the associated node corresponding to the node.

Optionally, on the basis of the organizational structure permission setting device shown in fig. 12, referring to fig. 13, fig. 13 is a schematic structural diagram of another organizational structure permission setting device provided in an embodiment of the present application. The device also includes:

an organization architecture data generation module 1301, configured to generate organization architecture data to be updated for the node according to the associated node range corresponding to the node and the basic information of the target organization architecture;

a control module 1302, configured to control the client corresponding to the node to display the organization architecture based on the data of the organization architecture to be updated.

Optionally, on the basis of the organizational structure permission setting apparatus shown in fig. 13, the association range determining module 1202 is specifically configured to:

determining a node needing to change the range of an associated node in the target organization structure as a node to be processed according to the target authority attribute of the target node and the preset rule;

determining a relevant node range corresponding to the node to be processed according to the target authority attribute of the target node;

the organization architecture data generation module 1301 is specifically configured to:

for each node to be processed, generating organization architecture data to be updated corresponding to the node to be processed according to the corresponding associated node range and the basic information of the target organization architecture;

the control module 1302 is specifically configured to:

and controlling the client corresponding to the node to be processed, and displaying the organization architecture based on the data of the organization architecture to be updated.

determining the associated node range corresponding to each node in the target organization framework according to the target authority attribute of the target node and the preset rule;

aiming at each node in the target organization architecture, generating organization architecture data to be updated of the node according to the corresponding associated node range and the basic information of the target organization architecture;

the control module 1302 is specifically configured to:

for each node in the target organization architecture, acquiring historical organization architecture data based on the last time the organization architecture is updated by the corresponding client, judging whether the corresponding organization architecture data to be updated is consistent with the historical organization architecture data, and if not, determining the node as the node to be updated;

and controlling the client corresponding to the node to be updated, and displaying the organization architecture based on the data of the organization architecture to be updated.

Optionally, on the basis of the organizational structure permission setting apparatus shown in fig. 13, the control module 1302 is specifically configured to:

acquiring historical organizational structure data based on the last time when the organizational structure is updated by the client corresponding to the node;

determining organization architecture change data according to the organization architecture data to be updated and the historical organization architecture data;

and controlling the client to display the organization architecture based on the organization architecture change data.

Optionally, on the basis of the organizational structure permission setting device shown in fig. 13, the control module 1004 obtains the historical organizational structure data by:

acquiring a timestamp sent by the client;

and according to the time stamp, determining historical organizational structure data based on the last time the organizational structure is updated by the client.

Optionally, on the basis of the organizational structure permission setting device shown in fig. 12, referring to fig. 14, fig. 14 is a schematic structural diagram of another organizational structure permission setting device provided in the embodiment of the present application. As shown in fig. 14, the apparatus further includes:

a feedback module 1401, configured to return a response message to the management client configured to set the target permission attribute for the target node, so as to inform that the management client has acquired the target permission attribute set for the target node.

Optionally, on the basis of the organizational structure permission setting device shown in fig. 12, referring to fig. 15, fig. 15 is a schematic structural diagram of another organizational structure permission setting device provided in an embodiment of the present application. As shown in fig. 15, the apparatus further includes:

a storage module 1501, configured to store an associated node range corresponding to a node in the target organization architecture in a database, and set a synchronization flag bit of the associated node range to a state to be synchronized;

a reading module 1502, configured to, when data with the synchronization flag bit set to be in the to-be-synchronized state exists in the database, acquire an associated node range with the synchronization flag bit set to be in the to-be-synchronized state, and trigger the association authority setting module 1203 to execute a related operation.

Optionally, on the basis of the organization structure authority setting apparatus shown in fig. 12, the target node is a department node or an employee node.

The organization architecture permission setting device provided by the embodiment of the application only needs enterprise managers to configure the target permission attributes aiming at the special nodes in the organization architecture, so that the disclosure states of the special nodes in the organization architecture are different from the default disclosure states, the workload required to be consumed when the enterprise managers configure the organization architecture permission can be reduced to a great extent, the operation experience is improved, and the working efficiency is also improved.

The embodiment of the present application further provides a device for setting an organizational structure authority, where the device may specifically be a server, and the server provided in the embodiment of the present application will be described below from the perspective of hardware materialization.

Referring to fig. 16, fig. 16 is a schematic structural diagram of a server 1600 according to an embodiment of the present disclosure. The server 1600 may vary widely by configuration or performance, and may include one or more Central Processing Units (CPUs) 1622 (e.g., one or more processors) and memory 1632, one or more storage media 1630 (e.g., one or more mass storage devices) storing applications 1642 or data 1644. Memory 1632 and storage media 1630 may be transient or persistent storage, among others. The program stored on the storage medium 1630 may include one or more modules (not shown), each of which may include a sequence of instructions operating on a server. Further, central processing unit 1622 may be configured to communicate with storage medium 1630 to execute a series of instruction operations on storage medium 1630 at server 1600.

The server 1600 may also include one or more power supplies 1626, one or more wired or wireless network interfaces 1650, one or more input-output interfaces 1658, and/or one or more operating systems 1641, such as Windows Server, Mac OS XTM, UnixTM, LinuxTM, FreeBSDTM, etc.

The steps performed by the server in the above embodiment may be based on the server structure shown in fig. 16.

The CPU 1622 is configured to execute the following steps:

Optionally, the CPU 1622 may be further configured to execute the steps of any implementation manner of the method for setting organization framework permissions provided in this embodiment of the present application.

The embodiment of the present application further provides a computer-readable storage medium for storing a computer program, where the computer program is configured to execute any one implementation of the method for setting an organization architecture authority described in the foregoing embodiments.

The present application further provides a computer program product including instructions, which when run on a computer, causes the computer to execute any one of the implementation manners of the method for setting organization architecture rights in the foregoing embodiments.

It is clear to those skilled in the art that, for convenience and brevity of description, the specific working processes of the above-described systems, apparatuses and units may refer to the corresponding processes in the foregoing method embodiments, and are not described herein again.

In the several embodiments provided in the present application, it should be understood that the disclosed system, apparatus and method may be implemented in other manners. For example, the above-described apparatus embodiments are merely illustrative, and for example, the division of the units is only one logical division, and other divisions may be realized in practice, for example, a plurality of units or components may be combined or integrated into another system, or some features may be omitted, or not executed. In addition, the shown or discussed mutual coupling or direct coupling or communication connection may be an indirect coupling or communication connection through some interfaces, devices or units, and may be in an electrical, mechanical or other form.

The units described as separate parts may or may not be physically separate, and parts displayed as units may or may not be physical units, may be located in one place, or may be distributed on a plurality of network units. Some or all of the units can be selected according to actual needs to achieve the purpose of the solution of the embodiment.

In addition, functional units in the embodiments of the present application may be integrated into one processing unit, or each unit may exist alone physically, or two or more units are integrated into one unit. The integrated unit can be realized in a form of hardware, and can also be realized in a form of a software functional unit.

The integrated unit, if implemented in the form of a software functional unit and sold or used as a stand-alone product, may be stored in a computer readable storage medium. Based on such understanding, the technical solution of the present application may be substantially implemented or contributed to by the prior art, or all or part of the technical solution may be embodied in a software product, which is stored in a storage medium and includes instructions for causing a computer device (which may be a personal computer, a server, or a network device) to execute all or part of the steps of the method according to the embodiments of the present application. And the aforementioned storage medium includes: a U disk, a removable hard disk, a Read-Only Memory (ROM), a Random Access Memory (RAM), a magnetic disk or an optical disk, and other various media capable of storing computer programs.

It should be understood that in the present application, "at least one" means one or more, "a plurality" means two or more. "and/or" for describing an association relationship of associated objects, indicating that there may be three relationships, e.g., "a and/or B" may indicate: only A, only B and both A and B are present, wherein A and B may be singular or plural. The character "/" generally indicates that the former and latter associated objects are in an "or" relationship. "at least one of the following" or similar expressions refer to any combination of these items, including any combination of single item(s) or plural items. For example, at least one (one) of a, b, or c, may represent: a, b, c, "a and b", "a and c", "b and c", or "a and b and c", wherein a, b, c may be single or plural.

The above embodiments are only used for illustrating the technical solutions of the present application, and not for limiting the same; although the present application has been described in detail with reference to the foregoing embodiments, it should be understood by those of ordinary skill in the art that: the technical solutions described in the foregoing embodiments may still be modified, or some technical features may be equivalently replaced; and such modifications or substitutions do not depart from the spirit and scope of the corresponding technical solutions in the embodiments of the present application.

Claims

1. A method for setting tissue architecture authority, the method comprising:

2. The method according to claim 1, wherein when the target permission attribute is used to characterize that the target node is hidden from the node in the target organization architecture, the determining, according to the target permission attribute of the target node, an associated node range corresponding to the node in the target organization architecture according to a preset rule includes:

3. The method of claim 2, further comprising:

determining a relevant node range corresponding to a node in the target organization framework according to the target authority attribute of the target node and a preset rule, including:

4. The method according to claim 1, wherein the setting of the association authority of the node in the target organizational structure according to the associated node range corresponding to the node comprises:

5. The method according to claim 1, wherein after determining the associated node range corresponding to the node in the target organization architecture according to the target permission attribute of the target node and according to a preset rule, the method further comprises:

generating organization architecture data to be updated of the nodes according to the associated node range corresponding to the nodes and the basic information of the target organization architecture;

and controlling the client corresponding to the node to display the organization architecture based on the data of the organization architecture to be updated.

6. The method according to claim 5, wherein the determining, according to the target permission attribute of the target node, an associated node range corresponding to a node in the target organization architecture according to a preset rule includes:

generating the organization architecture data to be updated of the node according to the associated node range corresponding to the node and the basic information of the target organization architecture, including:

the controlling the client corresponding to the node to display the organization architecture based on the data of the organization architecture to be updated includes:

7. The method according to claim 5, wherein the determining, according to the target permission attribute of the target node, an associated node range corresponding to a node in the target organization architecture according to a preset rule includes:

8. The method according to claim 5, wherein the controlling the client corresponding to the node to display an organization architecture based on the data of the organization architecture to be updated comprises:

9. The method according to claim 7 or 8, wherein the obtaining of historical organizational structure data based on the last time the organizational structure was updated by the client corresponding to the node comprises:

acquiring a timestamp sent by the client;

and determining historical organizational structure data based on the last time the organizational structure is updated by the client according to the time stamp.

10. The method according to claim 1, wherein before said determining, according to the target permission attribute of the target node, an associated node range corresponding to a node in the target organization architecture according to a preset rule, the method further comprises:

and returning a response message to the management client for setting the target permission attribute aiming at the target node so as to inform the management client that the target permission attribute set aiming at the target node is acquired.

11. The method according to claim 1, wherein after determining the associated node range corresponding to the node in the target organization architecture according to the target permission attribute of the target node and according to a preset rule, the method further comprises:

storing the associated node range corresponding to the node in the target organization architecture into a database, and setting the synchronization flag bit of the associated node range to be in a state to be synchronized;

when the database is scanned to have the data with the synchronization flag bit set to be in the state to be synchronized, acquiring the associated node range with the synchronization flag bit set to be in the state to be synchronized, executing the associated node range corresponding to the node, and setting the associated authority of the node in the target organization structure.

12. A tissue architecture visibility range setting device, comprising:

13. The apparatus according to claim 12, wherein when the target state attribute is used to characterize that the target node is hidden from nodes in the target organizational structure, the association scope determination module is specifically configured to:

14. An apparatus, comprising a processor and a memory;

the memory is used for storing a computer program;

the processor is configured to execute the organizational structure permission setting method according to any one of claims 1 to 11 according to the computer program.

15. A computer-readable storage medium for storing a computer program for executing the organizational scheme permission setting method according to any one of claims 1 to 11.