Haochen CAD tutorial PDM system initial authority setting

Every employee in the enterprise has a clear responsibility, how to manage rights, define each employee's rights and responsibilities, work scope, work output, and ensure that employees do their own duties It is a content that corporate managers are particularly concerned about.

In order to meet the needs of enterprise management, in the PDM system of Haochen CAD, rights management is the basis for ensuring each user to perform related operations according to their power, and is also the basis of data security and collaborative work. Among them, the initial permission setting is often one of the first work we do. Therefore, in this CAD tutorial, we will introduce the setup and management examples of initial permissions in Haochen PDM software.

First, let's take a look at the initial permissions. A simple understanding of the initial permissions is the individual modules that the user has when logging into the system for the first time and the commands that can be manipulated in those modules.

The initial permissions of the system are set by the [role] module. The system provides three built-in permissions by default. We can create the roles used by different departments in the same folder as the following figure. 1).

Figure 1

After you create a project role, a role that we click, then use the right [properties] commands to set permissions for this role available to be used in this module and the module to The command can also be refined by the [Permissions] button on the right (Figure 2).

Figure 2

It should be noted that the list of commands in the role of authority have a special permission value of & ldquo; & rdquo ;. authorization If a user belongs to a role that has the "Authorization" permission, the user can authorize everyone in a module, redefine the permissions of everyone, so the role of "authorization" Permissions are generally provided to the system administrator (see Figure 3).

FIG. 3

Since & ldquo; initial permissions & rdquo; is immediately under the authority of a module having a user log. In a practical application, the permissions of a user vary with different departments and folders. It is rare for a user to have various permission commands under the entire module. Therefore, the user's "primary authority" has a permission command that is not suitable for providing too much, too wide, and can be customized for different users by the operation of "defining permissions" when planning the system model.