How to Use the page module of the starstar portal system to build a document library

The page module architecture of the starstar portal system can be used to build a document management system within the enterprise.

(1) application background

Enterprises usually use shared network disks to store documents between different departments. For example, the Administrator adds a document folder for the personnel department on the server.

However, as files increase, management becomes increasingly inconvenient, mainly reflected in

(1) it is inconvenient to search. You may find a document to repeat all folders.

(2) Maintenance of Public/Private unknown permissions is inconvenient. For example, some systems need to be made public within the document of the Ministry of Personnel, some of which must be viewed only within the Ministry of Personnel, and all the contents in the current management method are mixed and disorganized.

To this end, KaiXing launched the document management module of the pages module.

The document management of the open star pages module does not replace the shared online storage content. Instead, it optimizes the folder organization. In addition, the shared network disk and Web file management of our tasks should coexist.

 

(2) establish a file architecture

Before using pages to build a document library, the system administrator should plan how to divide the document's organizational structure, which is very important. Enterprise departments are independent and associated with each other. In our recommendations, they are generally put together.

Homepage, which is divided by department. Secondly, it is divided based on commonalities. For more information, see.

 

 

 

Generally, administrators classify documents by department, such as the "Personnel Department document" and "Finance Department document". Each department puts the documents in the response folder. General documents, such as "asset procurement" and "Enterprise attendance system", can be placed in "system specifications. For system documents, such as ISO system certification and QS quality management, a level-1 "system document" can be established ".

Before using pages, you must plan and manage documents in the future. The following describes how to implement the above functions.

 

(1) create a "Department document"

(1) Add the "pages" module to the page and click "Edit page" to enter the editing mode ., Click create page"

 

 

 

 

 

(2) On the page, select "blank document library" because the document is stored"

 

 

(3) enter the document library name "Department document"

 

(4) create a sub-document

In "edit mode", right-click the Department document, and a menu is displayed.

 

 

Select "New Project", select "blank document library", and enter the Page name "Personnel Department document". This completes the creation of the Personnel Department folder.

 

 

(3) Set permissions

The permissions of the KaiXing pages module are similar to those of the News Module, but they are more detailed than those of the News Module. Before using the pages module, let's take a look at the introduction of the News Module. Address is http://www.cnblogs.com/mqingqing123/p/3859385.html

 

When the "Personnel Department document" and "Finance Department document" are created under a department, these permissions are inherited from the upper level by default, while the upper level node is the "Department document". Therefore, as long as we authorize all login users to be visible in the "Department document", the sub-document users under it will also be visible.

Select a department document, right-click the Department document, and choose "permission settings". (if no menu is displayed, click the Edit page to enter the editing mode ).

View. authenticated is added here, which can be viewed by authorized users.

 

 

(4) disconnect inheritance.

The benefits of permission inheritance are convenient for maintenance, but sometimes we need to disconnect inheritance. For example, there is a "Personnel Manager" file under the Personnel Department document. By default, the personnel manager inherits permissions from the "personnel documents" at the upper level, while the personnel documents inherit permissions from the "department documents" by default, as a result, the personnel manager file is visible to all authorized users.

This is not what we want to see. We hope that only the personnel department manager can view the modified content. In this case, we need to disconnect the permission inheritance.

 

On the Personnel Manager node, right-click and select permission settings. Note that there is an additional permission inheritance.

The default "permission inheritance" option is selected. We deselect this option. Click OK.

 

 

In this way, no one on the Personnel Manager node can access the node (except the administrator ). In this case, the administrator can re-grant permissions to the changed node.