Documentum FAQ 6-system default file cabinet permission requirements

During system implementation, the customer needs to block the display of the default system folder on the interface. to simplify the display, change the dm_world permission of the default file cabinet to none, the file cabinet is hidden, which has little impact on normal query users. However, some errors may be reported from time to time during administrator operations, which are usually prompted by the permission section. Which of the following are the default file cabinets in the system? What are the requirements for permission settings for these file cabinets? What are these file cabinets used?

The following is a description on the EMC official forum.

1. Users must have write permission to the resources cabinet-otherwise they will not be able to use the distribution list or PDF annotation features. when users use these features, a user folder is created in resources and the user's files are kept in the user folder. this is a requirement of the out of the box Documentum system.
2. Users must have read permission to the system cabinet-otherwise they will not be able to log in. This is a requirement of the out of the box Documentum system.
3. Users must have write permission to the temp cabinet. this is required for the execution of server methods which have the save_results flag set to true. the server method result is saved in the temp cabinet and deleted after parsing for errors.
4. The docbase owner home, dmadmin, and templates cabinets may all be hidden from the users by assigning world = none.

Sort it out

 

File cabinet	User Group	Permission	Description
Resources	Dm_world	Write	Saves users' common personal information, such as tagging and assigning a list of PDF documents, including the remarks we mentioned before when processing workflow tasks, the system creates an independent folder for each user to store the data.
System	Dm_world	Read	Login calls system resources to save system public information, such as workflow templates and form templates.
Temp	Dm_world	Write	Results are retained to the temp file cabinet during method execution.
Dmadmin (docbase owner)	Dm_world	None	Hidden
Template	Dm_world	None	Hidden

In addition to the docbase owner (the account used to install docbase) and template, you can directly change dm_world to none to hide users. Other system file cabinet permissions cannot be changed as needed.

 

In what way can these file cabinets be controlled to be invisible to users?

Modify the file cabinet property to hide it.

1) In the attribute field of the file cabinet, you can select "hide. You cannot see it in the file cabinet list.

2) if you need to re-visible to the user, in tools-> preferences, tick the 'show hidden files' and return to the file cabinet list. The previously hidden file cabinet can be seen. Deselect the hide attribute check box. 'OK', visible.

Modifying file cabinet properties only does not affect permissions, so user operations are not affected, just blocking.