I. Intro

Who can perform these steps: Primary administrators or administrators with access to "Member Permissions." 

As an administrator, you can set the scope of the organizational structure that users see in Contacts ＞ Organization page in the Feishu app.

You can create a main rule that applies to everyone in the organization and create sets of supplementary rules that only apply to specified members, departments, or user groups. The scope of the organization seen by the members in the contacts varies according to the rule that you set. For example, if you set the members can see their department, then the Organization in the member's Contacts will only show their own department.

II. Steps

Set a main rule

Go to the Feishu Admin Console and click Security > Member Permissions > Visibility scope of organization.

On the Visibility tab, click Edit on the right of Main rule. Choose from one of the four options listed in the table below. Then, click Save to set the main rule.

Main rule type	Description	Associated settings
Members can see everyone	Members can see everyone in the organization.	Supervisors can see the department that they are in charge of is mandatory.
Members can see their unit	Members can only see the organizational structure of their own unit. Note: You'll only be able to choose this option after your organization enables the Unit feature and has at least one unit. For more information, see Admin \| Create and manage units.	You will need to specify to which unit type this rule will apply. Only one unit type can be chosen. For example, if this rule applies to the "Subsidiary" unit type, then members of "Subsidiary" units will only be able to see their unit's organizational structure. Supervisors can see the department that they are in charge of is mandatory. Note: If this rule is applied without any supplementary rules, members who don't belong to any units can't see anyone else.
Members can see their department	Members can see everyone in their department.	You can select Show sub-departments of this department as needed. Supervisors can see the department that they are in charge of is mandatory.
Members can't see anyone	All members can't view any other members.	You can select upervisors can see the department that they are in charge of as needed. If this option is selected, only department supervisors within the organization can see all people in their managed departments and sub-departments.

Click Save.

Set supplementary rules

If you need to set different levels of visibility for different members, departments, or user groups, you can set up supplementary rules for fine-grained visibility.

The priority across different visibility rule types is: high-priority supplementary rules, low-priority supplementary rules, and the main rule.

On the Visibility tab, click Add Rule to the right of either High-priority rules or Low-priority rules.

Set the subject, visibility, and object of the rule. In the example shown in the screenshot below, Alice can't see the "Entertainment BU" department.

Subject: The member, department, or user group to whom the rule applies. They will be the viewers of the organizational structure.

Object: The member or department that the rule either makes visible or hidden to the Subject.

Visibility: Can be set to can see or can't see.

Click Save to complete the setting.

(Optional) You can click Edit or Delete to the right of a rule to modify or remove it.

Verify permission rules

You can verify how the rules you set work. Each verification shows whether one member can see another member at a time.

On the Visibility tab, click Visibility Verification Rules.

In the pop-up window, enter the names, email addresses, or mobile numbers of the subject and object, and click Verify.

You can find how the rules work for the Subject against the Object in Verification result.

Customize department display

You can customize how the departments display when being viewed in Contacts and other scenarios.

Show or hide the number of members in departments

Go to Security > Member Permissions > Visibility scope of organization > Display.

Click Edit to the right of Display the number of members in each department.

Select an option and check the preview on the left.

Do not display: The department won't show the number count of its members.

Display: You can further select the counting method when a member belongs to multiple departments.

Count members from all departments: Members will be counted in each department to which they belong.

Count only the ones in the main department: Members will only be counted in their main department.

Click Save.

Set the display order of departments

You can set the order in which members and departments are displayed in Contacts with a preview.

On the Display tab, click Edit to the right of Display order.

Select an order and check the preview on the left.

Display departments first: The display order is department supervisor, sub-department, and members.

Display members first: The display order is department supervisor, members, and sub-department.

Click Save.

III. About the priority of visibility rules

Across multiple rule types

The priority across different visibility rule types is: high-priority supplementary rules, low-priority supplementary rules, and the main rule.

Within the same rule type

When multiple rules in the same high-priority or low-priority rule conflict, the rules apply in the priority order below:

If the subjects of different rules are inclusive, the rules will follow the priority of subjects as members, user groups, and departments.

If the subjects of the same and are not inclusive, the rule of "can't see" takes priority over "can see".

Rules with the same subjects will be applied according to the priority of objects as members, user groups, and departments. If the objects are not inclusive, the rule of "can't see" takes priority over "can see".

If both the subjects and objects of different rules are identical, the rule of "can't see" takes priority over "can see".

Note: The subjects and objects are identified by their IDs, which can be found on the corresponding details pages. For more information, see Admin | Modify member information, Admin | Create departments and department groups, and Admin | Manage user groups.

How rules are applied in different cases

Subjects of different rules
Objects of different rules
Visibility options
Rule priority
Example
Inclusive (departments and sub-departments)
Irrelevant
Irrelevant
The rule of lower-level departments takes priority over that of higher-level departments.
Rule 1: Department A can't see Member X.
Rule 2: Department A's sub-department can see Member X.
Result: Sub-department rule takes priority over department rule. The sub-department can see Member X while the rest of Department A can't.
Different types, but share members
Irrelevant
Irrelevant
The rules are applied following the priority of subjects as member, user group, and department.
Rule 1: Department A can't see Department B.
Rule 2: User Group 1 can see Department B.
Member X is in both Department A and User Group 1.
Result: User group rule takes priority over department rule. Member X can see Department B.
Same but not inclusive types that share the same members
Irrelevant
Conflicted (include both "can see" and "can't see")
The rule of "can't see" takes priority over that of "can see".
Rule 1: User Group 1 can't see Department A.
Rule 2: User Group 2 can see Department A.
Member X is in both User Group 1 and User Group 2, and the two user groups don't belong to each other.
Result: "Can't see" rule takes priority over "can see" rule. Member X can see Department A.
Identical
Inclusive (departments and sub-departments)
Irrelevant
The rule of lower-level departments takes priority over that of higher-level departments.
Rule 1: Department A can see Department B.
Rule 2: Department A can't see Department B's sub-department.
Result: Sub-department rule takes priority over department rule. Department A can't see the sub-department of Department B.
Different types
Irrelevant
The rule with a member object takes priority over that with a department object.
Rule 1: Department A can see Department B.
Rule 2: Department A can't see Member X in Department B.
Result: Member rule takes priority over department rule. Department A can't see Member X.
Same but not inclusive types that share the same members
Conflicted (include both "can see" and "can't see")
The rule of "can't see" takes priority over that of "can see".
Rule 1: Department A can see Department B.
Rule 2: Department A can't see Department C.
Member X is in both Department B and Department C, and the two departments don't belong to each other.
Result: "Can't see" rule takes priority over "can see" rule. Members in Department A can't see Member X.
Note: The following will happen in Contacts:
If Member X is not the department supervisor of either Department B or Department C, members of Department A can find Member X under Department B in Contacts, but not under Department C.
If Member X is the department supervisor of Department B, members of Department A can't find Member X under both Department B and Department C in Contacts.
Identical
Conflicted (include both "can see" and "can't see")
The rule of "can't see" takes priority over that of "can see".
Rule 1: Member X can see Department A.
Rule 2: Member X can't see Department A.
Result: "Can't see" rule takes priority over "can see" rule. Member X can't see Department A.