The settings of shared directories in dzzoffice are established through institutional departments.
First open Institution User Management. Establish required agencies and departments. Here institutions and departments can be understood as the names of the shared directories. You can also name it according to your own needs, not necessarily the name of the institution and department.
The user's usage rule for the shared directory is that the user can only view the shared directory in the location of his own department. That is to say, which department the user is in, he can see the shared directory of which department. Departments in which he is not present cannot be seen or used.
Admin Rules
There are system administrators, organization administrators, and department administrators in dzzoffice.
System administrators cannot see the shared directories of all institutions and departments.
Organization administrators can see, use and manage all shared directories under the organization.
Department administrators can see, use and manage all shared directories under this department.
In the organization and user management, the establishment of organizations and departments, that is, the establishment of the structure of the system shared directory, can be combined with the above rules to design according to your own needs. Basically, most of the usage requirements of shared directories can be achieved.
Some other issues to be aware of:
1. After the establishment of the institution and department, select the setting page of the institution or department, which needs to enable the shared directory of the institution or department . If you want to put a shortcut to the shared directory automatically on the user's desktop. Need to select on, create a desktop shortcut.
2. After the shared folders of institutions and departments are established, the default root directory is read-only for ordinary members. Administrators need to create a new shared directory with different permissions according to their needs, and then ordinary members can add and use content in it as required. (The purpose of this is to prevent people from messing up the root directory when there are many users, so that the shared directory is not adjusted)
An example of a shared directory
Scenario: There are multiple departments in the "Shanghai Leyun" enterprise, and it is required that the shared directory between the departments cannot be viewed with each other. However, there are some common file contents in the enterprise that need to be viewed and used by all personnel. The following figure shows the created directory structure.
Here you can see that there are some directories under the organization "Shanghai Leyun". These directories are placed directly under the organization, and all personnel under the organization can see and use them (the use is based on the permissions set by the specific shared folder, you can see the distinction of many color icons). There are several departments under the organization. This picture was taken by the administrator of the organization. Organization administrators can view and manage all content under this organization, so he can see all directories. Next, use an account of an "ordinary member of the technical department" to take a screenshot.
Let's take a look at the directory that the "ordinary member of the technical department" sees is the shared directory of his own department, and the shared directory that "Shanghai Leyun" provides for all enterprise members to view. He can't see the shared directory of the finance department and the marketing department in the previous picture.
suggestion:
If using DzzOffice to share files. There are very few people who use it. If there are 2-3 people, they don't care much about permissions. It is completely possible for 2 or 3 people to share an account and share files directly on the same desktop. This is the most convenient.
If there are not many people in the company, maybe 10 or more. Confidentiality between departments is not required. It is possible to establish only one institution without establishing a department. All personnel are placed under this agency. Managers can directly create some shared folders under the organization's directory for use together.
If it is a multi-organization, there are many people. The above example can be repeated to create multiple institutional setups. But if you want to have some common content among multiple institutions, everyone can view it. Here, for the time being, multiple institutions can be regarded as "departments" and placed under the general directory of a top-level institution. Multi-level nesting to achieve.